AWS directconnect documentation change
Summary
Updated product name from 'AWS Direct Connect gateways' to 'Direct Connect gateways' in title and replaced 'AWS Direct Connect location' with 'Direct Connect location'.
Security assessment
Changes are limited to product name standardization. No alterations to security controls, prefix validation logic, or access policies.
Diff
diff --git a/directconnect/latest/UserGuide/allowed-to-prefixes.md b/directconnect/latest/UserGuide/allowed-to-prefixes.md index deee4b474..981bdc8f1 100644 --- a//directconnect/latest/UserGuide/allowed-to-prefixes.md +++ b//directconnect/latest/UserGuide/allowed-to-prefixes.md @@ -7 +7 @@ Virtual private gateway associationsTransit gateway associationsExample: Allowed -# Allowed prefixes interactions for AWS Direct Connect gateways +# Allowed prefixes interactions for Direct Connect gateways @@ -70 +70 @@ Consider the configuration where you have instances in two different AWS Regions - * A transit virtual interface from the on-premises location and the AWS Direct Connect location. + * A transit virtual interface from the on-premises location and the Direct Connect location.