Skip to main content

🛡️ AWS Elastic Beanstalk Environment does not have enhanced health reporting enabled🟢

  • Contextual name: 🛡️ Environment does not have enhanced health reporting enabled🟢
  • ID: /ce/ca/aws/elastic-beanstalk/environment-health-reporting
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: RELIABILITY

Logic​

Similar Policies​

Description​

Open File

Description​

This policy identifies AWS Elastic Beanstalk Environments that do not have enhanced health reporting enabled.

Rationale​

Enabling Enhanced Health Reporting provides significant operational advantages. It allows for faster detection and diagnosis of issues that may affect application availability and performance. The detailed metrics and customizable health dashboards offer deeper insights into the root causes of problems, helping reduce downtime and improve overall reliability.

In contrast, Basic Health Reporting only provides binary instance health information from Elastic Load Balancing checks, which is often insufficient for diagnosing complex issues.

Audit​

This policy flags an AWS Elastic Beanstalk Environment as INCOMPLIANT if its related AWS Elastic Beanstalk Configuration Set. contains the entry aws:elasticbeanstalk:healthreporting:system SystemType basic in Option Settings.

Beanstalk Environment is marked as INAPPLICABLE in its Status is not Ready.

Remediation​

Open File

Remediation​

Enable Enhanced Health Reporting​

Using the EB CLI​

  1. Open your environment configuration in the default text editor:

    ~/project$ eb config

  2. Locate the aws:elasticbeanstalk:healthreporting:system namespace and update the SystemType value to enhanced:

    aws:elasticbeanstalk:healthreporting:system:
    SystemType: enhanced

  3. Save the configuration file and close the editor:

    The EB CLI will automatically start an environment update to apply the changes. You can monitor the update progress in the terminal or exit safely using Ctrl+C:

    ~/project$ eb config
    Printing Status:
    INFO: Environment update is starting.
    INFO: Health reporting type changed to ENHANCED.
    INFO: Updating environment no-role-test's configuration settings.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElasticBeanstalk.1] Elastic Beanstalk environments should have enhanced health reporting enabled1no data
💼 AWS Well-Architected → 💼 REL11-BP01 Monitor all components of the workload to detect failures2no data
💼 AWS Well-Architected → 💼 REL11-BP02 Fail over to healthy resources1no data
💼 Cloudaware Framework → 💼 System Configuration45no data
💼 FedRAMP High Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)213no data
💼 FedRAMP High Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)2714no data
💼 FedRAMP Low Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)113no data
💼 FedRAMP Low Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)14no data
💼 FedRAMP Moderate Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)213no data
💼 FedRAMP Moderate Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)214no data
💼 NIST CSF v2.0 → 💼 DE.AE-02: Potentially adverse events are analyzed to better understand associated activities35no data
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources50no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events145no data
💼 NIST CSF v2.0 → 💼 DE.CM-02: The physical environment is monitored to find potentially adverse events13no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-06: External service provider activities and services are monitored to find potentially adverse events35no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events142no data
💼 NIST CSF v2.0 → 💼 ID.IM-01: Improvements are identified from evaluations26no data
💼 NIST CSF v2.0 → 💼 ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties40no data
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities41no data
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded31no data
💼 NIST CSF v2.0 → 💼 ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked31no data
💼 NIST SP 800-53 Revision 5 → 💼 CA-7 Continuous Monitoring613no data
💼 NIST SP 800-53 Revision 5 → 💼 SI-2 Flaw Remediation6611no data