AWS AWSEC2 documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in security context
Security assessment
Branding change in existing security recommendation about VPC endpoints. Does not introduce new security content.
Diff
diff --git a/AWSEC2/latest/UserGuide/interface-vpc-endpoints.md b/AWSEC2/latest/UserGuide/interface-vpc-endpoints.md index 02e1ff66b..5334e8228 100644 --- a//AWSEC2/latest/UserGuide/interface-vpc-endpoints.md +++ b//AWSEC2/latest/UserGuide/interface-vpc-endpoints.md @@ -9 +9 @@ Create an interface VPC endpointCreate an endpoint policy -You can improve the security posture of your VPC by creating a private connection between resources in your VPC and the Amazon EC2 API. You can access the Amazon EC2 API as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. EC2 instances in your VPC don't need public IP addresses to access the Amazon EC2 API. +You can improve the security posture of your VPC by creating a private connection between resources in your VPC and the Amazon EC2 API. You can access the Amazon EC2 API as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. EC2 instances in your VPC don't need public IP addresses to access the Amazon EC2 API.