Answer by Ashoka for AWS:ELB health is failing or not available for all...
I have created an end point in my spring boot application as follows and deployed app to AWS Elastic Beanstalk. But still ELB health check fails.package com.sme.controller;import...
View ArticleAnswer by Sumit Kumar for AWS:ELB health is failing or not available for all...
create an endpoint for health check and send 200 status code.İf you want to use another path you should modify load balancer.example: "default 80 HTTP /" to default 80 HTTP "/ping"
View ArticleAnswer by anderwald for AWS:ELB health is failing or not available for all...
I had the same problem as you and followed Gökhan Ayhan's approach.Modifying the load balancer from "default 80 HTTP /" to "default 80 HTTP /healthCheck" did not help, but you can also set the expected...
View ArticleAnswer by Gökhan Ayhan for AWS:ELB health is failing or not available for all...
Application load balancer(a part of ELB) looking default "/" endpoint for health check and ELB gets 404 status code so ElasticBeanstalk instances turn red. You should create an endpoint for health...
View ArticleAWS:ELB health is failing or not available for all instances
Our ELB is intermittently failing health checks on instances and throws errors "Environment health has transitioned from Ok to Warning. 2 out of 2 instances are impacted. See instance health for...
View Article
