Skip to main content

Use Case for AWS ALB Low Traffic Detector

  1. Configure AWS ALB Low Traffic Detector
  2. Use Case for AWS ALB Low Traffic Detector
  3. Triage Guides by Violation Type
    1. Triage AWS ALB Low Traffic Detector LOW_TRAFFIC

AWS ALB Low Traffic Detector Use Cases

This policy helps you monitor the network activity of your AWS Application Load Balancers (ALBs) by reporting low bytes processed. It's beneficial for identifying underutilized ALBs over a specified period, which can indicate overprovisioning or a potential misconfiguration.

Pros​

  • Cost Management: By identifying low-traffic ALBs, you can reduce costs by resizing or decommissioning them.
  • Resource Optimization: Helps ensure that ALBs are appropriately sized and configured for their workloads.

Cons​

  • False Positives: May flag ALBs with intentionally low traffic, such as those used for staging or low-use applications.

How It Works​

  • Sets a threshold for average bytes processed per day.
  • Sets the number of days to look back for traffic data from AWS CloudWatch metrics.

Variables​

  • averageBytesThreshold: The minimum average bytes processed per day. Default is 0.
  • lookBackDays: The number of days to analyze. Default is 30.

Violation Types​

  • LOW_TRAFFIC: Triggered when an ALB has lower than the threshold average daily bytes processed.