Skip to main content

Triage AWS RDS Low Connections ZERO_CONNECTIONS

  1. Configure AWS RDS Low Connections
  2. Use Case for AWS RDS Low Connections
  3. Triage Guides by Violation Type
    1. Triage AWS RDS Low Connections CONNECTIONS_BELOW_THRESHOLD
    2. Triage AWS RDS Low Connections ZERO_CONNECTIONS

Zero Connections Violation Guide

Understand​

Instances with zero connections over the past 30 days are likely not being used, resulting in unnecessary costs.

Validate​

  1. Open the AWS Management Console.
  2. Navigate to the CloudWatch dashboard.
  3. Find the DBConnections metric for the specific RDS instance.
  4. Ensure you have selected the past 30 days range.

Data Source: CloudWatch metrics.

This policy scans on a reactive basis.

Triage​

  • Impact: Unused RDS instances incur costs without providing any benefit.
  • Persistence: This issue will persist until the instance use case is reassessed.
  • Downtime Risk: Deleting or decommissioning may impact dependent services.

Act​

  1. Review the use case for the RDS instance.
  2. If confirmed unused, decommission or repurpose the instance.

Reflect​

If this alarm occurs frequently without meaningful action, consider adjusting the threshold or policy settings based on operational needs.