Ensure ELB has appropriate idle timeout
Load balancer idle timeout should be configured appropriately for the application workload.
Security Impact
Incorrect idle timeout can cause connection drops for long-running requests or resource waste for short requests.
How to Remediate
Configure idle timeout based on application needs. Default is 60 seconds, may need adjustment for long-running requests.
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-20
- Service
- Elastic Load Balancing (ELB)
- Category
- Performance
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial