Skip to main content
All CollectionsMonitoringTests
Test 298: AWS Application Load Balancer Unhealthy Hosts Monitored
Test 298: AWS Application Load Balancer Unhealthy Hosts Monitored

Validates that all AWS Application Load Balancers have a CloudWatch metric alarm (subscribed to an SNS topic) for unhealthy hosts count.

Updated over a month ago

ASSOCIATED DRATA CONTROL

This test is part of the System Monitoring control (DCF-86) that ensures production systems and resources are monitored and automated alerts are sent out personnel based on pre-configured rules. Events are triaged to determine if they constitute an incident and escalated per policy if necessary.

WHAT TO DO IF A TEST FAILS

If Drata finds that one or more AWS Application Load Balancers do not have a CloudWatch metric alarm for unhealthy hosts count configured with a subscription to an SNS topic, the test will fail.

STEPS TO REMEDIATE

  1. Sign in to CloudWatch console.

  2. Create an alarm by selecting 'Alarm' then 'Create alarm' from the navigation panel.

  3. Click 'select metric' > 'ApplicationELB' (Application Elastic Load Balancing) > 'Per AppELB, per TG Metrics' > select the load balancer failing this test > select the 'UnhealthyHostCount' metric.

  4. Specify metrics and conditions for the alarm such as threshold value and period.

  5. Choose an existing SNS topic or create a new one to subscribe to.

  6. Give your alarm a name, review your settings, and finish creating the alarm.

  7. Repeat for each failing AWS Application Load Balancer.

Did this answer your question?