AWS - Route53 Failover Policy

-

 

"Route 53 failover" refers to a feature within Amazon Route 53, a DNS service, that allows automatic redirection of traffic to a backup server or region if the primary server or region becomes unavailable, essentially ensuring continuous website access even during outages by utilizing health checks to monitor the status of your resources and route users to the healthy endpoint.

For this post, I have 2 webservers running web application on port 80.

First, I am going to create Route53 Private Hosted Zone. 



The zone name is "labexample.com". I am making this zone as private, so that it can be accessed with AWS VPC.

Once we have the zone, we need to create Route53 health check, this is a critical piece to monitor the primary server and enabled route53 to failover if the primary server fails.




IP address to monitor is the IP address of the primary server.



Here, we are mentioning how often to monitor and failure threshold.




Next, we will create DNS record under the private hosted zone we created.

Below is the primary record. Look at the value(IP), routing policy, health check ID and fail over record type.

Failover record type, says the above IP is the PRIMARY.


Let's add secondary record.


We are done. Lets start testing using "dig" command.


We can see all the request to the domain "failover.labexample.com" goes to primary server.

Let's shutdown the primary server.


Now the traffic switch to the failover IP. Once the primary server is back online, the request falls back to the primary server.



Comments

Post a Comment

Popular posts from this blog

SRE/DevOps Syllabus

-
Image
  DEVOPS/SRE Principles. Git What is Git? Architecture of Git. Working principle of Git. Create and cloning a repo. Version control branching. Version control commit. Version control managing workflows. Git hooks. Git Reflog. Git Stash. Git Cherry Picking. Undoing changes in different states of Git. Git based terraform template management. AWS CI/CD SDLC Automation. Code Commit. Code Build. Code Deployment. Code Pipeline. Elastic Beankstalk. Code Artifact. CodeGuru. Terraform Terraform Basics. Terraform State. Working with Terraform. Terraform with AWS. Remote State. Terraform Provisioners. Terraform Import, Tainting and Debugging. Terraform Modules. Terraform Functions and Conditional Expressions. Automation using Python - AWS AWS lambda. Automating EC2 with Lambda. Automating S3 with Lambda. Automating VPC with Lambda. Cost optimization with Lambda. SNS,SQS and SES with Python. Managing and Automating AWS Security with Python. Kubernetes - CKAD Application Developer. Kubernetes A...
Read more

AWS Code Commit - CI/CD Series Part 1

-
Image
  This is a multi-part series to show how to implement a CI/CD pipeline in AWS. In this post, We will see how to use AWS Code Commit. AWS CodeCommit is a fully managed source control service that allows you to store and manage your code securely in the cloud.  It provides a private Git repository for your code and supports all Git commands and workflows. CodeCommit also integrates with other AWS services like AWS CodePipeline and AWS CodeBuild, allowing you to automate your entire software release process. This can help you streamline your development workflows and improve the overall efficiency of your team. I created a repo from AWS CodeCommit -> Create Repository. And I begin with cloning the repo locally. So that I can make changes and push it. To clone the repo click on "HTTPS" under Clone URL. I make changes to index.html file. Now push it to AWS CodeCommit. Let’s verify the changes in AWS Code commit. Changes are reflected in AWS CodeCommit. We are done with Part ...
Read more

Docker - Preventing IP overlapping

-
Image
  What is IP address overlapping? When the container IP address overlaps with another IP external, then the application running on the container is not accessible from outside due to the IP address overlapping.  NOTE: This IP address overlapping can happen on the bridge interface IP or docker container IP. Let's see how to address this IP overlapping issue on the bridge interface. I already have a running container.  root@demo:~# docker run -d --name web --network mynet1 nginx:alpine 268647e11011d513d2357ce1c81e0f48787038a83d01d028d31a5b29dbdb885b root@demo:~# docker container ls CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES 268647e11011   nginx:alpine   "/docker-entrypoint.…"   4 seconds ago   Up 3 seconds   80/tcp  ...
Read more