Score:1

Can an AWS Application Load Balancer mark a service as unhealthy "early"

mx flag

I try to find out, if it is possible to configure an AWS Application Load Balancer in a way, that if the backend service responds with an error status code (e.G. 503 Service Unavailable) to a regular incoming http request, that the Application Load Balancer then marks the requested backend service as "unhealthy"? Maybe even tries a different one?

I am aware of the typical health checks that AWS Application Load Balancers do. But they only occur in specific intervals. Meaning that if in between of these intervals something goes bad, all upcoming requests until the next interval would still be routed to the already broken backend service.

I am looking for a similar behavior as it is describe for nginx and apache in this post: Load balancer to handle server errors silently

Oscar De León avatar
la flag
You can certainly configure your ALB to mark a backend service as unhealthy sooner. You simply adjust the Interval and Timeout values to something that fits your situation.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.