- Newest
- Most votes
- Most comments
Unfortunately, it is impossible to change a node major version on EBS. You need to create a new EBS env with the new node version, make sure it is working and then use swap environment domain.
Terminate the old env after you make sure the new env is working properly.
This is all explained in the following link for node 16 -> 18, but it is the same process for 18 -> 20: https://nextlinklabs.com/resources/insights/how-to-upgrade-elastic-beanstalk-in-aws-to-node-18
answered 2 years ago
Hi
check these steps to resolve the issue:
Review Environment Configuration:
Check for documentation or configuration files (YAML/JSON) associated with your environment. They might mention platform type or branch locks.
Investigate IAM Permissions:
Less likely, but verify your IAM role or user has permissions to modify the platform type and branch using the AWS IAM console or CLI. Refer to the IAM documentation for managing permissions: https://docs.aws.amazon.com/service-authorization/latest/reference/reference_policies_actions-resources-contextkeys.html
Utilize CloudTrail Logs (Optional):
If you have CloudTrail enabled for your AWS account, you can check the logs for events related to your Elastic Beanstalk environment. These logs might indicate any configuration changes or permission issues that could be causing the problem. Refer to CloudTrail documentation: https://docs.aws.amazon.com/cloudtrail/
Consult AWS Documentation:
- The AWS documentation offers resources on troubleshooting Elastic Beanstalk environments:
- Troubleshooting Elastic Beanstalk Environments: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/troubleshooting.html
- Troubleshooting and Error Handling: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/troubleshooting.html
This is a copy & paste un-related response, the real answer is that it is impossible to change a major node version in EBS
Relevant content
asked a year ago
- AWS OFFICIALUpdated 6 months ago

Thank you for your reply. Do you know if there's a way to export / import configurations? We have so many environment variables...
I'm afraid the AWS console is not much help for that. Did you check the AWS CLI? maybe you can export configurations, make changes, and import them back using bash scripts.