AWS sap documentation change
Summary
Formatting changes including capitalization fixes, figure caption restructuring, and minor text corrections. Introduced a typo 'Directs Connect' instead of 'Direct Connect'. Updated documentation links and section headers.
Security assessment
Changes are primarily editorial improvements and formatting adjustments. The security-related content about NAT gateways, VPNs, and network segmentation remains unchanged. The typo 'Directs Connect' does not directly create a security vulnerability in documentation. No new security controls or vulnerabilities are being addressed.
Diff
diff --git a/sap/latest/general/overview-sap-planning.md b/sap/latest/general/overview-sap-planning.md index bcb4f76df..545482e72 100644 --- a//sap/latest/general/overview-sap-planning.md +++ b//sap/latest/general/overview-sap-planning.md @@ -5 +5 @@ -SAP notesSAP on AWS architecturesChoosing an AWS Region and Availability ZoneNetwork and connectivityFollowing security best practicesAmazon EC2 instance types for SAPOperating systemsDatabasesSAP installation media +SAP NotesSAP on AWS ArchitecturesChoosing an AWS Region and Availability ZoneNetwork and ConnectivityFollowing Security Best PracticesEC2 Instance Types for SAPOperating SystemsDatabasesSAP Installation Media @@ -30 +30 @@ With the SAP All-on-AWS architecture, all systems and components of your SAP env -Figure 3 depicts an SAP all-on-AWS architecture. The SAP environment running on AWS is integrated with on-premises systems and users via a VPN connection or a dedicated network connection via AWS Direct Connect. SAProuter is deployed in a public subnet and assigned a public IP address that is reachable from the internet to enable integration with the SAP OSS network via a secure network communications (SNC) connection. A [network address translation (NAT) gateway](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat-gateway.html) enables instances in the private subnet to connect to the internet or other AWS services, but prevents instances from receiving inbound traffic that is initiated by someone on the internet. For additional information, see the Configuring Network and Connectivity section. +Figure 3 depicts an SAP all-on-AWS architecture. The SAP environment running on AWS is integrated with on-premises systems and users via a VPN connection or a dedicated network connection via AWS Directs Connect. SAProuter is deployed in a public subnet and assigned a public IP address that is reachable from the internet to enable integration with the SAP OSS network via a secure network communications (SNC) connection. A [network address translation (NAT) gateway](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat-gateway.html) enables instances in the private subnet to connect to the internet or other AWS services, but prevents instances from receiving inbound traffic that is initiated by someone on the internet. For additional information, see the Configuring Network and Connectivity section. @@ -32 +32 @@ Figure 3 depicts an SAP all-on-AWS architecture. The SAP environment running on - +### Figure 3: SAP all-on-AWS architecture @@ -34 +34 @@ Figure 3 depicts an SAP all-on-AWS architecture. The SAP environment running on -**Figure 3: SAP all-on-AWS architecture** + @@ -49 +49 @@ With an SAP hybrid AWS architecture, some SAP systems and components are hosted -Figure 4 depicts an SAP hybrid AWS architecture with SAP DEV and QAS landscapes and SAP test, training, and PoC systems running on AWS. These systems are integrated with SAP systems and users on the corporate network. Connectivity between the VPC and the corporate network is provided with either a VPN connection or an AWS Direct Connect connection. The existing SAProuter and SAP Solution Manager running on the corporate network are used to manage the SAP systems running within the VPC. +Figure 4 depicts an SAP hybrid AWS architecture with SAP DEV and QAS landscapes and SAP test, training, and PoC systems running on AWS. These systems are integrated with SAP systems and users on the corporate network. Connectivity between the VPC and the corporate network is provided with either a VPN connection or an AWS Directs Connect connection. The existing SAProuter and SAP Solution Manager running on the corporate network are used to manage the SAP systems running within the VPC. @@ -51 +51 @@ Figure 4 depicts an SAP hybrid AWS architecture with SAP DEV and QAS landscapes - +### Figure 4: SAP hybrid AWS architecture @@ -53 +53 @@ Figure 4 depicts an SAP hybrid AWS architecture with SAP DEV and QAS landscapes -**Figure 4: SAP hybrid AWS architecture** + @@ -92 +92 @@ Multiple options are available to provide network connectivity between your on-p -[AWS Direct Connect](https://aws.amazon.com/directconnect) makes it easy to establish a dedicated network connection from your premises to AWS. Using AWS Direct Connect, you can establish private connectivity between AWS and your data center, office, or co-location environment. In many cases, this can reduce your network costs, increase bandwidth throughput, and provide a more consistent network experience than internet-based connections. For additional information, see the [AWS Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html). +[AWS Directs Connect](https://aws.amazon.com/directconnect) makes it easy to establish a dedicated network connection from your premises to AWS. Using AWS Directs Connect, you can establish private connectivity between AWS and your data center, office, or co-location environment. In many cases, this can reduce your network costs, increase bandwidth throughput, and provide a more consistent network experience than internet-based connections. For additional information, see the [AWS Directs Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html). @@ -96 +96 @@ Use cases: Recommended for customers who require greater bandwidth and lower lat -For more information, see [Amazon Virtual Private Cloud Cloud Connectivity Options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/welcome.html). +For more information, see [Amazon Virtual Compute Cloud Connectivity Options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/welcome.html). @@ -160 +160 @@ SAP solutions based on the SAP NetWeaver platform and that use [SAP Application -The SAP HANA platform and SAP solutions that run on top of an SAP HANA database—for example, SAP Suite on HANA, SAP S/4HANA, SAP Business Warehouse (BW) on HANA, SAP BW/4HANA— require specific EC2 instance types that have been certified for SAP HANA. For more information, see [Amazon EC2 instance types for SAP on AWS](https://docs.aws.amazon.com/sap/latest/general/ec2-instance-types-sap.html). +The SAP HANA platform and SAP solutions that run on top of an SAP HANA database—for example, SAP Suite on HANA, SAP S/4HANA, SAP Business Warehouse (BW) on HANA, SAP BW/4HANA-- require specific EC2 instance types that have been certified for SAP HANA. For more information, see [Amazon EC2 instance types for SAP on AWS](https://docs.aws.amazon.com/sap/latest/general/ec2-instance-types-sap.html). @@ -256 +256 @@ The following table lists the licensing options available for each operating sys -Operating system | License/subscription options + Operating system | License/subscription options @@ -364 +364 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -SAP on AWS overview +SAP on AWS Overview