AWS outposts documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for service name consistency
Security assessment
Purely a branding/naming convention update without any security implications. No changes to technical requirements or security controls.
Diff
diff --git a/outposts/latest/install-server/outposts-requirements.md b/outposts/latest/install-server/outposts-requirements.md index 7c349cfbe..273d26b2a 100644 --- a//outposts/latest/install-server/outposts-requirements.md +++ b//outposts/latest/install-server/outposts-requirements.md @@ -97 +97 @@ TCP | 1024-65535 | Service Link IP | 443 | Outposts Registration endpoints -You can use an AWS Direct Connect connection or a public internet connection to connect the Outpost back to the AWS Region. For Outposts 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 Outposts service link connectivity, you can use NAT or PAT at your firewall or edge router. Service link establishment is always initiated from the Outpost.