VPC endpoint pricing explained
Interface VPC endpoints (AWS PrivateLink) cost $0.01 per hour for each Availability Zone they are deployed in, plus $0.01 per GB processed, in us-east-1 at the time of writing. Gateway endpoints for S3 and DynamoDB are free. Both are usually cheaper than sending the same traffic through a NAT gateway.
Pricing dimensions
| Endpoint type | Hourly | Data processed |
|---|---|---|
| Interface endpoint | $0.01 per endpoint per AZ | $0.01 per GB (first petabyte a month) |
| Gateway endpoint (S3, DynamoDB) | Free | Free |
| Gateway Load Balancer endpoint | $0.01 per AZ | $0.0035 per GB |
From the AWS Price List API at the time of writing. One interface endpoint in three AZs is three billable endpoint-hours each hour, about $21.90 a month before traffic.
Worked examples
1. Private subnets for ECS on Fargate. Five interface endpoints (ECR API, ECR Docker, CloudWatch Logs, STS, Secrets Manager) in three AZs, carrying 200 GB a month: 15 × 730 × $0.01 = $109.50 plus 200 × $0.01 = $2.00, $111.50 a month.
2. Endpoint against NAT for 2 TB of pulls. Through a NAT gateway, 2,048 × $0.045 = $92.16 in processing; through an interface endpoint, 2,048 × $0.01 = $20.48. ECR image layers are served from S3, so a free S3 gateway endpoint takes most of that traffic for nothing.
3. S3 through a gateway endpoint. 5 TB a month from S3 to instances in the same Region: $0.00 for the endpoint, against 5,120 × $0.045 = $230.40 through NAT.
When an interface endpoint pays off
Each interface endpoint costs about $7.30 per AZ a month before traffic. It saves $0.035 per GB against NAT processing ($0.045 − $0.01), so a single-AZ endpoint breaks even at roughly 209 GB a month of traffic it would otherwise send through NAT. Below that, it is worth having only for security (no internet path) or for private DNS resolution of AWS APIs.
Easy-to-miss charges
- Endpoints in every VPC: the hourly charge repeats per VPC. Centralising endpoints in a shared services VPC reached by Transit Gateway trades endpoint-hours for Transit Gateway processing.
- Endpoints in AZs you do not use.
- Cross-AZ traffic to an endpoint ENI in another zone.
- Endpoint services you publish: consumers pay their endpoint charges, and you pay for the NLB behind your service.
Sharing endpoints across VPCs
Interface endpoints can be placed in a shared services VPC and reached from other VPCs through Transit Gateway or VPC peering, with Route 53 private hosted zones resolving the service names to the shared endpoint. This saves endpoint-hours when you have many small VPCs, but adds Transit Gateway data processing and cross-VPC complexity, so it pays off mainly for services with light traffic used from many VPCs.
Seeing endpoint cost
Interface endpoint charges appear under VPC in Cost Explorer, with usage types USE1-VpcEndpoint-Hours
and USE1-VpcEndpoint-Bytes. To list endpoints and their type:
aws ec2 describe-vpc-endpoints \
--query 'VpcEndpoints[].{id:VpcEndpointId,svc:ServiceName,type:VpcEndpointType,subnets:length(SubnetIds)}' --output table Cutting it: VPC endpoint cost.
Questions
Do VPC endpoints cost money?
Interface endpoints do: $0.01 per AZ-hour plus $0.01 per GB in us-east-1 at the time of writing. Gateway endpoints for S3 and DynamoDB are free.
Is the S3 VPC endpoint free?
The gateway endpoint for S3 is free. An interface endpoint for S3, needed for access from on-premises or other Regions, is billed like any interface endpoint.
How much does a VPC interface endpoint cost per month?
About $7.30 per AZ before traffic, so roughly $21.90 for an endpoint in three AZs, plus $0.01 per GB processed.
A missing endpoint often shows up as a NAT cost spike after a new service ships. CloudConsole is being built to show costs and alarms on a phone.
About the app → · Download on the App Store