2

I'm trying to deploy backend application to the AWS Fargate using cloudformation templates that I found. When I was using the docker image training/webapp I was able to successfully deploy it and access with the externalUrl from the networking stack for the app.
When I try to deploy our backend image I can see the stacks are deploying correctly but when I try to go to the externalUrl I get 503 Service Temporarily Unavailable and I'm unable to see it... Another thing that I've noticed is on the docker hub I can see that the image is continuously pulled all the time when the cloudformation services are running...

The backend is some kind of maven project I don't know exactly what but I know that locally its working but to get it up running the container with this backend image takes about 8 minutes... I'm not sure if this affects the Fargate ?? Any Idea how to get it working ?

Mugetsu
  • 1,739
  • 2
  • 20
  • 41
  • Hi Mugetsu, I have the same problem as you (and the same log that my port is unhealty). How did you solve this ? – lads Aug 13 '18 at 06:44
  • 3
    @lads Hi, I don't know if it will help you much but I managed to find the solution by going through the events errors. > ecs -> cluster -> service -> events. Basically, my problem was with the health checks for the deployed image. I had to increase the time for the health check because my image was deploying kinda long and increasing timing for about 30 sec was enough to get it up and running. – Mugetsu Aug 14 '18 at 07:39
  • Thanks Mugetsu. That solved my problem too. – lads Aug 14 '18 at 08:38
  • @lads can you please mention the parameters? I am getting the same error. – Parth Trivedi Feb 13 '19 at 12:36

2 Answers2

8

It sounds like you need to find the actual error that you're experiencing, the 503 isn't enough information. Can you provide some other context?

I'm not familiar with fargate but have been using ecs quite a bit this year and I generally would find that by going to (on the dashboard) ecs -> cluster -> service -> events. The events tab gives more specific errors as to what is happening.

My ecs deployment problems are generally summarized into

  1. the container is not exposing the same port as is in the definition, this could be the case if you're deploying from a stack written by someone else.
  2. the task definition memory/cpu restrictions don't grant enough space for the application and it has trouble placing (probably a problem with ecs more than fargate but you never know.)
  3. Your timeout in the task definition is not set to 8 minutes: see this question, it has a lot of this covered
  4. Your start command in the task definition does not work as expected with the container you're trying to deploy

If it is pulling from docker hub continuously my bet would be that it's 1, 3 or 4, and it's attempting to pull the image over and over again.

Datise
  • 3,683
  • 2
  • 11
  • 12
  • this is some logs from service events https://pasteboard.co/HfOQYpt7.png – Mugetsu Apr 09 '18 at 13:23
  • huzzah! when you see health check failed its usually either the startup takes to long or the port is misconfigured. Glad it worked out. – Datise Apr 12 '18 at 19:21
1

Try adding a Health check grace period of 60 by going to ECS -> cluster -> service -> update Network Access section.

Miguel Carvalhais Matos
  • 1,113
  • 2
  • 13
  • 21