All checks
Low
Elastic Beanstalk environments should have enhanced health reporting enabled
Checks that an Elastic Beanstalk environment uses enhanced health reporting, where a health agent on each instance reads its logs and operating system metrics, so a change in the health of the infrastructure shows up quickly with a severity and likely causes. It needs a supported platform version, a service role and an instance profile.
- service
- ElasticBeanstalk
- severity
- Low
- scope
- evaluated in every region
How to fix it
- Can break clients: Rolling updates and deployments then wait for every instance to pass enhanced health's stricter checks, so one that only passed the load balancer check can stall or fail them.
In the console
Elastic Beanstalk → Environments → the environment → Configuration → Updates, monitoring, and logging
- Health reporting → System
- Enhanced
With the AWS CLI
aws elasticbeanstalk update-environment --environment-name <environment-name> --option-settings Namespace=aws:elasticbeanstalk:healthreporting:system,OptionName=SystemType,Value=enhanced --region <region>With Terraform
resource "aws_elastic_beanstalk_environment" "this" {
name = var.environment_name
application = var.application_name
setting {
namespace = "aws:elasticbeanstalk:healthreporting:system"
name = "SystemType"
value = "enhanced"
}
}See which of your accounts this check is failing on.
Book a live scan