The database waits. Your authentication flows decide if the connection happens. AWS RDS IAM Connect changes that decision into a secure, dynamic handshake. No stored passwords. No static database users. Just short-lived, signed tokens created on-demand.
The licensing model for AWS RDS IAM Connect is hidden in plain sight. There is no extra fee for enabling IAM authentication on RDS instances. Whether you run MySQL or PostgreSQL in RDS, IAM Connect is included in your existing RDS pricing. Standard AWS IAM features apply—you pay for RDS compute, storage, and I/O, but IAM authentication itself has no line item cost. This frees you from per-seat or per-user licensing models common in other database platforms.
IAM Connect shifts database access control into IAM policies. This centralizes permissions and integrates with AWS’s identity federation. You define which IAM users, roles, or AWS services can call rds-db:connect for a given DB instance resource. Once approved, they generate an auth token through aws rds generate-db-auth-token. This token is valid for 15 minutes by default. The database validates it against AWS’s public keys, removing any direct password management from your stack.