Skip to main content

Aurora RDS Issues

Common issues with Aurora database provisioning and connectivity.

No Database Available​

  • Pool empty — If all clusters in the pool are checked out, your environment will wait. Contact your platform team to check pool capacity.
  • Pool not configured — Your application may not be configured with a database pool. Check with your platform team.

Connection Failures​

  • Wrong endpoint — Use ${database.<pool>.writer_endpoint} for the primary connection. Double-check the pool name matches your configuration.
  • Security group — Your service may not have network access to the database. Verify your infrastructure security group rules allow the connection.
  • Credentials — Database credentials are typically delivered via secret providers. Make sure your secret provider is configured correctly.

Data Not Persisting​

  • Ephemeral environments — Database clusters are tied to the environment lifecycle. When the environment is deleted, the database is returned to the pool and may be reset.
  • Pool snapshots — Clusters are typically restored from a snapshot. Your starting data depends on when the snapshot was taken.