Environment health has transitioned to Severe ☁️ AWS

Elastic Beanstalk: Environment health has transitioned from Ok to Severe

Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.

Seen on: AWS

Meaning

Enhanced health turns Severe when requests fail (5xx), instances are unhealthy, or deployments failed. The health causes and /var/log/web.stdout.log / eb-engine.log explain why: app crash, wrong port (must listen on PORT, default 8080/5000), failed deployment hooks, or full disk.

Common causes

  • Application crash or exceptions (5xx)
  • App listening on the wrong port
  • Failed deployment (eb-engine.log)
  • Instance resource exhaustion (CPU, memory, disk)

⚡ Quick fix

  1. eb health --refresh and eb logs to see causes
  2. Listen on process.env.PORT
  3. Roll back to the last good version

Detailed fix by platform

AWS CLI

  1. bash
    eb health --refresh
eb logs --all
eb deploy --label previous-good   # or redeploy an earlier application version

How to diagnose

  1. Causes — Health tab "Causes"
  2. Logs — web.stdout.log, eb-engine.log
  3. Port — App vs proxy port

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.