AWS vpc documentation change
Summary
Clarified that enabling DNS resolution for same-account VPC peering works for both same-region and cross-region connections
Security assessment
Change provides operational clarification about DNS resolution scope but contains no security-specific context or vulnerability references
Diff
diff --git a/vpc/latest/peering/vpc-peering-dns.md b/vpc/latest/peering/vpc-peering-dns.md index 9e68cdc86..e33c67dd1 100644 --- a//vpc/latest/peering/vpc-peering-dns.md +++ b//vpc/latest/peering/vpc-peering-dns.md @@ -25 +25 @@ The public IPv4 DNS hostname resolves to the private IPv4 address of the instanc - * The owner of the requester VPC must modify the requester VPC peering options, and the owner of the accepter VPC must modify the accepter VPC peering options. If the VPCs are in the same account and Region, you can enable DNS resolution for the requester and accepter VPCs at the same time. + * The owner of the requester VPC must modify the requester VPC peering options, and the owner of the accepter VPC must modify the accepter VPC peering options. If the VPCs are in the same account, you can enable DNS resolution for the requester and accepter VPCs at the same time. This works for both same-region and cross-region VPC peering connections.