AWS transform documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Naming convention change that doesn't affect the security posture of VPC endpoint configurations. PrivateLink security benefits remain unchanged.
Diff
diff --git a/transform/latest/userguide/vpc-interface-endpoints.md b/transform/latest/userguide/vpc-interface-endpoints.md index 0752fbaa1..6bada58b7 100644 --- a//transform/latest/userguide/vpc-interface-endpoints.md +++ b//transform/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for AWS Transform VPC endpointsPrerequisitesCreating an interface -You can establish a private connection between your VPC and AWS Transform 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 the AWS Transform console without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Traffic between your VPC and AWS Transform does not leave the Amazon network. +You can establish a private connection between your VPC and AWS Transform 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 the AWS Transform console without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Traffic between your VPC and AWS Transform does not leave the Amazon network.