[Music]
hi I'm Jenny a cloud support engineer
here at the AWS office in North Virginia
sometimes customers ask me how they can
troubleshoot the issue that an
application not bannister here's take
for instance in an ambien ECS container
is returning an unhealthy status when
you the in bridge mode I tear them in
order to pass application not a banister
here shake they need to make sure the
following is true the application in
your easiest container returns the
correct or response code by default 200
okay when the nor banister sends an HTTP
GET request to the hair shake pass the
security groups of your knot banister or
container instance appropriate
configured the target groups are the
long hairs check settings are properly
configured let me walk you through the
process first make sure the application
in your easiest container returns the
corrected response code by default 200
ok when the node manager sends an HTTP
GET request to the hairs check pass to
confirm that the application is working
as expected
log into the container instance using
SSH and perform a check manually by
following these steps Here I am already
logged into the AWS management console
this code - easiest and find the easiest
instance
so here I already create a ECS cluster
core data for collective Ford
then click ECS instance tab
we received a normal ec2 instance ID
click a we will go to ec2 management
console here we can get the public IP of
the ec2 instance
let's move to the terminal first we need
to install her if you haven't already
you can use young 4m the Linux and other
rpm based descriptions or you can use a
packet for Debian based systems here I
already insert curve next we can find
the container ID for the relevant
container by running the following
command
here we can find the output under pours
which will be similar to this take a
special note of the potion of the output
80 which is support for the local
listener and also take a note for the
corresponding container ID will reduce
it to four next step here I'm going to
copy it
next obtain the IP address of the
container by running the following
command where container ID is the
corresponding container ID you note it
is step two as you can see we get the
container IP here
next take a note of the IP address run
the following command where container IP
is IP address you obtained in previous
step and port is a local lesson abort
you noted in previous step Kurt - V HTTP
container IP and port
as you can see the command should return
200 okay or if you are using an
application not answered and have
updated your matter setting your
preferred response coding state if the
command does not return 200 okay then
your application is not listening to
HTTP traffic now let's move back over to
the console now we need to make sure the
secured groups attached to your not been
sir and container instance appropriate
configured a pistol practice is to
config to security groups one for your
container instance and another for your
not bannister make sure to check the
following we can find the security group
before you're not penser in not answer
tab go little bit down your see security
click security group
we'll see the security group for your
not been sir and for your container
instance the security group associated
with you're not answer allows or icarus
traffic to the security group associated
with your back-end instance as we can
see in outbound we created a rule next
the security group associated with your
back-end the container instance allows
or increased traffic on host reports
from the security group associated with
your not balancer as you can see here if
you are using dynamic hostile port
mapping be sure the security group
attached to the container service is
configured to allow access by FM
airports in the range three to seven six
eight to six five five three five that
are associated with the security group
attach it to your non Penzer like what I
did here and if you declare the hosts
reporter in your task a definition be
sure that declared the port is allowed
instead of the FME report range finally
we need to make sure the target groups
are the ones the hairs check settings
are properly configured to do that let's
go to the left and levitation pen and
click target group
make sure you selected the relevant to
target group pay special attention to
the following easiest specific points
for target group use new target group do
not add the targets to the target group
manually the course easiest
automatically registers and the
registers containers with the target
group for port this moved to his check
tab use the default of traffic port
choosing overwrite causes a check
traffic to be routed incorrectly thanks
for watching and happy cloud computing
from all of us here at aw
[Music]
you