AWS Elastic Beanstalk configuration not showing correct values in AWS console

0

Hi,

I'm pretty sure I came across this problem some days before, but now I have it again. The AWS console configuration page (view and edit) for Elastic Beanstalk environments does not show the correct values of the underlying CloudFormation stack and the actual resources. In our case, the configuration dialog shows Min instances 2 and Max instances 3, while the auto-scaling group setting is Minimum capacity 1 and Maximum capacity 2. Also the AWS CLI shows wrong settings when executing

aws elasticbeanstalk describe-configuration-settings --application-name [app-name] --environment-name [env-name]

. Never experienced that before - is there something I might have missed, or is it an actual bug?

asked 6 months ago149 views
2 Answers
0

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.

AWS
Drew D
answered 6 months ago
0

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.

answered 6 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions