All checks
Medium ELB · regional

Application and Network Load Balancers with listeners should use recommended security policies

Verifies that every HTTPS listener on an Application Load Balancer and every TLS listener on a Network Load Balancer uses one of the eight security policies AWS recommends for encrypting data in transit. The list is fixed, so a stricter policy outside it still fails; where that is deliberate, mark the finding Won't fix rather than weaken the listener.

service
ELB
severity
Medium
scope
evaluated in every region

How to fix it

  • Can break clients: Clients limited to TLS 1.1 or older, or to ciphers the new policy drops, can no longer connect, so check the access logs for the versions in use first.
  • Interrupts service: AWS warns that changing the policy can disrupt a load balancer under high traffic, so apply it at a quiet time or after an LCU reservation.

In the console

EC2 → Load balancers → the load balancer → Listeners and rules → the listener → Secure listener settings

Security policy
ELBSecurityPolicy-TLS13-1-2-Res-2021-06, or ELBSecurityPolicy-TLS13-1-3-2021-06 if every client has TLS 1.3

With the AWS CLI

aws elbv2 modify-listener --listener-arn <listener-arn> --ssl-policy ELBSecurityPolicy-TLS13-1-2-Res-2021-06 --region <region>

With Terraform

resource "aws_lb_listener" "https" {
  load_balancer_arn = var.load_balancer_arn
  port              = 443
  protocol          = "HTTPS"
  certificate_arn   = var.acm_certificate_arn
  ssl_policy        = "ELBSecurityPolicy-TLS13-1-2-Res-2021-06"

  default_action {
    type             = "forward"
    target_group_arn = var.target_group_arn
  }
}

See which of your accounts this check is failing on.

Book a live scan