amazon-aurora-mysql

Creates, sizes, and optimizes Amazon Aurora MySQL clusters with cost analysis and safety guardrails.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill amazon-aurora-mysql-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amazon-aurora-mysql
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/amazon-aurora-mysql
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill amazon-aurora-mysql-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, and includes scripts (resource) and references (resource) components.

What problem does it solve? Managing Aurora MySQL clusters involves complex decisions around serverless ACU sizing, I/O-Optimized storage, Reserved Instance vs Savings Plan commitments, and version upgrades, where mistakes are costly and destructive operations are irreversible. ## Core Features & Use Cases - Cluster Creation & Configuration: Guides full VPC-based Aurora MySQL cluster provisioning with tagging, confirmation gates, and tiered safety guardrails that block destructive operations like deletions and public accessibility. - Cost & Capacity Analysis: Bundled Python scripts compute Aurora serverless ACU sizing, I/O-Optimized breakeven points, and RI vs Database Savings Plan comparisons using live AWS pricing or offline fallback data. - Upgrade Planning: Provides major/minor version upgrade guidance with LTS recommendations and pre/post-upgrade checklists. - Use Case: A user asks whether to switch their db.r7g.2xlarge fleet to Aurora serverless; the skill loads the serverless-advisory sub-skill, runs the ACU calculator with their CPU metrics, and returns a cost comparison table with a recommendation. ## Quick Start Ask the assistant to help you create an Aurora MySQL cluster or estimate Aurora serverless ACU sizing for your current provisioned instance.

Frequently Asked Questions about amazon-aurora-mysql

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

FAQPage Schema
How do I size Aurora serverless ACUs for my workload?

Run the bundled acu_calculator.py script with your instance type, CPU p95 and max utilization, and storage size. It recommends min and max ACU settings, factors in connection and memory floors, and compares serverless versus provisioned monthly costs.

Reserved Instances vs Database Savings Plans for Aurora, which should I choose?

RIs offer deeper discounts (up to ~66% on 3-year terms) but lock you to one instance family, while DSP is family-agnostic but 1-year only and excludes older families like r6g and r5. The commitment_pricing_analyzer.py script compares both against your actual workload.

Does Aurora MySQL support express configuration for quick cluster creation?

No, express configuration is PostgreSQL-only. Aurora MySQL requires full VPC-based configuration including subnet groups, security groups, KMS keys, and parameter groups before cluster creation.

When should I switch to Aurora I/O-Optimized storage?

Switch when I/O costs exceed roughly 25% of your total cluster spend, using the io_optimized_analyzer.py script to compute the breakeven. Note the switch from Standard to I/O-Optimized is limited to once every 30 days.

Can the skill delete my Aurora cluster or make it publicly accessible?

No, destructive and high-risk operations like cluster deletion, failovers, major version upgrades, and public accessibility are hard-blocked by Tier 3 guardrails. The skill refuses and redirects you to the AWS Console or your change-control process with a safer alternative.

Why does commitment pricing analysis skip my Aurora cluster?

The analyzer returns skipped: true when a cluster has no DB instances attached, meaning there is no compute to price. This typically indicates a paused cluster, deleted instances, or a mid-migration state; resume the cluster and wait 14 days before re-running.