Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Understand AWS Cross Region Failover
in 10 easy steps
- Ishant Kumar
Introduction
Each Amazon EC2 region is designed to be
completely isolated from the other Amazon EC2
regions. This achieves...
Amazon EC2 is hosted in multiple locations world-wide.
These locations are composed of regions and Availability Zones.
...
Amazon operates state-of-the-art, highly-available data centers. Although rare,
failures can occur that affect the availa...
In this Presentation, I’ll demonstrate the feature of AWS Route 53
which can be used for Cross Region Failover of applicat...
Step 1
Create two ec2 instances in two different regions . In our case I am
provisioning one instance in N.Virginia and ot...
### Instance in N. California
Step 2
Install httpd server on each EC2 server and create a index.html file.
# yum install httpd
# cd /var/www/html/
# vim...
Step 3
Start the httpd Server in both EC2 server.
#service httpd start
Step 4
Go to Route 53 and create health check at port 80 for both the
instances as by default httpd server works on port 8...
Step 5
Now in Route53, create a recordset in a hosted zone.
In this article I have a domain registered with name ishantkum...
Step 6
Enter the Recordset name. I created test.ishantkumar.in.
Step 7
Enter the public IPs of both the instances (one in a line only).
Set the routing policy as failover.
Step 8
Associate the health check type of one the instance which we created
in step 5.
In this Article, I am giving NVirgi...
Step 9
Test the website. (test.ishantkumar.in) . It will show you the webpage
associated with Primary Health Check. In our...
Step 10
Delete the N.Virginia’s instance and check your website.
Still we are able to see the website but this time we are getting web
page hosted in N.California Region. It shows even on...
Thanks
Looking Forward for your interest in DevOpsJourney.com
http://devopsjourney.com
Email us: mail@devopsjourney.com
Upcoming SlideShare
Loading in …5
×

Understand AWS Cross Region Failover in 10 Easy Steps

8,505 views

Published on

Understand AWS Cross Region Failover in 10 Easy Steps

Published in: Technology
  • Dating for everyone is here: ❶❶❶ http://bit.ly/2Q98JRS ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Follow the link, new dating source: ♥♥♥ http://bit.ly/2Q98JRS ♥♥♥
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Here's How YOU Can Stake Out Your Personal Claim In Our EIGHT MILLION DOLLAR GOLDMINE... ♣♣♣ https://bit.ly/2Ruzr8s
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Free Magical Healing Soundscape - Attract more abundance... clear negativity... reduce stress... sleep deeper... and bring astonishing miracles into your life... simply by listening for a few minutes each day. Get yours now. ➤➤ http://t.cn/AiuvUMl2
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • We called it "operation mind control" - as we discovered a simple mind game that makes a girl become obsessed with you. (Aand it works even if you're not her type or she's already dating someone else) Here's how we figured it out... ♥♥♥ http://t.cn/AiurDrZp
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Understand AWS Cross Region Failover in 10 Easy Steps

  1. 1. Understand AWS Cross Region Failover in 10 easy steps - Ishant Kumar
  2. 2. Introduction Each Amazon EC2 region is designed to be completely isolated from the other Amazon EC2 regions. This achieves the greatest possible fault tolerance and stability. Amazon EC2 provides multiple regions so that you can launch Amazon EC2 instances in locations that meet your requirements. For example, you might want to launch instances in Europe to be closer to your European customers or to meet legal requirements. The following table lists the regions that provide support for Amazon EC2.
  3. 3. Amazon EC2 is hosted in multiple locations world-wide. These locations are composed of regions and Availability Zones. Each region is a separate geographic area. Each region has multiple, isolated locations known as Availability Zones. Amazon EC2 provides you the ability to place resources, such as instances, and data in multiple locations. Resources aren’t replicated across regions unless you do so specifically.
  4. 4. Amazon operates state-of-the-art, highly-available data centers. Although rare, failures can occur that affect the availability of instances that are in the same location. If you host all your instances in a single location that is affected by such a failure, none of your instances would be available. All communications between regions is across the public Internet. Source : http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions- availability-zones.html
  5. 5. In this Presentation, I’ll demonstrate the feature of AWS Route 53 which can be used for Cross Region Failover of application deployed in multiple regions. For Example : One Application is deployed in N. Virginia and same in N. California so when N. Virginia goes down we’ll be having access to our application which is in N. California.
  6. 6. Step 1 Create two ec2 instances in two different regions . In our case I am provisioning one instance in N.Virginia and other one in N. California Region. ### Instance in N.Virginia
  7. 7. ### Instance in N. California
  8. 8. Step 2 Install httpd server on each EC2 server and create a index.html file. # yum install httpd # cd /var/www/html/ # vim index.html Add Contents in index.html file in order to distinguish in between the regions. —index.html in N.Virginia This Webpage is from N.Virginia Region —index.html in N.California This Webpage is from N.California
  9. 9. Step 3 Start the httpd Server in both EC2 server. #service httpd start
  10. 10. Step 4 Go to Route 53 and create health check at port 80 for both the instances as by default httpd server works on port 80. Here we are monitoring the health (service running) on the instances. wait till the status becomes healthy.
  11. 11. Step 5 Now in Route53, create a recordset in a hosted zone. In this article I have a domain registered with name ishantkumar.in in Route53. I am going to create one recordset with name test.ishantkumar.in. Select the recordset and click on Go to Record Sets.
  12. 12. Step 6 Enter the Recordset name. I created test.ishantkumar.in.
  13. 13. Step 7 Enter the public IPs of both the instances (one in a line only). Set the routing policy as failover.
  14. 14. Step 8 Associate the health check type of one the instance which we created in step 5. In this Article, I am giving NVirginiaHealthCheck as primary.
  15. 15. Step 9 Test the website. (test.ishantkumar.in) . It will show you the webpage associated with Primary Health Check. In our case web page hosted in N.Virginia Region.
  16. 16. Step 10 Delete the N.Virginia’s instance and check your website.
  17. 17. Still we are able to see the website but this time we are getting web page hosted in N.California Region. It shows even one region goes down, website is still up and running in another region.
  18. 18. Thanks Looking Forward for your interest in DevOpsJourney.com http://devopsjourney.com Email us: mail@devopsjourney.com

×