AWS efs documentation change
Summary
Added documentation about DNS limitations and Route 53 integration for cross-VPC mounting
Security assessment
Clarifies operational requirements for cross-VPC access but doesn't address security vulnerabilities or document security features
Diff
diff --git a/efs/latest/ug/mount-fs-different-vpc.md b/efs/latest/ug/mount-fs-different-vpc.md index ae944c1ed..7d74841f8 100644 --- a//efs/latest/ug/mount-fs-different-vpc.md +++ b//efs/latest/ug/mount-fs-different-vpc.md @@ -10,0 +11,4 @@ When you use a VPC peering connection or transit gateway to connect VPCs, Amazon +You can't use DNS name resolution for EFS mount points in another VPC. To mount your EFS file system, use the IP address of the mount points in the corresponding Availability Zone. + +Alternatively, you can use Amazon Route 53 as your DNS service. In Route 53, you can resolve the EFS mount target IP addresses from another VPC by creating a private hosted zone and resource record set. For more information on how to do so, see [Working with private hosted zones](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html) in the _Amazon Route 53 Developer Guide_. +