AWS secretsmanager documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Change only modifies branding terminology (removes 'AWS' prefix from 'Direct Connect'). No security implications or new security guidance introduced.
Diff
diff --git a/secretsmanager/latest/userguide/vpc-endpoint-overview.md b/secretsmanager/latest/userguide/vpc-endpoint-overview.md index dc604a889..acb4774ba 100644 --- a//secretsmanager/latest/userguide/vpc-endpoint-overview.md +++ b//secretsmanager/latest/userguide/vpc-endpoint-overview.md @@ -9 +9 @@ Create an endpoint policyShared subnets -We recommend that you run as much of your infrastructure as possible on private networks that are not accessible from the public internet. You can establish a private connection between your VPC and Secrets Manager by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Secrets Manager APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Secrets Manager APIs. Traffic between your VPC and Secrets Manager does not leave the AWS network. For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html) in the _Amazon VPC User Guide_. +We recommend that you run as much of your infrastructure as possible on private networks that are not accessible from the public internet. You can establish a private connection between your VPC and Secrets Manager by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Secrets Manager APIs without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Secrets Manager APIs. Traffic between your VPC and Secrets Manager does not leave the AWS network. For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html) in the _Amazon VPC User Guide_.