Consider the following scenario.
I have a bunch of appliances that serve my production environment (RDS, Mongo, Cache, Search etc...).
On the other side I have 2 more application environments (Lets say, Legacy and NewGen ). Each has its own deployments, and resides in its own VPC.
I would like both my Legacy and NewGen to be able to "talk" with my appliances VPC. Thats what the VPC peering is for.
What I would also like to do is, with in the appliances VPC to create a private hosted zone that will map some rds.comp.com or cache.comp.com routes to their designated instances/services and be able to make calls to rds.comp.com or cache.comp.com from my Legacy or NewGen VPCs .
Before I get into this I would like to know if what i am asking is possible or not.
Thanks.
Yes, your scenario is directly supported by Amazon Route 53 Private Hosted Zones .
A private hosted zone is a container that holds information about how you want to route traffic for a domain and its subdomains within one or more Amazon Virtual Private Clouds (Amazon VPCs).
In this way, a Private Hosted Zone can be setup between the Legacy and NewGen VPCs. A resource record in the private zone of comp.com
can be associated to both VPCs. A DNS query in each VPC for a resource will return the RR associated in the zone.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.