Why is my Elastic Beanstalk environment in a non-operational state?

Short description

Elastic Beanstalk creates an CloudFormation stack to manage the resources that are associated with the Elastic Beanstalk environment. You can check this stack in the CloudFormation console with the stack name awseb-envID-stack.

When the Elastic Beanstalk environment enters a non-operational state, the CloudFormation stack shows a FAILED status. You also receive the following error message:

"The stack stack_id associated with environment environment-ID is in stack-status state."

Resolution

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

To change your Elastic Beanstalk environment to an operational state, use the following table to take actions depending on your CloudFormation stack status:

If your CloudFormation stack has a FAILED status, then use one of the following resolutions.

CREATE_FAILED status

When the stack has a CREATE_FAILED status, the environment can't recover. The environment continues to have issues, even if the stack status changes to UPDATE_COMPLETE. If your stack has the CREATE_FAILED status, then you must create a new Elastic Beanstalk environment.

To recreate the environment, select one of the following options:

• If there's an issue that prevents the creation of a new environment, then address the root cause of the stack failure.
• Create a saved configuration to maintain a similar configuration that's accessible to your new environment.
• Perform a blue/green deployment. After the new environment works correctly, use the CloudFormation console to swap the CNAMEs between the URLs of the two environments. Or, run either the eb swap command or swap-environment-cnames command.
• Create a new environment. To do this, first terminate the current environment. Then, run the CreateEnvironment operation again. You can also rebuild the environment through the console, or run the rebuild-environment command.

UPDATE_ROLLBACK_FAILED status

To change the Elastic Beanstalk environment to an operational state, complete the following steps:

1. Open the CloudFormation console.
2. Identify the resource that failed to update during the rollback from the stack event, and then address the failure.
3. Change the stack to the UPDATE_ROLLBACK_COMPLETE status. To do so, perform an update rollback in the CloudFormation console.
4. In the Continue update rollback dialog box, expand Advanced troubleshooting.
5. In the Resources to skip - optional section, select the resource that failed to update.
6. Choose Continue update rollback. The stack now shows the UPDATE_ROLLBACK_COMPLETE status.
7. Retry the operation that returned the error.

DELETE_FAILED status

To change the Elastic Beanstalk environment to an operational state, complete the following steps:

1. Open the CloudFormation console.
2. Identify the resource that failed to delete during the stack event.
3. Manually delete the resource. For example, if the resource is a security group, then delete the security group from the Amazon Elastic Compute Cloud (Amazon EC2) console.
4. Delete the CloudFormation stack from the CloudFormation console. The deleted stack shows a DELETE_COMPLETE status.
5. Retry the Terminate environment or Rebuild environment operations.

For more information, see How do I terminate or rebuild my Elastic Beanstalk environment when the AWSEBSecurityGroup fails to delete?

Related information

Recovering your Elastic Beanstalk environment from an invalid state