This website uses cookies to ensure you get the best experience.
Learn more.
A central network account owns a Transit Gateway used by production and development VPCs. Both environments need a shared DNS VPC, but must not route to each other. Which design is appropriate?
Published
- Use VPC peering to the DNS VPC and rely on transitive peering for all other traffic.
- Use different security group descriptions as the only transit routing control.
- Use separate transit route tables with deliberate shared-services routes and controlled propagation.
- Propagate every attachment into one common route table.
Comments — 0
Sign in to comment