AWS lightsail documentation change
Summary
Updated network connection reference from 'AWS Direct Connect' to 'Direct Connect'
Security assessment
Branding/nomenclature update for Direct Connect service. No security implications as the functionality and security posture of PrivateLink remains unchanged.
Diff
diff --git a/lightsail/latest/userguide/vpc-interface-endpoints.md b/lightsail/latest/userguide/vpc-interface-endpoints.md index e5b453f63..a2241b9f7 100644 --- a//lightsail/latest/userguide/vpc-interface-endpoints.md +++ b//lightsail/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointAWS CLI examplesCreate an endpoint pol -You can use AWS PrivateLink to create a private connection between your VPC and Amazon Lightsail. You can access Amazon Lightsail as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access Amazon Lightsail. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon Lightsail. You can access Amazon Lightsail as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access Amazon Lightsail.