Elasticbeanstalk platform upgrade from Node.js 18 running on 64bit Amazon Linux 2023/6.3.0 to Node.js 18 running on 64bit Amazon Linux 2023/6.4.0 failed

Thank you for providing the details about your Elastic Beanstalk platform upgrade issue. Let's address the problem step by step:

1. Permission Issue: It's good that you've already addressed the initial SSM permission issue by granting the "AmazonSSMManagedInstanceCore" policy. This should resolve the "ssm:UpdateInstanceInformation" error you were seeing initially.

2. SSM Agent Error: The error message you're seeing now ("Error occurred fetching the seelog config file path: open /etc/amazon/ssm/seelog.xml: no such file or directory") is related to the Amazon SSM Agent. This error suggests that the SSM Agent is having trouble locating its configuration file.

3. Application Unable to Start: This could be a consequence of the SSM Agent issue or a separate problem altogether.

To address these issues, you can try the following steps:

1. Verify SSM Agent Installation: Ensure that the SSM Agent is correctly installed and configured on your EC2 instance. You may need to reinstall or update the SSM Agent.

2. Check Node.js Version Compatibility: Verify that your application is compatible with the Node.js version included in the new platform version (6.4.0). According to the latest information, Node.js 18 AL2023 version 6.4.0 uses Node.js version 18.20.4.

3. Review Application Logs: Check your application logs for any specific errors that might be preventing it from starting. The issue might not be related to the platform upgrade but to your application's compatibility with the new environment.

4. Verify Environment Variables: Ensure that all necessary environment variables are correctly set in the new platform version.

5. Check Nginx Configuration: Since you're running Nginx with Node.js, verify that your Nginx configuration is compatible with the new platform version.

6. Consider a Clean Deployment: If the issues persist, you might want to consider creating a new environment with the desired platform version (6.4.0) and deploying your application to it, rather than upgrading an existing environment.

7. AWS Support: If none of the above steps resolve the issue, you may need to contact AWS Support for further assistance, as there might be a specific issue with the platform version or your account configuration.

Remember to thoroughly test your application in a non-production environment before applying changes to your production environment.

Sources
Release: Elastic Beanstalk Amazon Linux 2023 platform updates on November 21, 2024 - AWS Elastic Beanstalk
Node.js platform history - AWS Elastic Beanstalk

Did you have any luck figuring out a solution to this? I am now seeing this with NodeJS 20 upgrades to 6.4.0

After some further research I've found this is a known bug in kernel which is affecting Amazon Linux 2023. It appears that a fix is slated to be released to AL2023 later this month. Seems like the only option at this time is to wait for a fix:

https://github.com/amazonlinux/amazon-linux-2023/issues/840#issuecomment-2485782075

https://github.com/amazonlinux/amazon-linux-2023/issues/856

https://github.com/nodejs/node/issues/55587