Give database connections a shared entrance — RDS Proxy

Your goal

Create a database proxy configuration and change its idle connection timeout.

Why this matters

Many workers can create too many database connections. A proxy has its own connection settings. You will configure a proxy record and inspect its idle timeout without opening a real database connection.

Words you will use

A proxy sits between an app and its database. Pooling reuses connections. An endpoint is the address an app connects to.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Prepare the proxy configuration

Create private-network resources, a practice secret, and a proxy role, then create a PostgreSQL-family proxy. This models connection settings without running a SQL connection pool.

2. Set the idle timeout

Choose how many seconds an idle client connection may remain open. Save the setting on your proxy. This does not change the database’s query timeout.

Idle client timeout in seconds: Choose 60–3600 seconds for this practice setting. Suggested practice value: 300.

3. Inspect the proxy

Describe the proxy and compare IdleClientTimeout with your value. Inspect its TLS and authentication settings as well. Configuration alone does not prove failover or database throughput.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.