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.

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

How to get your inputs

  • Interface endpoints: count distinct interface endpoints you plan to deploy (often by AWS service).
  • AZs per endpoint: this is the main multiplier (2 vs 3 AZs changes endpoint-hours materially).
  • Schedule: hours/day and days/month should match endpoint uptime.
  • GB processed: estimate how much NAT traffic to AWS services will shift to endpoints (use flow logs or model scenarios).
  • Pricing: use region-specific endpoint-hour and data processing rates.

Result interpretation

  • Endpoint-hours scale with AZ count; that is usually the fixed base cost.
  • Data processed scales with traffic shifts; model a migration spike if moving traffic from NAT.

Common mistakes

  • Forgetting that interface endpoints are per AZ (endpoint-hours scale with AZ count).
  • Creating endpoint sprawl across environments without ownership/lifecycle.
  • Moving traffic across AZ boundaries and creating transfer charges elsewhere.
  • Counting gateway endpoints (S3/DynamoDB) in PrivateLink endpoint costs.

Scenario planning

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

Validate after changes

  • Verify NAT GB processed decreases for the targeted destinations.
  • Verify endpoint-hours match your endpoint x AZ deployment.
  • Check cross-AZ transfer trends after routing changes.
  • Compare endpoint-hours and GB processed line items to billing.

Next steps

AWS network cost hub Estimate endpoint inputs Endpoints optimization
Advertisement

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

AWS network cost guide: NAT, VPC endpoints, PrivateLink, and data transfer (what to model)
A practical AWS network cost hub: how to model NAT Gateway, VPC endpoints/PrivateLink, and cross-AZ/cross-region data transfer. Includes formulas, break-even workflow, and a troubleshooting checklist.
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.
Advertisement

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