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

Provision an Amazon Aurora cluster with instances and managed Secrets Manager passwords.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill creating-amazon-aurora-db-cluster-with-instances
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-amazon-aurora-db-cluster-with-instances
Source: https://github.com/mreferre/aws-agent-toolkit-skills/tree/main/.kiro/skills/creating-amazon-aurora-db-cluster-with-instances
Command: npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill creating-amazon-aurora-db-cluster-with-instances

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about creating-amazon-aurora-db-cluster-with-instances

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Amazon Aurora cluster and manage the master password with Secrets Manager?

Creating an Amazon Aurora database cluster requires provisioning an empty cluster, attaching instances to make it queryable, and using Secrets Manager to store the master user password securely without exposing plaintext credentials during the process.

What is the correct order of operations for provisioning an Aurora database cluster with instances?

Provisioning an Aurora database cluster requires creating the empty cluster first, then attaching one or more instances in supported availability zones, and finally polling cluster and instance status until the environment is ready to accept queries.

Can I use plaintext parameters when setting up an Aurora PostgreSQL cluster?

Setting up an Aurora PostgreSQL cluster does not allow plaintext password parameters; it mandates using the manage-master-user-password feature so credentials are stored and referenced securely via Secrets Manager and KMS encryption without leaking sensitive values.

How does infrastructure automation handle Aurora cluster status monitoring during provisioning?

Infrastructure automation handles Aurora cluster status monitoring by polling the cluster and instance status via the call_aws tool, automatically aborting the provisioning process if it detects operational failures or excessive pending time before returning endpoints.

Does this Aurora provisioning approach support both MySQL and PostgreSQL environments?

This Aurora provisioning approach supports both MySQL and PostgreSQL environments, applying the same coordinated process of cluster creation, instance attachment, Secrets Manager password handling, and KMS encryption for production-ready database setups.