If a deployment fails, you can use the EB CLI or the console to retrieve instance logs as a ZIP file to diagnose errors in the environment's health or application execution. Create an Elastic Beanstalk application source bundle
: On macOS, it is recommended to remove hidden system files like __MACOSX or .DS_Store to keep the archive clean and avoid configuration issues. Troubleshooting and Logs
: You can create a ZIP file on your local machine and upload it directly through the Elastic Beanstalk Management Console . eb.zip
: The archive must not include a parent folder. Your application's root files (e.g., index.php or app.js ) must be at the top level of the ZIP. Size Limit : The bundle cannot exceed 500 MB .
: For platforms like Node.js, you should typically exclude the node_modules folder as Elastic Beanstalk will automatically run npm install during the deployment process. How to Create and Deploy If a deployment fails, you can use the
: The eb deploy command can automatically package your project into a ZIP file and deploy it to your environment. If Git is initialized, it uses the latest commit; otherwise, it respects an .ebignore file if present.
To ensure a successful deployment, the ZIP file must follow specific AWS guidelines: : The archive must not include a parent folder
An eb.zip file is a compressed source bundle containing your application's code, configuration files, and dependencies needed to run on the AWS Elastic Beanstalk platform. Key Requirements