---
title: "Discussion on \"RDS Proxy in Production: Solving Connection Exhaustion and Sub-Minute Failover\" | Hashnode"
description: "Discussion on \"RDS Proxy in Production: Solving Connection Exhaustion and Sub-Minute Failover\". Your Lambda functions are throwing \"too many connections\" errors at 3 AM, waking up your on-call engineer. Your application survived the traffic spike, but your RDS instance hit its connection limit because each Lambda created its own connection pool..."
url: "https://hashnode.com/posts/rds-proxy-in-production-solving-connection-exhaustion/699d67a9713d67eb0dd788bb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [RDS Proxy in Production: Solving Connection Exhaustion and Sub-Minute Failover](https://timderzhavets.hashnode.dev/rds-proxy-in-production-solving-connection-exhaustion?utm_source=hashnode&utm_medium=feed)

Your Lambda functions are throwing "too many connections" errors at 3 AM, waking up your on-call engineer. Your application survived the traffic spike, but your RDS instance hit its connection limit because each Lambda created its own connection pool...

Feb 24 · 19 min read · timderzhavets.hashnode.dev  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#lambda](https://hashnode.com/tag/lambda)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#rds](https://hashnode.com/tag/rds)

## Written by

[Tim Derzhavets](https://hashnode.com/@timderzhavets)

@timderzhavets

  
[View profile](https://hashnode.com/@timderzhavets)

tderzhav

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
