MemberMarch 15, 2021 at 2:25 pm
Regarding the question:
A financial company has several accounting applications that are hosted in AWS and used by thousands of small and medium businesses. As part of its Business Continuity Plan, the company is required to set up an automatic DNS failover for its applications to a disaster recovery (DR) environment. They instructed their DevOps team to configure Amazon Route 53 to automatically route to an alternate endpoint when their primary application stack in us-west-1 region experiences an outage or degradation of service.
What steps should the team take to satisfy this requirement?
- Set up health checks in Route 53 for non-alias records to each service endpoint. Configure the network access control list and the route table to allow Route 53 to send requests to the endpoints specified in the health checks.
Why non-alias record is used for the secondary failover record type in this case? Is it because of the “alternate endpoint” which is not mentioned to be in AWS?
AdministratorMarch 20, 2021 at 12:54 am
Thanks for posting your question.
An Alias record in the context of Route53 maps a domain name to an AWS Resource endpoint. A non-alias record can resolve a domain name to another domain or to a stable IP address.
In the scenario, the alternate endpoint was assumed to be a custom endpoint. Note that both records can be used as failover targets.
Let me know if this answers your question.
Log in to reply.