Ensure Classic Load Balancers are not used
Classic Load Balancers should be migrated to Application or Network Load Balancers for better features and security.
Security Impact
Classic Load Balancers lack features like WAF integration, host-based routing, and improved security policies.
How to Remediate
Migrate Classic Load Balancers to ALB or NLB using the AWS migration wizard or manual recreation.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Load Balancing (ELB) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elb-11
- Service
- Elastic Load Balancing (ELB)
- Category
- Best Practices
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial