VPC peering with a VPC from a different AWS Organization - cost implications

Question

**Background:**

Customer's Fargate tasks in VPC 1 accessed MongoDB clusters on EC2 in VPC 2. Customer migrated their MongoDB clusters on EC2 to MongoDB Atlas (marketplace SaaS offering) in Atlas' VPC. Customer VPC is peered with the external Mongo/Atlas VPC.

Post this migration, customer data transfer cost decreased. (As I understand, customer is no longer responsible VPCPeering-in cost)

**Customer question:**

"Does traffic over a vpc peering connection shows up in cost explorer as api operation = vpc-peering even if one of the vpc’s involved is in another company’s organization/account."

**Ask:**

Q1)  Does VPCPeering-in and VPCPeering-out show in customer account even when customer's VPC is peered with the VPC of an external organization?

Accepted Answer

Q1: Yes, this will be shown in the customers account for the customer's part of the cost. SaaS provider will also see their own part of the cost. Both parties will have some IN and OUT traffic.

If the VPCs in the VPC peering connection are within the same region, the charges for transferring data within the VPC peering connection are the same as the charges for transferring data across Availability Zones. If the VPCs are in different AWS Regions, inter-region data transfer costs apply.

Data transferred "in" to and "out" from Amazon EC2, Amazon RDS, Amazon Redshift , Amazon DynamoDB Accelerator (DAX), and Amazon ElastiCache instances or Elastic Network Interfaces across Availability Zones or VPC Peering connections in the same AWS Region is charged at $0.01/GB in each direction.

https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-basics.html

VPC peering with a VPC from a different AWS Organization - cost implications

Contenido relevante