Skip to main content

How to pass the Load balancer unhealthy host count monitored (AWS) Test

S
Written by Shannon DeLange
Updated today

The Load balancer unhealthy host count monitored (AWS) test requires that you set up healthy host count alerts in Amazon Cloudwatch or a 3rd party monitoring provider for your application and classic load balancers. Define alerts for at least one of the following metric categories:

  • UnHealthyHostCount

  • HealthyHostCount

  • EnvironmentHealth

Prerequisites

  • AWS Cloudwatch

  • AWS Classic or Application ELB

Procedure

For Classic and Application Load Balancers, We're reading these two metrics:

UnHealthyHostCount
HealthyHostCount

  • Select one of the two Metrics, and continue

mceclip2.png

  • Next, Configure the Alarm Conditions

mceclip3.png

  • And finally, Configure the Notification type and any Action you'd like to take

mceclip4.png


The same steps apply for a Classic Load Balancer:

mceclip6.png



Once finished, you should see your new Alarm appear in the All Alarms dashboard!
Vanta will then pull this Load Balancer in and test to see if alarms are configured for those metrics.

  • For ElasticBeanstalk, We look for the following Metric:

EnvironmentHealth

Example:

i.png

Common Issues

  • Vanta cannot read your Queried Metrics for your Alarms:

    mceclip8.png

  • If you're using a Query to build your alarms, You may need to deactivate monitoring on that specific Load Balancer. You can upload a screenshot of your current Alarm config for manual evidence.