| 💼 [ELB.1] Application Load Balancer should be configured to redirect all HTTP requests to HTTPS | | | | |
| 💼 [ELB.2] Classic Load Balancers with SSL/HTTPS listeners should use a certificate provided by AWS Certificate Manager | | | | |
| 💼 [ELB.3] Classic Load Balancer listeners should be configured with HTTPS or TLS termination | | | | |
| 💼 [ELB.4] Application Load Balancer should be configured to drop invalid http headers | | | | |
| 💼 [ELB.5] Application and Classic Load Balancers logging should be enabled | | | | |
| 💼 [ELB.6] Application, Gateway, and Network Load Balancers should have deletion protection enabled | | | | |
| 💼 [ELB.7] Classic Load Balancers should have connection draining enabled | | | | |
| 💼 [ELB.8] Classic Load Balancers with SSL listeners should use a predefined security policy that has strong AWS Configuration | | | | |
| 💼 [ELB.9] Classic Load Balancers should have cross-zone load balancing enabled | | | | |
| 💼 [ELB.10] Classic Load Balancer should span multiple Availability Zones | | | | |
| 💼 [ELB.12] Application Load Balancer should be configured with defensive or strictest desync mitigation mode | | | | |
| 💼 [ELB.13] Application, Network and Gateway Load Balancers should span multiple Availability Zones | | | | |
| 💼 [ELB.14] Classic Load Balancer should be configured with defensive or strictest desync mitigation mode | | | | |
| 💼 [ELB.17] Application and Network Load Balancers with listeners should use recommended security policies | | | | |