AWS prescriptive-guidance documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in hybrid connectivity section
Security assessment
Terminology standardization without impact on security posture or connectivity architecture.
Diff
diff --git a/prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/solution-3.md b/prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/solution-3.md index 9191e1cfe..f92321a43 100644 --- a//prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/solution-3.md +++ b//prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/solution-3.md @@ -43 +43 @@ The diagram illustrates the following traffic flow: - 4. For hybrid connectivity between AWS and your on-premises data center (not shown in the previous diagram) use Transit Gateway, AWS Direct Connect or AWS Site-to-Site VPN with Route 53 Resolver endpoints, as shown in [solution 1](./solution-1.html) and [solution 2](./solution-2.html). + 4. For hybrid connectivity between AWS and your on-premises data center (not shown in the previous diagram) use Transit Gateway, Direct Connect or AWS Site-to-Site VPN with Route 53 Resolver endpoints, as shown in [solution 1](./solution-1.html) and [solution 2](./solution-2.html).