creating-amazon-aurora-db-cluster-with-instances

What problem does it solve?

Creating an Amazon Aurora database cluster with ready-to-use instances is error-prone because cluster provisioning, instance attachment, and Secrets Manager password handling must happen in the correct order without exposing credentials.

Core Features & Use Cases

• End-to-end Aurora setup: Creates an empty Aurora cluster first, then provisions one or more instances to make the database queryable.
• Managed password via Secrets Manager: Uses Aurora’s --manage-master-user-password and the Secrets Manager KMS key so passwords are stored and referenced securely.
• Operational monitoring and guardrails: Polls cluster and instance status via call_aws, aborting on failures or excessive pending time, and provides endpoint details without leaking passwords.

Use case example: Stand up a new production-ready Aurora PostgreSQL cluster for a new application environment by creating the cluster, attaching an instance class in supported availability zones, and retrieving the endpoint while keeping the master password safely in Secrets Manager.

Quick Start

Create an Aurora MySQL or PostgreSQL cluster with an attached instance using a managed master user password and return the cluster endpoint by following the procedure described in the included reference.