VPC Interface Endpoint Cost Calculator (PrivateLink)

Estimate VPC Interface Endpoint (PrivateLink) cost using a simple model: endpoint-hours (endpoints x AZs x hours/day x days/month) + data processed (GB). Compare baseline vs peak traffic with your pricing.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-01-29. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

AWS network cost hub Guide: VPC endpoints pricing Guide: PrivateLink pricing Guide: estimate endpoint-hours and GB

Inputs

Interface endpoints
AZs per endpoint
Hours/day
Days/month
Use 30.4 for an average month.
Monthly hours: 730
Price ($ / endpoint-hour)
Data processed (GB / month)
~65.79 GB/day, 6.09 Mbps.
Avg Mbps
Use measured throughput from VPC flow logs.
Est 19,699 GB/month.
Price ($ / GB processed)
Scenario presets

Results

Estimated monthly total
$63.78
Hourly component
$43.78
Data processing component
$20.00
Endpoint-hours
4,378

PrivateLink has a fixed AZ footprint before traffic even arrives

Interface endpoints behave differently from NAT and generic transfer tools because they create a recurring endpoint-hour base cost the moment you deploy them. This means the first question is not only "how much GB will flow?" but also "how many endpoints across how many AZs are we willing to keep alive?"

  • Fixed base: endpoints x AZs x runtime window.
  • Variable line: processed GB after the path shifts away from NAT or public routing.
  • Main multiplier: AZ count often matters more than teams expect.

What makes endpoint projects look cheaper on paper than in production

The common modeling error is to compare one endpoint against one NAT line without accounting for endpoint sprawl, per-environment duplication, or the fact that the traffic path may still create cross-AZ spend elsewhere. Private connectivity can be the right decision and still fail as a cost model if the surrounding topology is ignored.

  • AZ expansion: moving from 2 to 3 AZs raises endpoint-hours immediately.
  • Endpoint sprawl: multiple services, environments, and accounts create a quiet fixed-cost floor.
  • NAT displacement assumptions: not every byte behind NAT actually moves to an endpoint.
  • Service mismatch: gateway endpoints such as S3 and DynamoDB should not be counted as interface endpoints.

What to confirm before calling endpoints a savings win

  • Verify which service paths really leave NAT and which still require public or alternate egress.
  • Check whether the endpoint path introduces cross-AZ traffic that offsets some of the NAT reduction.
  • Separate one-time migration traffic from normal processed GB after the routing change settles.
  • Track ownership and lifecycle so unused endpoints do not become permanent fixed cost.

Baseline vs migration-shift endpoint scenarios

Scenario Endpoints AZs Processed GB
Baseline Configured 2-3 Expected
Peak Same Same Migration spike

How to review the first bill after enabling endpoints

  • Verify NAT GB processed decreases for the targeted destinations.
  • Verify endpoint-hours match the real endpoint x AZ deployment instead of the planned diagram.
  • Check cross-AZ transfer trends after routing changes so savings are not being offset elsewhere.
  • Compare endpoint-hours and processed GB line items to billing before treating the rollout as complete.

Next steps

AWS network cost hub Estimate endpoint inputs Endpoints optimization

Example scenario

  • 3 interface endpoints across 2 AZs running 24 hours/day for 30 days, processing 2,000 GB/month.
  • Peak 180% scenario captures migration surges or batch spikes.

Included

  • Endpoint-hours from endpoints x AZs x hours/day x days/month x $ per endpoint-hour.
  • Data processing from GB/month x $ per GB processed.
  • Optional Mbps-based data processed estimator.
  • Baseline vs peak scenario table for endpoint and data spikes.

Not included

  • Other VPC data transfer line items (cross-AZ/cross-region) depending on your path.
  • Service-specific pricing differences and tiered steps unless you reflect them in your inputs.

How we calculate

  • Endpoint-hours = endpoints x AZs per endpoint x (hours/day x days/month).
  • Hourly cost = endpoint-hours x $ per endpoint-hour.
  • Data processing cost = GB processed/month x $ per GB processed.
  • Total = hourly cost + data processing cost.

FAQ

What should I use for AZs per endpoint?
Use the number of Availability Zones where you attach the endpoint. Many teams deploy in 2 or 3 AZs for resiliency, which multiplies endpoint-hours.
How do I estimate data processed (GB)?
Start from the traffic you currently send through NAT to AWS services and estimate how much will move to endpoints. Use flow logs/metrics when possible, or model a few scenarios.
Does this replace the NAT bill?
Not automatically. Endpoints can reduce NAT GB processed for compatible services, but you should model both before and after to find the break-even point.

Related tools

AWS network cost hub Guide: VPC endpoints pricing Guide: PrivateLink pricing Guide: estimate endpoint-hours and GB Guide: VPC endpoints cost optimization Guide: PrivateLink cost optimization Guide: NAT vs VPC endpoints (cost) NAT gateway cost calculator VPC data transfer cost

Related guides

Estimate VPC endpoint cost inputs: endpoint-hours and GB processed
How to estimate VPC interface endpoint (PrivateLink) cost inputs: count endpoints across AZs, estimate monthly hours, and estimate GB processed from NAT metrics, flow logs, or scenario models.
NAT Gateway vs VPC endpoints cost: when PrivateLink wins
Compare NAT Gateway vs VPC endpoints (Interface/Gateway endpoints) cost: model gateway-hours + GB processed versus endpoint-hours + per-GB, estimate how much NAT traffic endpoints remove, and avoid transfer surprises.
PrivateLink cost optimization: reduce endpoint-hours, GB processed, and operational sprawl
A practical PrivateLink optimization playbook: minimize endpoint-hours (endpoints × AZs × hours), reduce traffic volume safely, avoid cross-AZ transfer surprises, and prevent endpoint sprawl across environments.
VPC endpoints cost optimization: reduce endpoint-hours and avoid transfer pitfalls
A practical playbook to reduce VPC interface endpoint costs: consolidate endpoints, right-size AZ coverage, reduce endpoint GB processed, and avoid cross-AZ transfer pitfalls.
VPC endpoints pricing: what to model (interface vs gateway endpoints)
A practical VPC endpoints pricing checklist: interface endpoint hours, per-GB processing, gateway endpoint differences, and the transfer pitfalls that cause surprises.
AWS PrivateLink pricing: what to model (consumer vs provider)
A practical PrivateLink pricing checklist: interface endpoint-hours, per-GB processing, and provider-side considerations. Includes the transfer pitfalls that cause surprise bills.

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-01-29. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .