Many Lambda functions start at the same time and the RDS connection limit is reached.
Pool application connections and reduce the cost of establishing database sessions.
Which service is most appropriate?
Place Amazon RDS Proxy between Lambda and RDS to pool and reuse database connections during concurrency spikes.
Detailed explanation
A presigned URL grants object access and is not a database connection pool.
A presigned URL grants object access and is not a database connection pool.
RDS Proxy pools and reuses connections so bursts of application invocations do not create one database connection each.
RDS Proxy pools and reuses connections so bursts of application invocations do not create one database connection each.
This increases instance and operational overhead and does not solve connection pooling.
This increases instance and operational overhead and does not solve connection pooling.
DNS routing does not pool or reuse database sessions.
DNS routing does not pool or reuse database sessions.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS Proxyの接続プーリング公式説明を確認する。
What to confirm
サーバーレスからリレーショナルDBへの接続管理にRDS Proxyを選べる。
Key points
- Amazon RDS Proxy
- Connection pooling
- Lambda concurrency
Notes
- Environment: AWS公式RDS Proxyドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Burst absorption
A proxy decouples invocation bursts from the number of backend database sessions.
Relational interface
RDS Proxy preserves the relational database endpoint while changing how connections are managed.