2 Answers
- Newest
- Most votes
- Most comments
0
Hi there ,
It had happened due to system status check failure.
I would ask you to make use of Autoscaling group behind ELB so that these events can be handled automatically
0
SatyamSinha-AWS wrote:
Hi there ,
It had happened due to system status check failure.
I would ask you to make use of Autoscaling group behind ELB so that these events can be handled automatically
as in post https://forums.aws.amazon.com/thread.jspa?messageID=886201󘖹:
We have the same situation , and looking at the situation during the 504 errors they happens when the Target group contains one or more instances in draining state.
I think ALB needs some time to understand that an instance is not available. But this is not the right behaviour
answered 6 years ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 months ago