CloudWatch Metric Guide
DatabaseConnectionsAmazon RDS CloudWatch metric
DatabaseConnections counts the number of client network connections open to the RDS instance at the time of sampling. It reflects both active and idle connections held by your application's connection pool.
What it measures
About DatabaseConnections
DatabaseConnections counts the number of client network connections open to the RDS instance at the time of sampling. It reflects both active and idle connections held by your application's connection pool.
| Namespace | AWS/RDS |
| Metric name | DatabaseConnections |
| Unit | Count |
| AWS docs | Official Amazon RDS metrics reference |
Why this metric matters
Connection saturation is one of the most common and fastest-moving RDS failures. When DatabaseConnections reaches max_connections, every new connection attempt returns "too many connections" — your application starts throwing errors immediately, with no gradual degradation.
Small RDS instance classes have lower max_connections values. A db.t3.micro uses approximately 66 connections by default (the formula is DBInstanceClassMemory ÷ 12,582,880). Applications with poorly configured connection pools — or runaway Lambda functions — can saturate a small instance in seconds. Knowing your headroom at all times is non-negotiable.
Recommended alarm threshold for DatabaseConnections
Recommended threshold
≥ 80% of your RDS instance's max_connections parameter value
The max_connections limit is set by the DB parameter group, not a fixed number. Alarms should be percentage-based. AWS documentation notes that exceeding max_connections causes immediate connection refusals. The 80% threshold (Nuberio recommendation) gives you enough runway to investigate and scale before connections are fully exhausted.
Is your DatabaseConnections alarm already set up correctly?
The free Nuberio Audit scans your CloudWatch setup and flags missing or misconfigured alarms — including DatabaseConnections — in 5 minutes.
Common failures that show up in DatabaseConnections
When DatabaseConnections reaches an alarm threshold, these are the most common root causes — in order of how often Nuberio sees them across customer AWS accounts.
Connection pool misconfiguration — pool max set higher than DB max_connections, so the pool creates connections until the DB refuses them
Lambda functions running without a connection pool layer (e.g., RDS Proxy), so each invocation opens a new connection and never closes it
Long-running transactions holding idle connections that the pool can't reclaim
Traffic spike exceeding auto-scaling assumptions — connection count grows faster than horizontal scaling can respond
Replica promotion failover — during the promotion window, existing connections are dropped and clients reconnect simultaneously
How the Nuberio Audit checks DatabaseConnections
The free Audit scans every Amazon RDS resource in your account and checks whether a DatabaseConnections alarm exists, whether its threshold and evaluation period are configured sensibly, and flags it if it's missing entirely. Every finding comes with the exact CLI command to fix it — read-only access, no credit card, results in about 5 minutes.
Nuberio Audit
Scans your CloudWatch setup for missing or misconfigured DatabaseConnections alarms. Free, 5-minute read-only scan.
Related Amazon RDS metrics
DatabaseConnections rarely fails in isolation. These metrics tend to correlate — monitor them together for complete Amazon RDS coverage.
FAQ
Frequently asked questions about DatabaseConnections
Common questions about setting up CloudWatch alarms for DatabaseConnections in Amazon RDS.
What is the recommended CloudWatch alarm threshold for DatabaseConnections?+
≥ 80% of your RDS instance's max_connections parameter value. The max_connections limit is set by the DB parameter group, not a fixed number. Alarms should be percentage-based. AWS documentation notes that exceeding max_connections causes immediate connection refusals. The 80% threshold (Nuberio recommendation) gives you enough runway to investigate and scale before connections are fully exhausted.
Which CloudWatch namespace does DatabaseConnections belong to?+
DatabaseConnections is published in the AWS/RDS namespace with a unit of Count. You can find it in the CloudWatch console under "Metrics" → "AWS/RDS". See the Amazon RDS CloudWatch metrics reference in the AWS documentation.
Does Nuberio automatically create CloudWatch alarms for DatabaseConnections?+
No — the free Nuberio Audit does not create alarms for you. It scans your CloudWatch setup and tells you which Amazon RDS resources are missing a DatabaseConnections alarm, then gives you the exact CLI command to create it yourself.
Can I use Nuberio without already having a DatabaseConnections alarm set up?+
Yes. The free Audit works whether or not you have any DatabaseConnections alarm configured — it reads the resource directly from CloudWatch and tells you which resources need one, plus the copy-paste AWS CLI command to create it.
This page is part of the CloudWatch metric guide — thresholds and debugging guidance for every metric across RDS, Lambda, ECS, ALB, EC2, DynamoDB, SQS, API Gateway, S3, CloudFront, ElastiCache, and EKS. To find which Amazon RDS alarms your account is missing — including DatabaseConnections — run the free CloudWatch alarm audit. The scan takes under 5 minutes and requires no account.