You can create interface VPC endpoints to enable private connectivity to a service that is either owned by AWS or owned by an AWS customer or partner. You will be billed for each hour that your VPC endpoint remains provisioned in each Availability Zone, irrespective of the state of its association with the service. Such hourly billing for your VPC endpoint will stop when you delete it. Hourly billing will also stop if the endpoint service owner rejects your VPC endpoint’s attachment to their service, and that service is subsequently deleted. Such VPC endpoints cannot be reused, you should delete them.
Data processing charges apply for each Gigabyte processed through the VPC endpoint regardless of the traffic’s source or destination. Each partial VPC endpoint-hour consumed is billed as a full hour. Irrespective of the association state of the VPC endpoint, you will incur data transfer charges if you send data to a VPC endpoint.
Some AWS services may optionally include the cost of interface VPC endpoints associated with their service in the cost of their service, and you may not see these costs directly identified in your bill. Such cases will be identified in each of those services pricing information.
|Region||Price per VPC endpoint per AZ ($/hour)||Price per GB data processed ($)|
|US East (N. Virginia)||0.01||0.01|
|US East (Ohio)||0.01||0.01|
|US West (Oregon)||0.01||0.01|
|US West (N. California)||0.011
|Asia Pacific (Singapore)||0.013||0.01|
|Asia Pacific (Seoul)
|Asia Pacific (Sydney)||0.013
|Asia Pacific (Mumbai)||0.013||0.01|
|Asia Pacific (Tokyo)||0.014||0.01|
|South America (São Paulo)