PrivateLink Cost Calculator
Price AWS PrivateLink interface endpoints across Availability Zones, including the per-ENI hours and per-GB processing.
Inputs
Each zone gets its own endpoint network interface, and each is billed.
Estimated Monthly Cost
$161.40
Endpoint Network Interfaces Billed
18
Endpoint Hour Charges
$131.40
Data Processing Charges
$30.00
Cost per Endpoint Service
$26.90
Fixed Charges Share of the Bill
81.4%
Step by step
Values used
Interface endpoints = 6 endpoints; Availability Zones per endpoint = 3 zones; Price per endpoint-hour in each zone = 0.0100 USD; Data processed per month = 3,000 GB; Price per GB processed = 0.0100 USD; Billable hours per month = 730 hours
PrivateLink Cost
cost = endpoints × zones × hours × endpoint rate + GB processed × per-GB rate.
Estimated Monthly Cost
= 161.40
Endpoint Network Interfaces Billed
= 18
Endpoint Hour Charges
= 131.40
Data Processing Charges
= 30.00
Cost per Endpoint Service
= 26.90
Fixed Charges Share of the Bill
= 81.4
How it works
An interface endpoint is billed per Availability Zone, not per endpoint, because AWS places an elastic network interface in each subnet you select — so the same endpoint in three zones costs three times the hourly rate. On top of that sits a per-GB data processing charge, which is why the hourly component dominates for many small endpoints and the data component dominates for a few busy ones. PrivateLink often replaces NAT Gateway traffic to AWS APIs, and comparing the endpoint hours against the NAT data processing charge it removes is the calculation that justifies the migration.
Formula
PrivateLink Cost
cost = endpoints × zones × hours × endpoint rate + GB processed × per-GB rate.
- endpoints
- Interface endpoints created for AWS or partner services
- zones
- Availability Zones each endpoint is provisioned in
- endpoint rate
- Hourly price per endpoint network interface
Frequently Asked Questions
How is PrivateLink Cost calculated?
cost = endpoints × zones × hours × endpoint rate + GB processed × per-GB rate. An interface endpoint is billed per Availability Zone, not per endpoint, because AWS places an elastic network interface in each subnet you select — so the same endpoint in three zones costs three times the hourly rate. On top of that sits a per-GB data processing charge, which is why the hourly component dominates for many small endpoints and the data component dominates for a few busy ones.
Why does PrivateLink Cost matter?
PrivateLink often replaces NAT Gateway traffic to AWS APIs, and comparing the endpoint hours against the NAT data processing charge it removes is the calculation that justifies the migration.
What values do I need to enter?
This calculator takes 6 inputs: Interface endpoints, Availability Zones per endpoint, Price per endpoint-hour in each zone, Data processed per month, Price per GB processed, Billable hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
How is PrivateLink different from a gateway endpoint?
Gateway endpoints, available only for S3 and DynamoDB, are route table entries with no hourly or per-GB charge. Interface endpoints use PrivateLink, work with hundreds of services, and carry both charges — so prefer a gateway endpoint where one exists.
Are these prices current?
The defaults reflect us-east-1 list prices for illustration. Interface endpoint hourly and per-GB rates vary by region and the data charge is tiered by monthly volume, so confirm the figures on the AWS PrivateLink pricing page before you budget.