High Availability and Route53 Configuration for AWS EC2 Instances

Achieving High Availability for AWS EC2 Instances and Configuring Route53

Prev Question Next Question

Question

Your company is planning to set up applications over the internet with the following aspects. · 2 Applications, each with its own domain name · Each application will have EC2 Instances as Web servers You need to ensure High Availability for the servers and also configure Route53

How would you achieve this? Choose 2 answers from the options given below.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer - B and C.

Since 2 domains are required, and these are Web servers that most probably will need to be exposed to the Internet, you need to define 2 separate public hosted zones and an ELB.Options A and D are incorrect since private zones and ELBs will not allow access to the resources from the Internet.

For more information on working with Hosted Zones, please refer to the below URL.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/AboutHZWorkingWith.html

To ensure high availability for the web servers and configure Route 53 for the two applications, the following steps can be taken:

  1. Create EC2 instances: Launch two EC2 instances in two different availability zones (AZs) for each application. This will ensure that if one AZ goes down, the other AZ will keep the application up and running. You can create an Auto Scaling group for each application that automatically creates and terminates EC2 instances based on demand.

  2. Create Elastic Load Balancer (ELB): Create an Elastic Load Balancer (ELB) for each application. An ELB is a highly available and scalable load balancer that can distribute incoming traffic across multiple EC2 instances. By using ELB, you can improve the availability and fault tolerance of your application.

  3. Configure Route 53: Configure two public hosted zones in Route 53, one for each application. Route 53 is Amazon's DNS service that allows you to manage the DNS records for your domain names. You can use Route 53 to route traffic to your ELB.

  4. Create A record sets: Create A record sets in each of the hosted zones and point them to the ELBs. This will allow users to access the web applications using their domain names.

  5. Enable Health Checks: Enable health checks for the ELBs. Route 53 can monitor the health of your web servers by sending requests to the ELBs. If a web server fails the health check, Route 53 will automatically redirect traffic to the healthy instances.

  6. Optionally, configure private hosted zones: If you want to use private IP addresses to access your EC2 instances, you can create two private hosted zones in Route 53, one for each application. This will allow you to use internal DNS names to access your instances.

Therefore, the correct answers are:

B. Configure 2 public hosted zones in Route 53. C. Create a public Elastic Load Balancer.