- Newest
- Most votes
- Most comments
It seems there might be a synchronization issue between the AWS Elastic Beanstalk console and the actual settings in your CloudFormation stack and resources. This could potentially be a bug, but before concluding that, it's recommended to troubleshoot to confirm the settings and to see if there's an explanation for the discrepancy.
You could use AWS Systems Manager to troubleshoot your Elastic Beanstalk environments, as it provides predefined Automation runbooks for Elastic Beanstalk. One such document is **AWSSupport-TroubleshootElasticBeanstalk**
, which checks various components of your environment, including the Auto Scaling groups and CloudFormation stack, and provides troubleshooting steps and recommendations
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/troubleshooting-systems-manager.html
If after troubleshooting, you find that the discrepancies persist without a clear explanation, I would open a support case for further investigation as it might indeed be a bug or a display issue within the AWS Management Console.
Thanks for pointing out! I tried to troubleshoot using the runbook you mentioned. All checks reported success, except CheckEc2Health - but this is for my understanding due to a flaw in the respective script. I get
for B in H.describe_target_health(TargetGroupArn=N['DefaultActions'][0]['TargetGroupArn'])['TargetHealthDescriptions']:
KeyError: 'TargetGroupArn'
Actually, that's correct, because it happens when examining all listeners, and the port http:80 listener just redirects to https:443, hence has no target group. Of course, I'm not willing to change the configuration itself.
For me, it doesn't look like there is a problem in the environment.
Relevant content
- asked a year ago
- Accepted Answerasked 9 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- How do I customize my nginx configuration to modify the "client_max_body_size" in Elastic Beanstalk?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago