Will Route53 Private Hosting Network Work on AWS VPC Peering
Consider the following scenario.
I have a bunch of appliances that serve my production environment (RDS, Mongo, Cache, Search, etc.).
On the other hand, I have 2 more app environments (say Legacy and NewGen ). They each have their own deployments and are in their own VPC.
I wish both of my Legacy and NewGen could "talk" to my VPC appliances. This is what the VPC is peering for.
What I would also like to do is that in VPC devices to create a private hosting zone some rds.comp.com or cache.comp.com will be mapped to their designated instances / services and calls to rds can be made. comp.com or cache.comp.com from my VPC Legacy or NewGen .. p>
Before I get this, I would like to know if what I am asking is possible or not.
Thank.
source to share
Yes, your scenario is directly supported by Amazon Route 53 Private Hosted Zones .
A closed zone is a container that contains information about how you want to route traffic for a domain and its subdomains within one or more Amazon virtual private clouds (Amazon VPCs).
Thus, a private hosting zone can be set up between VPC Legacy and NewGen. A resource record in a private zone comp.com
can be associated with both VPCs. A DNS query in each VPC for a resource returns the RR associated with the zone.
source to share