AWS efs documentation change
Summary
Updated terminology from 'AWS VPN' to 'Site-to-Site VPN' in VPC endpoint connectivity context.
Security assessment
Terminology clarification with no impact on security functionality or documentation.
Diff
diff --git a/efs/latest/ug/efs-vpc-endpoints.md b/efs/latest/ug/efs-vpc-endpoints.md index d99942963..7a407b15a 100644 --- a//efs/latest/ug/efs-vpc-endpoints.md +++ b//efs/latest/ug/efs-vpc-endpoints.md @@ -11 +11 @@ To establish a private connection between your virtual private cloud (VPC) and t -Interface VPC endpoints are powered by AWS PrivateLink, a feature that enables private communication between AWS services using private IP addresses. To use AWS PrivateLink, create an interface VPC endpoint for Amazon EFS in your VPC using the Amazon VPC console, API, or CLI. Doing this creates an elastic network interface in your subnet with a private IP address that serves Amazon EFS API requests. You can also access a VPC endpoint from on-premises environments or from other VPCs using AWS VPN, Direct Connect, or VPC peering. To learn more, see [Connect your VPC to services using AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/userguide/endpoint-services-overview.html) in the _Amazon VPC User Guide_. +Interface VPC endpoints are powered by AWS PrivateLink, a feature that enables private communication between AWS services using private IP addresses. To use AWS PrivateLink, create an interface VPC endpoint for Amazon EFS in your VPC using the Amazon VPC console, API, or CLI. Doing this creates an elastic network interface in your subnet with a private IP address that serves Amazon EFS API requests. You can also access a VPC endpoint from on-premises environments or from other VPCs using Site-to-Site VPN, Direct Connect, or VPC peering. To learn more, see [Connect your VPC to services using AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/userguide/endpoint-services-overview.html) in the _Amazon VPC User Guide_.