AWS sap documentation change
Summary
Minor wording change from 'Once' to 'After' in VPN attachment instructions and restructured pricing examples with improved formatting and currency notation updates ($ to USD).
Security assessment
Changes involve documentation clarity improvements and formatting adjustments. No security vulnerabilities, configurations, or features are mentioned or modified. The VPN attachment process remains unchanged.
Diff
diff --git a/sap/latest/general/rise-connection-cloud-wan.md b/sap/latest/general/rise-connection-cloud-wan.md index 4d90ba3fc..774baa66d 100644 --- a//sap/latest/general/rise-connection-cloud-wan.md +++ b//sap/latest/general/rise-connection-cloud-wan.md @@ -45 +45 @@ You can find out more details from these documentations: - 1. **Attaching AWS Site-to-Site VPN (S2S VPN) to AWS Cloud WAN** – Create a Site-to-Site VPN connection with Target Gateway Type set to Not Associated. You can create an AWS S2S VPN attachment for AWS Cloud WAN under Site-to-Site VPN connections from the Amazon VPC console. Once the AWS S2S VPN is created, you can [attach it to AWS Cloud WAN core network](https://docs.aws.amazon.com/network-manager/latest/cloudwan/cloudwan-vpn-attachment-add.html). For more information, see [How Site-to-Site VPN connection can be created for AWS Cloud WAN](https://docs.aws.amazon.com/vpn/latest/s2svpn/create-cwan-vpn-attachment.html). + 1. **Attaching AWS Site-to-Site VPN (S2S VPN) to AWS Cloud WAN** – Create a Site-to-Site VPN connection with Target Gateway Type set to Not Associated. You can create an AWS S2S VPN attachment for AWS Cloud WAN under Site-to-Site VPN connections from the Amazon VPC console. After the AWS S2S VPN is created, you can [attach it to AWS Cloud WAN core network](https://docs.aws.amazon.com/network-manager/latest/cloudwan/cloudwan-vpn-attachment-add.html). For more information, see [How Site-to-Site VPN connection can be created for AWS Cloud WAN](https://docs.aws.amazon.com/vpn/latest/s2svpn/create-cwan-vpn-attachment.html). @@ -58 +58,5 @@ You can estimate the costs of deploying AWS Cloud WAN from the [pricing document -**Pricing example – AWS Cloud WAN connecting two VPCs in same Regions** _[NOTE: cost between AWS Regions vary. For more information see:[ Amazon EC2 pricing Data Transfer](https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer)]_ 100GB of data sent from a VPC in Region X in the AWS account – managed by SAP via Cloud WAN that resides in the AWS account – managed by customer ending at a VPC managed by customer. 100GB * $0.02 per-GB = $2 (Cloud WAN data processing) (Billed to AWS account – managed by SAP) Apart from data processing there would be VPC attachment cost to AWS account – managed by SAP. [Cloud WAN pricing](https://aws.amazon.com/cloud-wan/pricing/) would vary depending upon region where SAP VPC is attached to Cloud WAN. For example, SAP VPC is in Region US East (N. Virginia). You pay $0.065 per hour for VPC attachments in the US East (N. Virginia) Region. $0.065 * 730 = $47.45 (Monthly fixed cost billed to AWS account , managed by SAP) Hence the total cost = $49.45 Data processing and VPC Attachment costs are charged to the VPC owner who sends the traffic to AWS Cloud WAN. As the sending VPC is residing in the AWS account – managed by SAP and the cost for data transfer is included in the RISE subscription, thus the AWS account – managed by Customer will not incur data transfer and attachment cost for this example. The AWS account - managed by customer will only be billed for the price Cloud WAN per VPC attachment per hour. Data out of an AZ will always go via Cloud WAN endpoint in that AZ to reach other VPC, so there is no cross AZ Data Transfer costs. +**Pricing example – AWS Cloud WAN connecting two VPCs in same Regions** + +###### Note + +Cost between AWS Regions vary. For more information, see [Amazon EC2 pricing Data Transfer](https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer). 100GB of data sent from a VPC in Region X in the AWS account – managed by SAP via Cloud WAN that resides in the AWS account – managed by customer ending at a VPC managed by customer. 100GB * USD 0.02 per GB = USD 2 (Cloud WAN data processing) (Billed to AWS account – managed by SAP) Apart from data processing there would be VPC attachment cost to AWS account – managed by SAP. [Cloud WAN pricing](https://aws.amazon.com/cloud-wan/pricing/) would vary depending upon region where SAP VPC is attached to Cloud WAN. For example, SAP VPC is in Region US East (N. Virginia). You pay USD 0.065 per hour for VPC attachments in the US East (N. Virginia) Region. USD 0.065 * 730 = USD 47.45 (Monthly fixed cost billed to AWS account , managed by SAP) Hence the total cost = USD 49.45 Data processing and VPC Attachment costs are charged to the VPC owner who sends the traffic to AWS Cloud WAN. Because the sending VPC resides in the AWS account – managed by SAP and the cost for data transfer is included in the RISE subscription, the AWS account – managed by Customer will not incur data transfer and attachment cost for this example. The AWS account - managed by customer will only be billed for the price Cloud WAN per VPC attachment per hour. Data out of an AZ will always go via Cloud WAN endpoint in that AZ to reach other VPC, so there is no cross AZ Data Transfer costs. @@ -65 +69,5 @@ You can estimate the costs of deploying AWS Cloud WAN from the [pricing document -**Pricing example – AWS Cloud WAN connecting two VPCs in different Regions** _[NOTE: cost between AWS Regions vary. For more information see:[ Amazon EC2 pricing Data Transfer](https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer)]_ 100GB of data sent from a VPC in region Y in the AWS account - managed by Customer via AWS Cloud WAN to AWS Account - managed by SAP in different region X. 100GB * $0.02 per-GB = $2 (Cloud WAN data processing) + 100GB * ($0.01 - $0.138 per-GB) = $1 - $13.8 (Region out) = $3 - $15.8 (Total - billed to AWS account – managed by Customer) Data processing is charged to the VPC owner who sends the traffic to Cloud WAN. As the sending VPC is residing in the AWS account – managed by customer all data transfer costs for this example are billed to the AWS account – managed by Customer. In addition, the AWS account – managed by Customer will be billed for the price per VPC attachment per hour in region Y. VPC attachment charges in Region X would be charged to AWS account – managed by SAP and the charges are included in the RISE subscription. +**Pricing example – AWS Cloud WAN connecting two VPCs in different Regions** + +###### Note + +Cost between AWS Regions vary. For more information, see [Amazon EC2 pricing Data Transfer](https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer). 100GB of data sent from a VPC in region Y in the AWS account - managed by Customer via AWS Cloud WAN to AWS Account - managed by SAP in different region X. 100GB * USD 0.02 per GB = USD 2 (Cloud WAN data processing) + 100GB * (USD 0.01–USD 0.138 per GB) = USD 1–USD 13.8 (Region out) = USD 3–USD 15.8 (Total - billed to AWS account – managed by Customer) Data processing is charged to the VPC owner who sends the traffic to Cloud WAN. As the sending VPC is residing in the AWS account – managed by customer all data transfer costs for this example are billed to the AWS account – managed by Customer. In addition, the AWS account – managed by Customer will be billed for the price per VPC attachment per hour in region Y. VPC attachment charges in Region X would be charged to AWS account – managed by SAP and the charges are included in the RISE subscription.