The previous sections discussed the Route Table Scenario when the client is located within the same VPC as the target node. However, if the client node is located within another VPC or located in an on-premise environment (connected to AWS via Direct Connect or VPN), the route table scenario cannot be used to specify the active target node. In this case Route53 may be used to route client traffic to the active target node.

The Route53 Recovery Kit (provided as part of LifeKeeper) can update the DNS entry allowing the client to connect to the active node as long as it can connect to the node via either VPC peering or Direct Connect.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment