AWS efs documentation change
Summary
Removed 'addresses' from 'private Internet Protocol version 4 (IPv4)' description in VPC peering documentation
Security assessment
Change simplifies technical phrasing about IPv4 usage in VPC peering without modifying security implications. No evidence of addressing vulnerabilities or enhancing security documentation.
Diff
diff --git a/efs/latest/ug/manage-fs-access-change-vpc.md b/efs/latest/ug/manage-fs-access-change-vpc.md index 67d17c53e..992acd73c 100644 --- a//efs/latest/ug/manage-fs-access-change-vpc.md +++ b//efs/latest/ug/manage-fs-access-change-vpc.md @@ -22 +22 @@ You can mount the EFS file system from these targets: -A _VPC peering connection_ is a networking connection between two VPCs that enables you to route traffic between them. The connection can use private Internet Protocol version 4 (IPv4) addresses. For more information on how Amazon EFS works with VPC peering, see [Mounting EFS file systems from another AWS account or VPC](./manage-fs-access-vpc-peering.html). +A _VPC peering connection_ is a networking connection between two VPCs that enables you to route traffic between them. The connection can use private Internet Protocol version 4 (IPv4). For more information on how Amazon EFS works with VPC peering, see [Mounting EFS file systems from another AWS account or VPC](./manage-fs-access-vpc-peering.html).