hi I'm Beth no potato veneer support
chain here in Sydney sometimes customer
tell me they have set up their services
in multiple regions and we want to know
how they can immediately direct you
their traffic to the region closer to
their location I tell them that this can
easily be done with a low road 53 a
demerit has made this happen the general
routing policy which is handy when you
want
among the route 50 G to respond to the
DNS queries based on the IP location of
your Google today I'm going to show you
how this can be achieved let's get us
started
as you can see in yoga I have three
regions with their own load balancer and
each has back-end web servers in this
example I want all queries from
Australia to be routed to a web servers
behind the LDA you and queries from us
to be routed to web servers behind the
ear the US and other countries be routed
to Le Europe let's create three
different record sets first created your
location policy record for us that is
all used to year the US second create a
geolocation policy record for Australia
that is all used to Al bi Australia and
third create a default geolocation
policy record to cover the rest of the
world that is all used to envy you as
you can see I already have logging to my
AWS management console then we are going
to run 53 dashboard
how's that though and here we have to
create our records app click on record
set and in a name put like ww the type
should be a record and all yes and here
you have to choose your lv sometimes it
takes time so if it's under loading
don't worry it will come up first I'm
creating for the u.s. riches so I will
choose my LV for the US then click on
routing policy for Joe location here on
a location you have to choose your
country or continent that I will choose
North America as a continent the set ID
is a friendly ID or friendly name that
you can put for uniquely identification
like I will put us and create for the
second one create record set ww a record
all yes and then the alias target you
choose the other really which is for the
Australia
and then routing policy geolocation and
has a location choose Australia set type
as one friendly name like yes and create
and for the third one which is for this
of the world I will use I record earlier
and the ELB which gives for the European
be and for the routing policy and you
are choosing geolocation you have to
choose default and for the society as we
put you and create you can see that I
already have three different rare
records for all the countries and I will
try to test it to see what's happening
you can see that for each of them is
going like for that from the Sydney is
going to ANZ page for Europe is going to
Europe page and for the u.s. is going to
us page we can see that from each
location we get a different IP address
based on our policies and important tips
you can create non geolocation resource
record sets that have the same value for
name and type as geolocation resource
record sets thanks for watching and
happy cloud computing from all of us
here at aw