AWS Pricing: IGW vs Native Peering Traffic Charges

VPC Peering Cost

There is no charge for setting up or running a VPC peering connection

• Reference1: https://aws.amazon.com/blogs/aws/new-vpc-peering-for-the-amazon-virtual-private-cloud/
• Data transferred across peering connections is charged at 1 cent/GB for send and receive, regardless of the AZ involved.
   
• Reference2: https://calculator.s3.amazonaws.com/index.html
  • VPC Peering Data Transfer: 1 cents/GB in one direction
  • Intra-Region Data Transfer: 1 cents/GB in one direction
  • Inter-Region Data Transfer Out: 2 cents/GB in one direction
• Reference3: https://aws.amazon.com/ec2/pricing/on-demand/
  • Data transferred “in” to and “out” from public or Elastic IPv4 address is charged at 1 cents/GB in each direction.

Conclusion

If the data stays within the AWS Network then the data-charges are consistent regardless if one is using AWS private IPs or AWS public IP (EIP).

That means, when Aviatrix build the tunnel using the AWS public IP (EIP), AWS detects that since both sides are its own IPs, it keeps the data inside the AWS Network.

If the data is really going out towards the INTERNET to a non AWS public IP, then the charges are 10 cents per GB.

Whether the tunnel uses IGW or Native Peering, within the AWS charges are same. 2 cents per GB (counting both directions).