Amazon VPC pricing

There are no additional charges for creating and using an Amazon Virtual Private Cloud (VPC) itself. If you choose to create a Network Address Translation (NAT) gateway in your VPC, you are charged for each “NAT Gateway-hour" that your gateway is provisioned and available. Amazon VPC Reachability Analyzer charges you each time you analyze connectivity between a given source and destination. If you choose to enable traffic mirroring, you will be charged hourly for each Elastic Network Interface (ENI) enabled with traffic mirroring. For specific pricing rates, please read below.

Usage charges for other Amazon Web Services solutions, including Amazon Elastic Compute Cloud (Amazon EC2), still apply at published rates for those resources, including data transfer charges. If you connect your VPC to your corporate datacenter using the optional hardware virtual private network (VPN) connection, pricing is per VPN connection-hour (the amount of time you have a VPN connection in the "available" state). Partial hours are billed as full hours, and data transferred over VPN connections will be charged at standard AWS Data Transfer rates.

NAT Gateway Pricing

If you choose to create a NAT gateway in your VPC, you are charged for each “NAT Gateway-hour" that your gateway is provisioned and available. Data processing charges apply for each gigabyte processed through the NAT gateway regardless of the traffic’s source or destination. Each partial NAT Gateway-hour consumed is billed as a full hour. You also incur standard AWS data transfer charges for all data transferred via the NAT gateway. If you no longer wish to be charged for a NAT gateway, simply delete your NAT gateway using the AWS Management Console, command line interface, or API.

Amazon VPC Reachability Analyzer Pricing

Amazon VPC Reachability Analyzer charges you each time you analyze connectivity between a given source and destination.

Amazon VPC Traffic Mirroring Pricing

If you choose to enable traffic mirroring on ENI of Amazon EC2 instances, you will be charged hourly for each ENI that is enabled with traffic mirroring. If you no longer wish to be charged for traffic mirroring, simply disable traffic mirroring on EC2 instance ENIs using the AWS Management Console, command line interface, or API.

Amazon VPC Ingress Routing

Amazon VPC ingress routing is available in all AWS commercial and AWS GovCloud (US) Regions at no additional cost.

Amazon VPC Reachability Analyzer - Pricing example

Let’s assume you analyze the connectivity between two instances ten times.

You will be charged for each analysis; the price per analysis processed is $0.10. 10 connections x $0.10 per connection = $1

This will result in a charge of $1.

Amazon VPC Traffic Mirroring - Pricing example

You enable traffic mirroring sessions on five ENIs in your Amazon VPC in the US East (Ohio). Traffic mirroring sessions were active for 30 days, 24 hours a day.

You will be charged on an hourly basis, for each hour the traffic mirroring sessions were active on ENIs. For US East (Ohio) Region, the hourly rate is $0.015.
5 sessions x 30 days x 24 hr/day x $0.015 per session-hr = $54

This will result in a charge of $54.

NAT Gateway - Pricing example

Let’s assume you created a NAT gateway and you have an EC2 instance routing to the internet through the NAT gateway. Your EC2 instance behind the NAT gateway sends a 1 GB file to one of your Amazon Simple Storage Service (Amazon S3) buckets. The EC2 instance, NAT gateway, and S3 Bucket are in the same region of the US East (Ohio), and the NAT gateway and EC2 instance are in the same Availability Zone. We calculate your cost as follows:

• NAT Gateway Hourly Charge: NAT Gateway is charged on an hourly basis. For this region, the rate is $0.045 per hour.
• NAT Gateway Data Processing Charge: 1 GB data went through the NAT gateway. The Data Processing charge will result in a charge of $0.045.
• Data Transfer Charge: This is the standard EC2 Data Transfer charge. 1 GB data was transferred from the EC2 instance to S3 via the NAT gateway. There was no charge for the data transfer from the EC2 instance to S3, as it is Data Transfer Out to Amazon EC2 to S3 in the same region. There was also no charge for the data transfer between the NAT gateway and the EC2 instance since the traffic stays in the same Availability Zone using private IP addresses. There will be data transfer charges between your NAT gateway and EC2 instance if they are in a different Availability Zone.