hi i'm yael and i'm a solution architect
with AWS today i want to walk you
through how you can configure failover
with amazon route 53 health checks and
s3 bucket let's get started already son
into a SS management console now let's
go to networking and pick route 53 i
just as you can see here I already have
a hostage on which is my domain in this
video I'm going to create an Amazon s3
bucket creator check to monitor the
endpoint and finally create the failover
record between the main endpoints in
this case my Z distance and the s3
bucket now let's move on to the s3
console so I click on services I go to
storage as free when you want to create
a failover endpoint with Amazon s3
you need to make sure that the day the
name of s3 bucket is the same name as
the record in our case our record is
going to be my own domain and s3 bucket
must have the same name so I'm going to
create the bucket with my own domain I'm
going to select the region not Virginia
and click on create now that we have
created the s3 bucket let's go and
select it we click on properties and we
are going to enable the esthetic website
hosting we click on it use this bad cat
to our website click it in the index
document we live index dot HTML and we
click on save now that our spirit market
is going to be a static website hosting
we are going to move to objects and we
are gonna
Clawd our index dot HTML we hit on add
file I click on index dot HTML and open
I click Next I click on manage Pub
public permissions and I click on read
for everyone
next next upload now that we created
there the s3 bucket and we enable the
web hosting we are going to move to
route 53 console so I select I go under
networker and select route 53 here I'm
going to create a health check so I'm
going to click on health checks click on
create health check so I'm going to put
here the name of my domain as a name for
the health check a water monitor I'm
going to select an endpoint because we
are going to monitor an ec2 instance
next I select that P address tube and
put there the others of my ec2 instance
for political I select HTTP because
milestones is listening on port 80
if successful route 53 submits an HTTP
request and waits for a HTTP status code
of 200 or greater and less than 400 I
leave my path is empty because I want to
indicate any landing page now I'm going
to expand the advanced configuration I
make sure that the request interval is
30 seconds and gonna change the failure
threshold from 3 to 2 now I'm going to
click Next I'm gonna leave no because I
don't want to receive any notification
when the health check fails and then I
click on create and check now that I
created the health check I'm going to
move back to the hostel
son I open my hosted son I'm going to
create my record set so I click on
create record set I'm going to put www
type that we live a and then in the
value I'm gonna put the IP address of my
ec2 instance averting policy I'm going
to select failover although there are
different ones but well in this case
we're not going to look we're gonna see
how failover works in the fellow record
type is primary because I'm as my first
choice my DNS needs to redirect to my
ec2 instance and then I I click on
associated with health check I'm going
to select the health checks that we
already created and then I click on
create after creating the primary
endpoint it is time to create the
failover endpoint in this case our s3
bug so I click on create record set and
the type www
in the type I leave a an alias I select
yes
alias a records are a special feature of
route 53 that allow you to point your
record to a nativist resource like an s3
bucket or an elastic load balance a
return that I create the addresses of
the resource without using cname this is
very useful when you are using a diverse
resources with your app X domain you can
find out more about this below now I can
select my s3 bucket from the drop-down
menu for routing policy I select
failover and for the type and select
secondary because this is my secondary
my failover endpoint I do not associate
this endpoint with any health check
because it is not necessary s3 is a
highly available and this second
end point now I click create now I move
to the terminal and let's use the Q see
if my instance elastic IP address is
returning correctly when I try to
resolve my record I can see their IP
address is written correctly now I move
to the browser to try and open our
website as you can see here the index
status returning is the one from the ec2
instance now that they see that it is
returning correctly I stop my web server
on my instance so my hijack start
failing now I am back to AWS management
console I'm going to go to services
compute in situ running instances from
here I'm going to stop the web server in
order for the hell check to start
failing instance take stop yes stop now
I'm back to the browser I'm going to
refresh the page after waiting for a few
seconds for the failover to happen I'm
going to load the page and here as you
can see the page changed in this point
to the s3 bucket thanks for watching and
happy computing from all of us here at
AWS