ALB port-80 listener does not redirect to HTTPS
- Severity
- Medium
- Service
- Elastic Load Balancing
- Check ID
- ALB_HTTP_TO_HTTPS_REDIRECT
What this check finds
An Application Load Balancer has a listener on port 80 (HTTP) whose default action is not a redirect to HTTPS. All HTTP traffic should be automatically redirected to HTTPS to ensure encryption in transit.
Passing looks like: ALB redirects HTTP to HTTPS.
How to fix it
Change the port-80 listener default action to a redirect.
AWS CLI
aws elbv2 modify-listener --listener-arn LISTENER_ARN --default-actions Type=redirect,RedirectConfig={Protocol=HTTPS,Port=443,StatusCode=HTTP_301}
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
EC2 → Load Balancers → select ALB → Listeners → HTTP:80 → Edit → Add action → Redirect.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| PCI-DSS v4.0.1 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs