A burst of concurrent Lambda invocations creates too many database connections.
Reuse connections instead of selecting a much larger database instance solely for that reason.
Which method is most appropriate?
Use an RDS Proxy connection pool to absorb connection bursts and separate connection pressure from database compute sizing.
Detailed explanation
Oversizing increases steady-state cost without correcting the connection pattern.
Oversizing increases steady-state cost without correcting the connection pattern.
Serializing all invocations removes scalability unnecessarily rather than managing connection reuse.
Serializing all invocations removes scalability unnecessarily rather than managing connection reuse.
RDS Proxy reuses database sessions and can reduce the need to oversize the database for connection churn.
RDS Proxy reuses database sessions and can reduce the need to oversize the database for connection churn.
S3 policies do not manage relational database connections.
S3 policies do not manage relational database connections.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS Proxyの接続プーリングとスケーリング公式説明を確認する。
What to confirm
DB容量と接続数のボトルネックを分けてコスト最適化できる。
Key points
- RDS Proxy
- Connection pool
- Database sizing
Notes
- Environment: AWS公式RDS Proxyドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Right-size the bottleneck
A proxy can address connection churn, while CPU, memory, and query load may still require database sizing.
Concurrency control
Limiting every invocation to one removes useful parallelism instead of solving the connection pattern.