AWS imagebuilder documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Terminology adjustment for consistency. No security implications or feature changes related to PrivateLink implementation.
Diff
diff --git a/imagebuilder/latest/userguide/vpc-interface-endpoints.md b/imagebuilder/latest/userguide/vpc-interface-endpoints.md index 48aebb041..2830cbe4e 100644 --- a//imagebuilder/latest/userguide/vpc-interface-endpoints.md +++ b//imagebuilder/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for Image Builder VPC endpointsCreate an interface VPC endpoint f -You can establish a private connection between your VPC and EC2 Image Builder 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 Image Builder 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 Image Builder APIs. Traffic between your VPC and Image Builder does not leave the Amazon network. +You can establish a private connection between your VPC and EC2 Image Builder 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 Image Builder 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 Image Builder APIs. Traffic between your VPC and Image Builder does not leave the Amazon network.