AWS outposts documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
Purely a branding/naming convention update. No changes to security requirements, configurations, or vulnerabilities addressed.
Diff
diff --git a/outposts/latest/network-userguide/outposts-rack2ndgen-requirements.md b/outposts/latest/network-userguide/outposts-rack2ndgen-requirements.md index 4e4010fe8..85677e7ea 100644 --- a//outposts/latest/network-userguide/outposts-rack2ndgen-requirements.md +++ b//outposts/latest/network-userguide/outposts-rack2ndgen-requirements.md @@ -235 +235 @@ TCP | 1025-65535 | Outpost service link /24 | 443 | Outpost Region's public -You can use an AWS Direct Connect connection or a public internet connection to connect the Outpost back to the AWS Region. For Outpost service link connectivity, you can use NAT or PAT at your firewall or edge router. Service link establishment is always initiated from the Outpost. +You can use an Direct Connect connection or a public internet connection to connect the Outpost back to the AWS Region. For Outpost service link connectivity, you can use NAT or PAT at your firewall or edge router. Service link establishment is always initiated from the Outpost.