无法在AWS Beanstalk部署React应用，报错Error code: 128

Hey there! Let's tackle that Error Code 128 you're running into when deploying your locally working demo to AWS Beanstalk. This error typically signals a failure in a command executed during the deployment process—usually tied to Git, permissions, or environment mismatches. Here are the most common fixes:

1. Resolve Git Repository Issues #

Error 128 often pops up when using Git-based deployments (the default for EB CLI). Here's what to check:

• Ensure your project is a Git repo: If you haven't already, run git init in your project root, then commit all files with git add . followed by git commit -m "Prepare for Beanstalk deployment". Uncommitted files can break the deployment push.
• Verify EB CLI remote setup: Run eb status to confirm your local repo is linked to the correct Beanstalk environment. If not, re-run eb init to re-associate your project with the right AWS region and environment.

2. Fix Script Permissions #

If your demo uses startup or build scripts (like start.sh or build.sh), missing execution permissions can trigger Error 128 when Beanstalk tries to run them:

• Add execute permissions to your script locally: chmod +x your-script-name.sh
• Commit this permission change to Git (git add your-script-name.sh then git commit -m "Add execute permission to script") before re-deploying.

3. Debug Dependency/Build Failures #

Just because your app works locally doesn't mean the Beanstalk environment has all the same dependencies. The error could be hiding a failed build step:

• Check deployment logs: In the AWS Beanstalk console, go to your environment → Logs → Request Logs → Full Logs. Look for lines like "npm install failed" or "pip install error"—these will tell you exactly which dependency is missing or broken.
• Lock down dependencies: For Node.js, make sure all required packages are listed in package.json (no local-only installs). For Python, ensure requirements.txt includes every package your app uses.

4. Refresh AWS Credentials/EB CLI Configuration #

If you're using the EB CLI, expired or misconfigured AWS credentials can cause the deployment push to fail with Error 128:

• Update your AWS credentials: Run aws configure and enter your valid access key ID, secret access key, default region, and output format.
• Reinitialize EB CLI: Run eb init again, selecting your existing environment to refresh the link between your local repo and AWS.

If none of these fixes work, share the full error output from your deployment command (or the relevant snippet from Beanstalk logs) and we can narrow it down further!

内容的提问来源于stack exchange，提问作者Sachin Vairagi