Networking
AWS PrivateLink Interface VPC Endpoint
- Timebilled
- Bytesbilled
- Callsnot billed
In one line
Hourly per endpoint per AZ, plus per GB processed. The AZ count is the multiplier people forget.
What gets missed
The hourly charge runs for every AZ the endpoint is provisioned in, irrespective of the state of its association with the service. Data processing applies in both directions and tiers across a whole Region.
Find it on your bill
Filter Cost Explorer or your Cost and Usage Report by these usage types. A usage type with no region prefix means us-east-1.
VpcEndpoint-HoursVpcEndpoint-Bytes
Bills the same way
These services turn exactly the same meters, so what you learn here transfers.