[Music]
hello I'm Shree a cloud Support Engineer
here at the AWS headquarters in Seattle
today I'm going to show you how to
configure geo proximity routing using
the Amazon route 53 console let's get
started
geo proximity routing let's route 53
route traffic based on the physical
distance between your users and your
resources you can adjust the bias value
to route more traffic or less to a given
resource in a region you must use route
53 traffic flow to use a geo proximity
routing policy I'm already logged in to
the AWS management console and I'll open
the route 53 console in the navigation
pane choose traffic policies choose
create traffic policy on the name policy
page specify the applicable values
choose next for start point
choose a IP address in ipv4 format as
the DNS type open the connect to menu
and then choose geo proximity rule
choose your endpoint location if you
choose custom you must enter the
locations latitude and longitude
coordinates otherwise choose the Amazon
ec2 region where your endpoint is
located such as US east Northern
Virginia bias is optional you may enter
a number or drag the slider to the bias
value you want health checks are
optional to select the health check from
the drop-down to associate with the
record and or clear the check box for
evaluated target health open the connect
to menu and then choose new endpoint for
type choose value for value enter the IP
address of your endpoint for each
additional endpoint you want to add
choose add another geo proximity
location and repeat the process we just
finished
you may click the interactive map icon
to assess to which region users in a
given geographic location will be routed
to the interactive map icon
automatically adjusts when the biased
value is changed choose create traffic
policy you can choose to create the
policy record now from the same screen
or do as follow choose skip this step in
the navigation pane choose policy
records on the policy records page
choose create policy records on the
create policy records page specify the
applicable values choose create policy
records if you want to create policy
records in another hosted zone repeat
the process we just finished now you
should see the newly created policy
record being applied now that we have
configured geo proximity routing policy
let us test f route 53 routes traffic to
the correct resource in a region to test
the DNS response using the route 53
console use test record set button
within a hosted zone to test the DNS
response in a Linux terminal use dig
version of 9.11 or later open a terminal
and use dig with the DNS name of your
traffic policy use + subnet in your
command to test routing from specific IP
address location the blest subnet is the
client subnet address with the mask in
the format of your typical IP address
thanks for watching and happy cloud
computing from all of us here at aw
[Music]
you
[Music]