AWS sap documentation change
Summary
Formatting corrections, figure label updates, and image placement adjustments in SAP architecture guide
Security assessment
Changes involve typo fixes (e.g., 'On premise' to 'On-premises'), figure caption updates, and image repositioning without any security-specific content modifications. No evidence of addressing vulnerabilities or security controls.
Diff
diff --git a/sap/latest/general/arch-guide-introduction.md b/sap/latest/general/arch-guide-introduction.md index d6c29cc44..5a6db1d8f 100644 --- a//sap/latest/general/arch-guide-introduction.md +++ b//sap/latest/general/arch-guide-introduction.md @@ -11 +11 @@ For decades, SAP customers protected SAP workloads on premise with two common pa -Let's recap the SAP system design and single points of failure that are part of the SAP n-tier architecture. +Let’s recap the SAP system design and single points of failure that are part of the SAP n-tier architecture. @@ -15,2 +14,0 @@ Let's recap the SAP system design and single points of failure that are part of - - @@ -18,0 +17,2 @@ Let's recap the SAP system design and single points of failure that are part of + + @@ -60,0 +61,2 @@ From the perspective of documented and measurable data points, HADR requirements +**Figure 1: SAP single points of failure** + @@ -63 +65 @@ From the perspective of documented and measurable data points, HADR requirements -**Figure 2: Recovery from a disruptive event** +≈ @@ -71 +73 @@ To meet disaster recovery requirements (the preceding scenarios represent an ele - +**Figure 3: On-premises disaster recovery** @@ -73 +75 @@ To meet disaster recovery requirements (the preceding scenarios represent an ele -**Figure 3: On premise disaster recovery** + @@ -77 +79 @@ In Figure 3, we give an example of an approach that customers often take on prem -Customers migrating their SAP workloads to cloud providers still revert to this architecture and map it to AWS Regions and Availability Zones (AZs) as depicted in Figure 4\. While this architecture can work in your environment, it does not follow the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) which helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for their applications. +Customers migrating their SAP workloads to cloud providers still revert to this architecture and map it to AWS Regions and Availability Zones (AZs) as depicted in Figure 4. While this architecture can work in your environment, it does not follow the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) which helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for their applications. @@ -79 +81 @@ Customers migrating their SAP workloads to cloud providers still revert to this - +**Figure 4: On-premises to AWS region mapping approach** @@ -81 +83 @@ Customers migrating their SAP workloads to cloud providers still revert to this -**Figure 4: On premises to AWS region mapping approach** + @@ -85,2 +86,0 @@ AWS isolates facilities geographically in Regions and Availability Zones. A Mult - - @@ -89 +89 @@ AWS isolates facilities geographically in Regions and Availability Zones. A Mult -With the risk of location failure significantly reduced for the primary compute capacity, the requirements for a second Region can be evaluated based on business requirements. You can rapidly deploy required capacity in the same or different Region with AWS. Idle hardware is no longer an issue. Data backups can be stored on Amazon Simple Storage Service (Amazon S3) in a single AWS Region or in multiple AWS Regions by leveraging cross-Region replication. This architecture can be simplified and be made readily available (Figure 6). + @@ -91 +91 @@ With the risk of location failure significantly reduced for the primary compute - +With the risk of location failure significantly reduced for the primary compute capacity, the requirements for a second Region can be evaluated based on business requirements. You can rapidly deploy required capacity in the same or different Region with AWS. Idle hardware is no longer an issue. Data backups can be stored on Amazon Simple Storage Service (Amazon S3) in a single AWS Region or in multiple AWS Regions by leveraging cross-Region replication. This architecture can be simplified and be made readily available (Figure 6). @@ -94,0 +95,2 @@ With the risk of location failure significantly reduced for the primary compute + +