Elastic Beanstalk: Configuration panel broken?

0

Everytime I visit the Configuration page for my eb environment I get the following error:

Invalid option value: '12.9' (Namespace: 'aws:rds:dbinstance', OptionName: 'DBEngineVersion'): Engine Version 12.9 not supported for postgres db (2)

I've never seen this error before so I'm not sure what to do.

Looking around google, I thought to set the configuration manually using eb config and then applying:

aws:rds:dbinstance:
  ~ other settings ~
  DBEngineVersion: '12.14'

However, doing that gives me a new error: ERROR: ServiceError - Configuration validation exception: RDS DB Engine Version option setting is not allowed to be changed

I've even tried to apply the configuration through .ebextensions but that hasn't worked either. Deployments are running just fine as well as the RDS instance. There are no pending updates/maintenance for the RDS and the application runs smoothly without any errors.

I have noticed something though, on the configuration page of the EB environment, clicking Review Changes will return a page showing the "changed values" (even though nothing was changed) (image attached.) The configuration page is also broken, values are not being prefilled etc. I'm super confused and this is becoming a massive headache for our team as we cannot update the configuration through the console (which is our current option).

1 Answer
0

Hi, even though your option is console, I would suggest you to execute a few EB CLI commands in the hope to obtain additional error messages pointing to the root cause:

  1. aws elasticbeanstalk describe-events --environment-name my-env
  2. aws elasticbeanstalk describe-environment-health --environment-name my-env --attribute-names All
  3. aws elasticbeanstalk describe-environments --environment-names my-env
  4. aws elasticbeanstalk describe-applications

For all details, see https://awscli.amazonaws.com/v2/documentation/api/latest/reference/elasticbeanstalk/describe-environment-health.html

Such commands may provide more details than the console on the root cause of your problem. In particular, describe-events may help you spot the moment where it started with a corresponding event.

Best,

Didier

profile pictureAWS
EXPERT
answered 9 months ago
  • Thanks, Didier! I'll try with the commands and let you know! Much appreciated :)

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