Question 18653 in Amazon Web Sevices Question posted in
The official Amazon Web Services documentation can be found here.

AWS ELB returns status 504 after 10 seconds – Amazon Web Sevices

I’m getting 504 status code returns when requesting my load balancer, it then transfers the request to a fargate container.

This happens when launching simultaneous calls, some return 200, some 504.

I tried raising the Idle timeout to 60 seconds in the UI as well as in the aws cli but my requests keep timing out after 10 seconds.

Is this normal behavior ? Is their another way to raise this threshold ?

Thanks

Tags:

2

Answers


  1. 0

    Seems more a connection issue between the ALB and some of the instances, that causes an intermittent Gateway Timeout.

    Check if the subnets where the instances are deployed are equally configured and, if you use a Network Load Balancer, enable Cross-Zone Load Balancing.

    Login or Signup to reply.
  2. 0

    504 Gateway Timeout means that the ALB couldn’t reach the backend, this is also quoted here: "The load balancer failed to establish a connection to the target before the connection timeout expired (10 seconds)."

    Raising the timeout (which is an idle connection timeout) has no effect. Please try to troubleshoot the connection between the ALB and the Fargate Container.
    The first and best check is to see if the TargetGroup is healthy.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search