View a markdown version of this page

Amazon VPC peering - General SAP Guides
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon VPC peering

VPC peering enables network connection between two Amazon VPCs using private IPv4 and IPv6 addresses. Instances can communicate over the same network. For more information, see What is VPC peering?

Before setting up a VPC peering connection, you need to create a request for SAP’s approval. For a successful VPC peering, the defined IPv4 Classless Inter-Domain Routing (CIDR) block must not overlap. Check with SAP for the CIDR ranges that can be used in RISE with SAP VPC.

VPC peering is one-on-one connection between VPCs, and is not transitive. Traffic cannot transit from one VPC to another via an intermediary VPC. You must setup multiple peering connections to establish direct communication between RISE with SAP VPC and multiple VPCs.

VPC peering works across Amazon Regions. All inter-Region traffic is encrypted with no single point of failure or bandwidth bottleneck. Traffic stays on Amazon Global Network and never traverses the public internet, reducing threats of common exploits and DDoS attacks.

VPC peering connections between multiple accounts in multiple Regions.

Data transfer for VPC peering within an Availability Zone is free. Across Availability Zones, Amazon charges per GB for data in and data out. Across regions, Amazon charges per GB for data out. For more information, see Amazon EC2 pricing. In your Amazon account, use the Availability Zone ID of Amazon account managed by SAP to avoid cross-Availability Zone data transfer charges. You can ask for the Availability Zone ID from SAP. For more information, see Availability Zone IDs for your Amazon resources.

Pricing example - VPC peering across Availability Zones

VPC peering across Availability Zones.

100GB of data sent from the Amazon account – managed by SAP via VPC Peering toward the Amazon account – managed by Customer across AZs:

100GB * USD 0.01 per GB = USD 1 (out - billed to Amazon account – managed by SAP) and 100GB * USD 0.01 per GB = USD 1 (IN - billed to Amazon account – managed by Customer)

Because the cost for data transfer is included in the RISE subscription, the Amazon account that you manage will incur only the cost for traffic in, for example, USD 0.01 per GB.

Note

This cost example also applies when the sender is the Amazon account managed by Customer and the receiver is the Amazon account managed by SAP.

Pricing example - VPC peering across Regions

Note

Cost between Amazon Regions vary. For more information, see Amazon EC2 pricing Data Transfer.

VPC peering across Regions.

1). 100GB of data sent from the Amazon account – managed by SAP via VPC Peering toward the Amazon account – managed by Customer across Regions.

100GB * (USD 0.01–USD 0.138 per GB) = USD 1–USD 13.8 (out - billed to Amazon account – managed by SAP)

Because the cost for data transfer is included in the RISE subscription, the Amazon account – managed by Customer will not incur cost for this example.

2). 100GB of data sent from the Amazon account – managed by Customer via VPC Peering toward the Amazon account – managed by SAP across Regions.

100GB * (USD 0.01–USD 0.138 per GB) = USD 1–USD 13.8 (out - billed to Amazon account – managed by Customer)

As the cost for data transfer is calculated for "data out" the Amazon account – managed by Customer will incur the cost for this example.