All geek questions in one place

AWS Route 53 Redirect to Status Page

The first question, so if I'm wrong, somehow kinder.

We use Route 53 with Amazon and have our primary front-end servers behind ELB. Our application also routes all requests via HTTPS. We use the offsite status page through statuspage.io.

What I'm trying to do is if the main site is down, I would like R53 to redirect both SSL and non-SSL traffic to our status page.

I initially tried setting up a static page on S3, but still had problems with HTTPS requests made on our site.

Has anyone done this successfully? I suppose this should be possible, but it is definitely beyond my competence.

Thanks so much for your time and help.

+5
source share
2 answers

You are correct, the S3 site does not support HTTPS. However, CloudFront does [1]. What you can do is switch to CloudFront and your origin is your S3 site or your status page.io.

Steps:

  • Create a distribution and install CNAME to match your DNS records.
  • Download and associate an SSL certificate with your distribution
  • Update your failover target to be your CloudFront distribution and set it as an alias.

[1] http://aws.amazon.com/about-aws/whats-new/2014/03/05/amazon-cloudront-announces-sni-custom-ssl/

+3
source

Route53 manages a DNS that is not what you want to do (even if you change the DNS, TTL is required for synchronization). What you need to do is use a combination of auto-scaling policies and health checks . These health checks will be performed by the ELB every 30 seconds, and if two consecutive checks fail, it will mark the instance as idle and stop directing traffic to it (ELB directs traffic to your instances in a circular approach).

Having multiple instances and using autoscaling rules is the key: it will allow AWS to terminate an unhealthy instance and instead include a new instance (in the same ASG with the same AMI, etc.).

+1
source

Source: https://habr.com/ru/post/1203275/

More articles:


All Articles