AWS sap documentation change
Summary
Reorganized documentation structure, moved/added AWS Direct Connect resiliency note, updated routing configuration steps, and adjusted image placements
Security assessment
The change adds a note recommending AWS Direct Connect for business-critical workloads and links to resiliency documentation. While this relates to network reliability (a security-adjacent concern), there is no direct evidence of addressing a specific security vulnerability. The recommendation supports availability, which is part of security best practices but isn't explicitly tied to a security flaw.
Diff
diff --git a/sap/latest/sap-hana/sap-oip-configuration-steps-for-aws-transit-gateway.md b/sap/latest/sap-hana/sap-oip-configuration-steps-for-aws-transit-gateway.md index 00ece2b83..1b7f77920 100644 --- a//sap/latest/sap-hana/sap-oip-configuration-steps-for-aws-transit-gateway.md +++ b//sap/latest/sap-hana/sap-oip-configuration-steps-for-aws-transit-gateway.md @@ -22,2 +18,0 @@ This section includes high-level steps necessary to understand overlay IP addres - - @@ -26,3 +21 @@ This section includes high-level steps necessary to understand overlay IP addres - 1. Do one of the following, depending on your connection: - - + @@ -29,0 +23 @@ This section includes high-level steps necessary to understand overlay IP addres + 3. Do one of the following, depending on your connection: @@ -38,0 +33 @@ When you associate a Transit Gateway with a Direct Connect gateway, you specify +**Note:** AWS Direct Connect is recommended for business critical workloads. See [Resilience in AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/disaster-recovery-resiliency.html) to learn about resiliency at the network level. @@ -42 +36,0 @@ When you associate a Transit Gateway with a Direct Connect gateway, you specify -**Note:** AWS Direct Connect is recommended for business critical workloads. See [Resilience in AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/disaster-recovery-resiliency.html) to learn about resiliency at the network level. @@ -44 +38 @@ When you associate a Transit Gateway with a Direct Connect gateway, you specify -## Step 2\. Configure routing for AWS and corporate networks +## Step 2. Configure routing for AWS and corporate networks @@ -64,5 +57,0 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is - - - - - @@ -71,4 +60 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is - 1. To route the outgoing traffic from VPCs where SAP instances are running to private IP addresses of another VPC where SAP instances are running attached to same Transit Gateway, create entries in the **route tables associated with these VPC subnets**. The target of these routes is AWS Transit Gateway. In the following VPC of production SAP system route table example, the non-production SAP VPC (third entry) and corporate network (fourth entry) are routed to the Transit Gateway. - - - + @@ -76 +62 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is - + 2. To route the outgoing traffic from VPCs where SAP instances are running to private IP addresses of another VPC where SAP instances are running attached to same Transit Gateway, create entries in the **route tables associated with these VPC subnets**. The target of these routes is AWS Transit Gateway. In the following VPC of production SAP system route table example, the non-production SAP VPC (third entry) and corporate network (fourth entry) are routed to the Transit Gateway. @@ -80,2 +66 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is - 1. In the VPC of the non-production SAP system, to route the outgoing traffic from the overlay IP address, create entries in the route tables with Transit Gateway as the target. In the following VPC of non-production SAP system route table example, the destination is the overlay IP range and the target is Transit Gateway. - + @@ -82,0 +68 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is + 3. In the VPC of the non-production SAP system, to route the outgoing traffic from the overlay IP address, create entries in the route tables with Transit Gateway as the target. In the following VPC of non-production SAP system route table example, the destination is the overlay IP range and the target is Transit Gateway. @@ -83,0 +70 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is +**Figure 5: VPC of non-production SAP system route table: Outgoing traffic from overlay IP address routed to Transit Gateway** @@ -87,3 +74 @@ When you create a Transit Gateway attachment to a VPC, the propagation route is -**Figure 5: VPC of non-production SAP system route table: Outgoing traffic from overlay IP address routed to Transit Gateway** - - 1. Configure routing from corporate devices to Amazon VPC IP addresses. + 4. Configure routing from corporate devices to Amazon VPC IP addresses.