Skip to main content
All CollectionsMonitoringTests
Test 293: AWS Classic Load Balancer Latency Monitored
Test 293: AWS Classic Load Balancer Latency Monitored

Validates that all AWS Classic Load Balancers have a CloudWatch metric alarm for latency and that the alarm is subscribed to an SNS topic.

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 Classic Load Balancers do not have a CloudWatch metric alarm for latency configured with a subscription to an SNS topic, the test will fail.

STEPS TO REMEDIATE

For Classic Elastic Load Balancers that are failing:

  1. Sign in to CloudWatch console.

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

  3. Click 'select metric' > 'ELB' (Elastic Load Balancing) > 'Per-ELB Metrics' > select the load balancer failing this test > select the 'Latency' 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 Classic Elastic Load Balancer.

Did this answer your question?