Using AWS Systems Manager Elastic Beanstalk runbooks - AWS Elastic Beanstalk

Using AWS Systems Manager Elastic Beanstalk runbooks

You can use Systems Manager to troubleshoot your Elastic Beanstalk environments. To help you get started quickly, Systems Manager provides predefined Automation runbooks for Elastic Beanstalk. An Automation runbook is a type of Systems Manager document that defines actions to perform on your environment's instances and other AWS resources.

The document AWSSupport-TroubleshootElasticBeanstalk is an Automation runbook designed to help identify a number of common issues that can degrade your Elastic Beanstalk environment. To do so, it checks components of your environment, including the following: EC2 instances, the VPC, AWS CloudFormation stack, load balancers, Auto Scaling groups, and network configuration associated with security group rules, route tables, and ACLs.

It also provides an option to upload bundled log files from your environment to AWS Support.

For more information, see AWSSupport-TroubleshootElasticBeanstalk in the AWS Systems Manager Automation runbook reference.

Use Systems Manager to run AWSSupport-TroubleshootElasticBeanstalk runbook
Note

Run this procedure in the same AWS Region where your Elastic Beanstalk environment is located.

  1. Open the AWS Systems Manager console.

  2. From the navigation pane, in the Change Management section, choose Automation.

  3. Choose Execute automation.

  4. On the Owned by Amazon tab, in the Automation document search box, enter AWSSupport-TroubleshootElasticBeanstalk.

  5. Select the AWSSupport-TroubleshootElasticBeanstalk card, then choose Next.

  6. Select Execute.

  7. In the Input parameters section:

    1. From the AutomationAssumeRole dropdown, select the ARN of the role that allows Systems Manager to perform actions on your behalf.

    2. For ApplicationName, enter the name of the Elastic Beanstalk application.

    3. For Environment Name, enter the Elastic Beanstalk environment.

    4. (Optional) For S3UploaderLink, enter a link if an AWS Support Engineer has provided you an S3 link for log collection.

  8. Choose Execute.

    If any of the steps fail, select the link under the Step ID column for the step that failed. This displays an Execution detail page for the step. The VerificationErrorMessage section will display a summary of the steps that require attention. For example, the IAMPermissionCheck could display a Warning message. In this case, you could check that the role selected in the AutomationAssumeRole dropdown has the necessary permissions.

After all of the steps successfully complete, the output gives troubleshooting steps and recommendations to restore your environment to a healthy state.