AWS prescriptive-guidance documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in connectivity options and corrected grammar in Local Zones connectivity section
Security assessment
Purely cosmetic updates to service naming conventions. No security configurations, vulnerabilities, or encryption methods were altered. The Direct Connect functionality remains identically documented.
Diff
diff --git a/prescriptive-guidance/latest/hybrid-cloud-best-practices/requirements.md b/prescriptive-guidance/latest/hybrid-cloud-best-practices/requirements.md index 054d15b51..a06f3cc59 100644 --- a//prescriptive-guidance/latest/hybrid-cloud-best-practices/requirements.md +++ b//prescriptive-guidance/latest/hybrid-cloud-best-practices/requirements.md @@ -34 +34 @@ Before you follow this guide, work with your AWS account team or AWS Partner to - * Option 1: An AWS Direct Connect link from your data center to the [AWS Direct Connect point of presence (PoP)](https://aws.amazon.com/directconnect/locations/) that's closest to the Local Zone. For more information, see [Direct Connect](https://docs.aws.amazon.com/local-zones/latest/ug/local-zones-connectivity-direct-connect.html) in the Local Zones documentation. + * Option 1: An Direct Connect link from your data center to the [Direct Connect point of presence (PoP)](https://aws.amazon.com/directconnect/locations/) that's closest to the Local Zone. For more information, see [Direct Connect](https://docs.aws.amazon.com/local-zones/latest/ug/local-zones-connectivity-direct-connect.html) in the Local Zones documentation. @@ -68 +68 @@ For additional connectivity options, see the [Local Zones documentation](https:/ - * Local Zones don't support AWS Transit Gateway. Instead, connect to the Local Zone by using a AWS Direct Connect Private virtual interface (VIF). + * Local Zones don't support AWS Transit Gateway. Instead, connect to the Local Zone by using a Direct Connect Private virtual interface (VIF).