- Newest
- Most votes
- Most comments
Hello,
I think you need to set the health check path of your application on the ELB properly which could be the reason for your issue.
Thanks
We have set that also and I can see it is being hit periodically on the application logs. But still no luck :)
The issue has been solved. There is one configuration of process in Elastic BeanStalk where we need to define the port on which our application is running . This port configuration was wrong and after setting it up correctly, the server works properly and health check also become green.
Please can you provide details of the security groups for the ALB and EC2s along with the health check settings
For this EC2 instance, we are using one auto scaling group. Inside that auto scaling group, we are having one security group which have the below configuration as inbound and outbound.
Inbound Rules 1:
IP version: Type: HTTP Protocol: TCP Port Range: 80
Inbound Rules 2:
IP version: Type: All Traffic Protocol: All Port Range: All
Inbound Rules 3:
IP version: Ipv4 Type: All Traffic Protocol: All Port Range: All
Outbound Rules 1:
IP version: Ipv4 Type: All Traffic Protocol: All Port Range: All
My understanding is that issue is not due to security rules.
The issue has been solved. There is one configuration of process in Elastic BeanStalk where we need to define the port on which our application is running . This port configuration we wrong and after setting it up correctly, the server works properly and health check also become green.
Relevant content
- asked 5 months ago
- asked 3 months ago
- asked 3 months ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 20 days ago
The issue has been solved. There is one configuration of process in Elastic BeanStalk where we need to define the port on which our application is running . This port configuration we wrong and after setting it up correctly, the server works properly and health check also become green.