- Newest
- Most votes
- Most comments
Hello,
The timing is correct. 5 seconds of Timeout and 15 seconds of delay. If the health checks are failing you need to check the security group rules for the instances behind the ALB to ensure they allow traffic from the load balancer and verify that the health check path is correct and does not result in a redirect (HTTP 301 response). Increasing the "Health check grace period" for the target group will also allow more time for your services to start up before the health checks begin.
If they are instead ok you can think of reducing them by adjusting the logging level for the ALB in your EKS cluster. You can do this by modifying the
aws-load-balancer-controller
Helm chart values or the Kubernetes Ingress annotations.
Use a log aggregation service, such as Amazon CloudWatch Logs or Elasticsearch, to centralize and manage your logs more effectively.
Docs: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/target-group-health-checks.html
Relevant content
- asked a year ago
- asked 5 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago