AWS cloud-map documentation change
Summary
Added detailed CLI examples for VPC association authorization in shared DNS namespaces
Security assessment
The change adds concrete CLI examples for securely configuring cross-account VPC associations in Cloud Map. While this relates to security configuration best practices (proper authorization for resource sharing), there's no indication it addresses a specific security vulnerability.
Diff
diff --git a/cloud-map/latest/dg/sharing-namespaces.md b/cloud-map/latest/dg/sharing-namespaces.md index b3117c70e..e7f16658b 100644 --- a//cloud-map/latest/dg/sharing-namespaces.md +++ b//cloud-map/latest/dg/sharing-namespaces.md @@ -53 +53,9 @@ This topic explains how to share resources that you own, and how to use resource - * For service discovery using DNS queries in a shared private DNS namespace, the namespace owner will need to call `CreateVPCAssociationAuthorization` with the `Id` of the private hosted zone associated with the namespace. The namespace consumers will need to call `AssociateVPCWithHostedZone` with the `Id` of the private hosted zone. For more information, see [CreateVPCAssociationAuthorization](https://docs.aws.amazon.com/Route53/latest/APIReference/API_CreateVPCAssociationAuthorization.html) and [AssociateVPCWithHostedZone](https://docs.aws.amazon.com/Route53/latest/APIReference/API_AssociateVPCWithHostedZone.html) in the _Route 53 API Reference_. + * For service discovery using DNS queries in a shared private DNS namespace, the namespace owner will need to call `create-vpc-association-authorization` with the ID of the private hosted zone associated with the namespace and the consumer's VPC. + + aws route53 create-vpc-association-authorization --hosted-zone-id Z1234567890ABC --vpc VPCRegion=us-east-1,VPCId=vpc-12345678 + +The namespace consumer will need to call `AssociateVPCWithHostedZone` with the ID of the private hosted zone. + + aws route53 associate-vpc-with-hosted-zone --hosted-zone-id Z1234567890ABC --vpc VPCRegion=us-east-1,VPCId=vpc-12345678 + +For more information, see [Associating an Amazon VPC and a private hosted zone that you created with different AWS accounts](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-associate-vpcs-different-accounts.html) in the _Route 53 API Reference_.