# Ensure Elastic Beanstalk Enhanced Health Reporting Enabled

- Source: https://support.icompaas.com/support/solutions/articles/62000218490-ensure-elastic-beanstalk-enhanced-health-reporting-enabled
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Security Controls](https://support.icompaas.com/support/solutions/62000065178) › [AWS Services](https://support.icompaas.com/support/solutions/folders/62000097507)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

## **Description:**

AWS **Elastic Beanstalk** is an easy-to-use service for deploying and scaling web applications and services. You can simply upload your code and Elastic Beanstalk automatically handles the deployment, from capacity provisioning, load balancing, auto-scaling to application health monitoring. At the same time, you retain full control over the AWS resources powering your application and can access the underlying resources at any time.

  

## **Rational:**

AWS Elastic Beanstalk enhanced health reporting gathers additional information about resources in your environment. Elastic Beanstalk uses changes in instance health to evaluate environment health but does not immediately change environment health status. When an instance fails health checks at least three times in any one-minute period, Elastic Beanstalk may downgrade the health of the environment.

  

## **Impact:**

Elastic Beanstalk analyzes the information gathered to provide a better picture of overall environment health and aid in the identification of issues that can cause your application to become unavailable.

  

## **Default Value:**

By default AWS elastic Beanstalk health report will be selected to Enhanced.

  

### **Pre Requisites**

-   Make sure you are in a correct region
    

  

## **Remediation:**

  

## **Test Plan:**

1.  Sign in to AWS console
    
2.  Navigate to Elastic Beanstalk console, and in the **Regions** list, select your AWS Region.
    
3.  Click on **Environments** in the left navigation pane, and then choose the name of your environment you want from the list.
    
4.  Choose **Configuration** In the navigation pane
    
5.  In the **Monitoring** configuration category, if you see **System: Basic** then follow implementation steps  
    ![](https://support.icompaas.com/assets/kb/370ece0d628611b9.png)
    

  

## **Using AWS CLI:**

### To know about the health of beanstalk

aws elasticbeanstalk describe-environment-health
\[--environment-name <value>\]
\[--environment-id <value>\]
\[--attribute-names <value>\]

###  **Implementation Steps**

1.  Sign in to AWS console
    
2.  Navigate to Elastic Beanstalk console, and in the **Regions** list, select your AWS Region.
    
3.  Click on **Environments** in the left navigation pane, and then choose the name of your environment you want from the list.![](https://support.icompaas.com/assets/kb/9e5f5e5b88d2f376.png)
    
    **Note:** If you have many environments, use the search bar to filter the environment list.
    
4.  choose **Configuration** In the navigation pane![](https://support.icompaas.com/assets/kb/0c4fe7b6b2e1c35b.png)
    
5.  In the **Monitoring** configuration category, Click **Edit**.![](https://support.icompaas.com/assets/kb/c3c5995e7be8ae4c.png)
    
6.  Under **Health reporting**, for **System**, select **Enhanced**.  
    ![](https://support.icompaas.com/assets/kb/e6a91086cf776d92.png)
7.  Click on **Apply**.

  

**CLI Remediation:**

aws elasticbeanstalk update-environment
  --region Region-Name
  --environment-name your\_environmentName
  --option-settings Namespace=aws:elasticbeanstalk:healthreporting:system,OptionName=SystemType,Value=enhanced

-   Replace Region-Name with your region(like us-east-1, us-east-2) in line 2.
-   Replace your\_environment with your environment name you want to enable enhanced health report in line 3

  

### **Backout Plan:**

If you want to roll back to basic reporting again do follow the same steps in the implementation section and in step 6 select the Basic option.

![](https://support.icompaas.com/assets/kb/21aa2dfd1d5c3e70.png)

**Using AWS CLI:**

**To make the health check is basic** 

aws elasticbeanstalk update-environment
  --region Region-Name
  --environment-name your\_environmentName
  --option-settings Namespace=aws:elasticbeanstalk:healthreporting:system,OptionName=SystemType,Value=basic

## **References:**

[![](https://support.icompaas.com/assets/kb/e4433b5bbb6a683d.png)](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced.html)[Enhanced health reporting and monitoring - AWS Elastic Beanstalk](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.