Amazon Aurora Postgresql
AWSOfficialPublished by AWS
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Amazon Aurora PostgreSQL provides a structured approach to managing Aurora PostgreSQL clusters, offering sub-skills for cluster creation, serverless capacity planning, storage optimization, commitment-based cost analysis, and version upgrade planning. It includes safety guardrails for resource mutations and utilizes specific scripts for sizing and financial modeling. The skill is designed to route user requests to the appropriate domain-specific instructions while ensuring consistent resource tagging and adherence to AWS operational best practices.
What it does
- Provisions Aurora PostgreSQL clusters using either express or full configuration workflows.
- Analyzes Aurora serverless capacity requirements and ACU sizing.
- Evaluates the cost-benefit of switching to I/O-Optimized storage.
- Compares Reserved Instances and Database Savings Plans for cost optimization.
- Provides guidance and checklists for major and minor version upgrades.
- Applies mandatory resource tagging and safety guardrails for all cluster operations.
When to use it
- When you need to create or modify an Aurora PostgreSQL cluster.
- When planning capacity for Aurora serverless or evaluating ACU scaling.
- When assessing whether to switch to I/O-Optimized storage.
- When comparing Reserved Instances versus Database Savings Plans.
- When preparing for a major or minor PostgreSQL version upgrade.
Advantages
- Automates complex configuration decisions through a structured decision matrix.
- Provides consistent, script-based financial analysis for cost optimization.
- Enforces safety guardrails to prevent accidental production impact.
- Ensures standardized resource tagging for all created infrastructure.
- Simplifies connection management for express-configured clusters via IAM auth.
Usage examples
- “I need to set up a new Aurora PostgreSQL database.”
- The agent identifies the request as a cluster creation task, determines whether to use express or full configuration based on your requirements, and guides you through the provisioning process.
- “Should I switch my cluster to I/O-Optimized storage?”
- The agent evaluates your current I/O usage against the 25% cost threshold rule and provides a recommendation on whether the switch is cost-effective.
- “Help me compare Reserved Instances and Savings Plans for my cluster.”
- The agent runs a commitment pricing analysis to show potential savings over 1-year or 3-year terms based on your specific instance type and region.
- “How do I plan for a major version upgrade of my Aurora PostgreSQL cluster?”
- The agent provides a pre-upgrade checklist, recommends a target version, and suggests a blue/green deployment strategy.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/aws/amazon-aurora-postgresql/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip amazon-aurora-postgresql.zip -d .agents/skills
Documentation by AWS
Amazon Aurora PostgreSQL
A modular toolkit for Aurora PostgreSQL organized as a registry of sub-skills. Each sub-skill handles one domain of Aurora PostgreSQL work. The router matches user intent to the right sub-skill, then loads only the references needed. (For Aurora MySQL, use the amazon-aurora-mysql skill.)
Operating procedure (follow in order)
Route — match the request to a sub-skill using the Trigger phrases column (match on meaning, not exact wording), then confirm with the When to route here column.
Load —
file_readthe matched sub-skill'sreferences/{id}-instructions.mdand announce the path. Do not answer a matched sub-skill from general knowledge alone.Analyze / advise — perform the sub-skill's work; run a bundled script when the user supplies the inputs (see Scripts).
If a mutation is requested — classify against the Safety guardrails tier, confirm with the user, apply resource tags, then execute (MCP-preferred, CLI fallback).
Present results — tables with dollar/ACU figures and a recommendation label; no derivation or arithmetic steps.
Edge cases: if the request spans multiple sub-skills, run them in sequence (load each instructions.md in turn). If no sub-skill matches, answer directly from Aurora PostgreSQL knowledge. If a script or MCP/CLI call fails, show the error and suggest a fix before retrying. The numbered Global rules below are details that hang off these steps.
Sub-skill registry
Column semantics: Trigger phrases = the keyword index you match the request against (step 1). When to route here = the decision logic confirming the match. Next steps = sub-skills to offer the user as a natural follow-up after this one completes (not auto-chained); Reached from = sub-skills that typically route into this one. Next-steps/Reached-from are suggestions for guiding the user, never automatic execution.
| ID | Name | When to route here | Trigger phrases | Reached from | Next steps |
|---|---|---|---|---|---|
create | Create Cluster | Routes Aurora PostgreSQL cluster creation requests. Express configuration (single API call, no VPC) is the default — routes to express-create. Routes to full configuration when VPC, custom KMS, custom params, or a specific engine version is required. | create a cluster, new database, set up Aurora PostgreSQL, get started, need a PostgreSQL database, provision | — | express-create, serverless-advisory, io-optimized |
express-create | Express Configuration | Provisions Aurora PostgreSQL serverless via the single-API-call express flow. AWS-managed connectivity (no customer VPC). IAM-only authentication via Internet Access Gateway — no master password. Post-creation connection is via IAM auth token (aws rds generate-db-auth-token). Use when no VPC, custom KMS, or custom parameter group is required. Routes back to create for full configuration needs. | express configuration, express create, internet access gateway, single API call, Aurora PostgreSQL serverless quick start, no VPC, IAM auth token, how to connect to express cluster | create | — |
serverless-advisory | Aurora serverless Advisory | All Aurora serverless questions: ACU sizing, scale-to-zero behavior and compatibility, provisioned→serverless migration, capacity planning, and feature constraints. | ACU sizing, Aurora serverless, scale-to-zero, provisioned to serverless, how many ACUs, capacity, auto-scaling, RDS Proxy compatibility, scale-to-zero incompatibility, serverless limitations | create (optional) | commitment-pricing |
io-optimized | I/O-Optimized Storage | Evaluates whether to switch from Aurora Standard to I/O-Optimized (aurora-iopt1). Uses the 25% I/O cost threshold rule. | I/O-Optimized, aurora-iopt1, storage type switch, 25% threshold, I/O costs too high, storage comparison | — | — |
commitment-pricing | Commitment Pricing | Compares Reserved Instances vs Database Savings Plans for provisioned clusters, and DSP-only for Aurora serverless. 1yr vs 3yr analysis. | Reserved Instance, RI, Savings Plan, DSP, 1yr vs 3yr, commitment, cost optimization, overpaying | serverless-advisory (optional) | — |
upgrade-planning | Upgrade Planning | Major and minor version upgrade planning for Aurora PostgreSQL. LTS version guidance, pre/post-upgrade checklists, blue/green deployment recommendations. | upgrade, version, LTS, pre-upgrade checklist, post-upgrade, major version, minor version, end of life, deprecation | — | — |
Express vs Full configuration — decision matrix
When routing a create request (sub-skill create), pick the path with this matrix. Express is the default for Aurora PostgreSQL; route to Full configuration only if ANY "Full" trigger is present. Don't present the choice to the user — decide, then state which path and why.
| Requirement / signal | Express | Full config |
|---|---|---|
| Default PostgreSQL create, no special networking | ✅ default | — |
| Quick start / "no VPC setup" / "ready in seconds" | ✅ | — |
| Customer VPC, subnet group, or specific security group | — | ✅ required |
| Customer-managed KMS key (CMK) | — | ✅ required |
| Custom DB cluster parameter group at creation | — | ✅ required |
| Specific engine version pinned by the user | — | ✅ required (intent to pin = not express) |
| Aurora MySQL | n/a | use amazon-aurora-mysql (express is PG-only) |
Notes: any single Full trigger disqualifies express — name every trigger you matched in the routing statement. Express clusters are still customizable after creation (e.g. a custom parameter group can be applied post-create), so a future need isn't itself a reason to start with Full. Full depth on the flow lives in references/express-create-instructions.md and references/create-instructions.md — load those for the actual steps.
Global rules (apply to every sub-skill)
Execute, don't just suggest. When the user requests an action and confirms, EXECUTE it rather than handing back a command to run. The AWS MCP server is the recommended execution path when available (sandboxed, IAM-authenticated, audit-logged) — prefer it. When MCP tools are not available (e.g. Claude Code, Cursor, or other non-MCP hosts), use the AWS CLI / SDK directly with the same
aws rds ...operation. Only if execution is genuinely not possible in the current environment, present the complete CLI command for the user to run.Confirmation before mutation. MUST confirm with the user before any create or modify operation. Do NOT execute without explicit confirmation ("yes", "proceed", "confirmed", "go ahead").
Resource tagging (always apply on resource creation). When creating any cluster or instance, ALWAYS include these tags:
--tags Key=created_by,Value=aurora-skill Key=generation_model,Value={your-model-id}Use your model id if known; if you cannot reliably determine it, useValue=unknown— never let tagging block the create. Include these tags even if the user does not mention tagging. If the user provides additional tags, append these to their tags.Safety guardrails.
Tier 1 — Confirm (a yes/no confirmation is enough; no risk briefing required):
create-db-cluster,create-db-cluster --with-express-configurationcreate-db-instancemodify-db-cluster --serverless-v2-scaling-configuration(ACU scaling)modify-db-cluster --backup-retention-periodmodify-db-cluster --deletion-protection/--no-deletion-protectionmodify-db-cluster --enable-cloudwatch-logs-exportsmodify-db-cluster --preferred-backup-windowmodify-db-cluster --enable-http-endpoint(Data API)add-tags-to-resource,remove-tags-from-resource
Tier 2 — High-impact: state the specific risk, THEN confirm (spell out the impact before asking; do not call any API until the user confirms with that risk in front of them):
modify-db-cluster --storage-type— no downtime for most instance classes; requires restart for NVMe/Optimized Reads instances (r6gd, r6id, r8gd). Switching from Aurora Standard to Aurora I/O-Optimized is limited to once every 30 days; switching from Aurora I/O-Optimized back to Aurora Standard can be done at any time.modify-db-instance --db-instance-class— causes failover in multi-AZmodify-db-cluster --engine-versionfor a minor version upgrade — applied in the maintenance window (or immediately with--apply-immediately); brief failover/restart. State the target version and the restart impact, then confirm. (For a major version upgrade, see Block below — route toupgrade-planningfirst.)Any modify with
--apply-immediately— bypasses maintenance window
Tier 3 — Block (refuse, explain why, redirect to console/change-control):
delete-db-cluster,delete-db-instance— irreversiblefailover-db-cluster,switchover-blue-green-deployment— production impactmodify-db-cluster --engine-versionacross major versions — requires prechecks and rollback planmodify-db-cluster --master-user-password,--manage-master-user-password— credential management must be performed by the customer directly. Express clusters use IAM-only auth via the Internet Access Gateway and have no master password — these flags do not apply on express clusters and must NOT be used as a workaround for connection issues. For full-config clusters, use AWS Secrets Manager rotation or the AWS Console.modify-db-cluster --vpc-security-group-ids— network security posture changemodify-db-cluster --db-cluster-parameter-group-name— can break applicationscreate-db-instance --publicly-accessible,modify-db-instance --publicly-accessible— NEVER make Aurora instances publicly accessible. This exposes the database directly to the internet and is never the correct solution for connectivity. See secure connection alternatives below.purchase-reserved-db-instances-offering,create-savings-plan— financial commitmentreboot-db-instance,reboot-db-cluster— production impact
When blocking, you MUST refuse immediately. Do NOT call any AWS API. Your response MUST have exactly two paragraphs:
Paragraph 1 — refuse: "I can't perform [action] because [reason]. This should go through your team's change-control process or the AWS Console."
Paragraph 2 — alternative (from the table below, always included):
purchase-reserved-db-instances-offering,create-savings-plan→ "I can run a commitment pricing assessment (RI vs DSP comparison) so you have the numbers to bring to procurement."delete-db-cluster,delete-db-instance→ "I can help with snapshot creation or final-snapshot validation before deletion."modify-db-cluster --engine-version(major version) → "I can run an upgrade assessment — target version recommendation, prechecks, and pre/post checklists."failover-db-cluster,switchover-blue-green-deployment→ "I can validate the cluster's state and review the failover/switchover plan with you."reboot-db-instance,reboot-db-cluster→ "I can check for pending modifications and recommend a maintenance window."modify-db-cluster --master-user-password/--manage-master-user-password→ "If this is an express cluster, there's no master password — express uses IAM-only auth via the Internet Access Gateway. I can walk you through generating an IAM auth token to connect. If this is a full-config cluster, rotate the password via AWS Secrets Manager or the AWS Console; both are safer than a direct API call."--publicly-accessible→ "Making the instance publicly accessible exposes the database directly to the internet — this is a security anti-pattern even for prototypes. Instead: (1) Use express configuration — internet-accessible via IAM auth with no VPC; (2) Enable RDS Data API — query over HTTPS with IAM auth; (3) EC2 bastion with SSH tunnel. I can help you set up any of these."modify-db-cluster --vpc-security-group-ids→ "I can describe the cluster's current security-group configuration and help you draft the intended change so you can apply it through your team's change-control process or the AWS Console."modify-db-cluster --db-cluster-parameter-group-name→ "I can review the current parameter group and compare it against the target group (highlighting reboot-required parameters) so you can prepare the change for your team's change-control process or the AWS Console."
Never omit paragraph 2. A refusal without an alternative is incomplete.
Reference loading. Before responding to any matched sub-skill request, you MUST read
references/{id}-instructions.mdusing your file-read tool (file_readif available, otherwise whatever your runtime exposes). Do not answer a matched sub-skill from the registry summary alone. Announce the path in your reply.Express is a single CLI call. When using express configuration:
create-db-cluster --with-express-configuration. Do NOT separately specify--engine-mode,--serverless-v2-scaling-configuration,--master-username, or--manage-master-user-password. The express flag sets all of these automatically.Stay in scope. Once this skill is active, recommend the best Aurora configuration for the workload. Do not suggest non-AWS alternatives. For light workloads, recommend express with scale-to-zero.
Never fabricate. Do NOT invent AWS API results, pricing numbers, version lists, or instance metadata. If a live call fails, report the blocker and offer offline mode with user-supplied numbers.
Carry context forward. Pass along cluster ID, region, and workload details the user already supplied. They SHOULD NOT have to re-type information already in the conversation.
Broad requests. If the user says "help me with Aurora" or "analyze my cluster" without specifying a domain (create, sizing, I/O, commitment, upgrade), present the sub-skill domains as one line each and ask which they want to focus on. Do NOT silently pick a sub-skill and run it. Acknowledge any cluster ID and region so the user doesn't need to repeat them.
Out-of-scope topics. If the user asks about an Aurora feature not covered by a sub-skill (e.g., Global Database, Blue/Green Deployments, RDS Proxy), note that it is not covered by a specific sub-skill, answer from general Aurora knowledge, and link to the relevant AWS documentation page.
Credential safety. Do not create, store, or display long-lived credentials or DB passwords. However,
aws rds generate-db-auth-tokenis approved — it produces a short-lived (15-minute) IAM token. This is the required connection method for express clusters. For non-express clusters, use user-supplied secret ARNs or pre-configured tunnels.Present results clearly. Use tables with dollar figures, ACU numbers, and recommendation labels. Do NOT show derivation or arithmetic steps. Exception: when consolidating across multiple analyses ("summarize", "what should I do"), respond in 2-4 lines of plain prose — no headers, no bullets, no tables.
Scripts
Bundled scripts in scripts/ for offline analysis. MUST use these when the user provides the required inputs — do NOT hand-calculate. Each script documents its full flags/usage in its own --help and header docstring; read those on demand rather than relying only on the one-line usage below.
Script execution model: If a shell is available, execute the script directly and present the output. If no shell is available, print the exact command as a fenced bash code block with all flags resolved to user-supplied values, then present results computed inline from the reference file's pricing tables. (Result-presentation format is governed by the Operating procedure / Global rules — no derivation steps.)
| Script | Purpose | Usage |
|---|---|---|
acu_calculator.py | Aurora serverless ACU sizing | python3 scripts/acu_calculator.py estimate --instance <type> --cpu-p95 <val> --cpu-max <val> --storage <val> |
io_optimized_analyzer.py | I/O-Optimized breakeven | python3 scripts/io_optimized_analyzer.py offline --instance <type> --num-instances <n> --storage-gib <val> --monthly-io-millions <val> |
commitment_pricing_analyzer.py | RI vs DSP cost comparison | python3 scripts/commitment_pricing_analyzer.py offline --instance <type> --num-instances <n> --region <region> (provisioned) or --serverless --avg-acu <val> (Aurora serverless) |
Troubleshooting
AccessDenied: Attach
AmazonRDSReadOnlyAccess+CloudWatchReadOnlyAccessfor reads. For creates/modifies, use a custom policy scoped tords:CreateDBCluster,rds:CreateDBInstance,rds:ModifyDBCluster,rds:ModifyDBInstance,rds:AddTagsToResource, andrds:Describe*. See Identity and access management for Amazon Aurora.ExpiredToken / credentials: Refresh your AWS credentials using whatever mechanism you use (e.g. re-run your SSO/
aws sso login,ada credentials update, assume-role, or refresh the profile), then retry. Do not assume a specific credential tool.DBClusterNotFoundFault: Verify region and cluster ID.
Throttling: Retry once, then narrow scope.
Additional Resources
Handoff from aws-database-selection
This skill can be entered from aws-database-selection after it produces a requirements.json. When you see a path matching aws_dbs_requirements/*/requirements.json in conversation:
Read the artifact. Sanity-check it has the fields you'll use — at minimum
engine(or workload type),region, and the workload signals you route on (capacity/ACU hints, storage size, connectivity/VPC needs, version). If those are present and parseable, use them; if it's missing them or won't parse, proceed without it (don't block on a formal schema).Acknowledge relevant facts in 1-2 bold sentences.
Scope-check: if the artifact doesn't match Aurora (e.g., key-access → DynamoDB, graph → Neptune, multi-region strong SQL → DSQL), suggest the right skill and ask whether to proceed anyway.
Continue with this skill's sub-skill routing.
Files
- ATTRIBUTION.mdAdded by AutoGineer936 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md19.0 KiB
- references/commitment-pricing-basics.md5.4 KiB
- references/commitment-pricing-instructions.md7.3 KiB
- references/commitment-pricing-mechanics.md6.0 KiB
- references/commitment-pricing-scenarios.md4.4 KiB
- references/commitment-pricing-skipped-cluster.md4.1 KiB
- references/commitment-pricing-worked-examples.md5.8 KiB
- references/create-instructions.md7.3 KiB
- references/express-create-comparison.md7.6 KiB
- references/express-create-connect-iam.md2.8 KiB
- references/express-create-constraints.md9.4 KiB
- references/express-create-documentation-links.md3.8 KiB
- references/express-create-feature-overview.md7.4 KiB
- references/express-create-instructions.md7.8 KiB
- references/express-create-migration-pgdump.md2.0 KiB
- references/express-create-migration.md7.5 KiB
- references/express-create-use-cases.md7.7 KiB
- references/io-optimized-data-collection.md4.2 KiB
- references/io-optimized-instructions.md6.9 KiB
- references/io-optimized-pricing-tables.md6.3 KiB
- references/io-optimized-pricing.md3.0 KiB
- references/io-optimized-worked-examples.md4.6 KiB
- references/serverless-advisory-concepts.md3.2 KiB
- references/serverless-advisory-formulas-and-examples.md4.5 KiB
- references/serverless-advisory-instructions.md7.0 KiB
- references/serverless-advisory-migration.md6.9 KiB
- references/serverless-advisory-worked-examples.md7.2 KiB
- references/shared-foundation-security-considerations.md5.4 KiB
- references/upgrade-planning-documentation-links.md2.1 KiB
- references/upgrade-planning-instructions.md5.6 KiB
- references/upgrade-planning-lts-recommendation.md4.9 KiB
- references/upgrade-planning-mode-b-discovery.md4.9 KiB
- references/upgrade-planning-mode-b-prechecks-checklists.md4.7 KiB
- references/upgrade-planning-post-checklist.md2.9 KiB
- references/upgrade-planning-post-upgrade-detail.md6.4 KiB
- references/upgrade-planning-post-upgrade-validation.md4.2 KiB
- references/upgrade-planning-pre-checklist.md2.2 KiB
- references/upgrade-planning-prechecks-postgresql.md7.0 KiB
- references/upgrade-planning-query-load-postgresql.md6.6 KiB
- scripts/acu_calculator.pyScript35.8 KiB
- scripts/commitment_pricing_analyzer.pyScript32.5 KiB
- scripts/io_optimized_analyzer.pyScript25.8 KiB
scripts/acu_calculator.py
"""Aurora Serverless v2 ACU Calculator.
Estimates ACU sizing, costs, and generates provisioned-vs-serverless comparisons.
Pricing & instance data: pulls live from AWS Pricing API + EC2/RDS APIs when
boto3 credentials are available, falls back to static defaults (us-east-1,
static fallback) when offline or credentials are missing.
Usage:
python acu_calculator.py --help
python acu_calculator.py estimate --instance db.r6g.xlarge --cpu-p95 35 --cpu-max 72 --storage 500
python acu_calculator.py estimate --region eu-west-1 --instance db.r6g.2xlarge --cpu-p95 20 --cpu-max 55 --connections 200 --storage 1000 --working-set 12
"""
import argparse
import json
import math
import re
import sys
from typing import Any
# ---------------------------------------------------------------------------
# Static fallback data (us-east-1)
# Used when AWS APIs are unavailable (no credentials, offline, API errors).
# ---------------------------------------------------------------------------
_STATIC_ACU_PRICE_STANDARD = 0.12 # $/ACU-Hr
_STATIC_ACU_PRICE_IO_OPTIMIZED = 0.156 # $/ACU-Hr (30% premium)
_STATIC_STORAGE_STANDARD_PER_GIB = 0.10 # $/GiB-month
_STATIC_STORAGE_IO_OPT_PER_GIB = 0.225 # $/GiB-month
_STATIC_LAST_UPDATED = "2026-03-28"
_STATIC_REGION = "us-east-1"
# Static instance specs: {name: (vcpus, memory_gib, price_per_hour)}
_STATIC_INSTANCE_SPECS = {
"db.t3.medium": (2, 4, 0.082),
"db.t3.large": (2, 8, 0.164),
"db.t4g.medium": (2, 4, 0.073),
"db.t4g.large": (2, 8, 0.146),
"db.r5.large": (2, 16, 0.290),
"db.r5.xlarge": (4, 32, 0.580),
"db.r5.2xlarge": (8, 64, 1.160),
"db.r5.4xlarge": (16, 128, 2.320),
"db.r5.8xlarge": (32, 256, 4.640),
"db.r5.12xlarge": (48, 384, 6.960),
"db.r5.16xlarge": (64, 512, 9.280),
"db.r5.24xlarge": (96, 768, 13.920),
"db.r6g.large": (2, 16, 0.260),
"db.r6g.xlarge": (4, 32, 0.519),
"db.r6g.2xlarge": (8, 64, 1.038),
"db.r6g.4xlarge": (16, 128, 2.076),
"db.r6g.8xlarge": (32, 256, 4.152),
"db.r6g.12xlarge": (48, 384, 6.228),
"db.r6g.16xlarge": (64, 512, 8.304),
"db.r7g.large": (2, 16, 0.276),
"db.r7g.xlarge": (4, 32, 0.553),
"db.r7g.2xlarge": (8, 64, 1.106),
"db.r7g.4xlarge": (16, 128, 2.211),
"db.r7g.8xlarge": (32, 256, 4.422),
"db.r7g.12xlarge": (48, 384, 6.633),
"db.r7g.16xlarge": (64, 512, 8.844),
"db.r8g.large": (2, 16, 0.276),
"db.r8g.xlarge": (4, 32, 0.552),
"db.r8g.2xlarge": (8, 64, 1.104),
"db.r8g.4xlarge": (16, 128, 2.208),
"db.r8g.8xlarge": (32, 256, 4.416),
"db.r8g.12xlarge": (48, 384, 6.624),
"db.r8g.16xlarge": (64, 512, 8.832),
"db.r8g.24xlarge": (96, 768, 13.248),
"db.r8g.48xlarge": (192, 1536, 26.496),
}
# ---------------------------------------------------------------------------
# Constants (non-pricing, do not vary by region)
# ---------------------------------------------------------------------------
# Aurora bills storage on actual usage per GiB-month with dynamic resizing —
# there is no fixed minimum billed storage. (No MIN_STORAGE_GIB floor.)
HOURS_PER_MONTH = 730
ACU_MIN = 0.5
ACU_MAX = 256
IO_OPT_COMPUTE_MULTIPLIER = 1.30 # I/O-Optimized compute premium
GIB_PER_ACU = 2.0 # Each ACU provides ~2 GiB of memory
# Instance family -> ACU ratio
ACU_FAMILY_RATIO = {"r": 4, "m": 2, "t": 2, "c": 1, "x": 4}
# AWS region code -> Pricing API "location" name
_REGION_NAMES = {
"us-east-1": "US East (N. Virginia)",
"us-east-2": "US East (Ohio)",
"us-west-1": "US West (N. California)",
"us-west-2": "US West (Oregon)",
"eu-west-1": "EU (Ireland)",
"eu-west-2": "EU (London)",
"eu-west-3": "EU (Paris)",
"eu-central-1": "EU (Frankfurt)",
"eu-north-1": "EU (Stockholm)",
"ap-southeast-1": "Asia Pacific (Singapore)",
"ap-southeast-2": "Asia Pacific (Sydney)",
"ap-northeast-1": "Asia Pacific (Tokyo)",
"ap-northeast-2": "Asia Pacific (Seoul)",
"ap-south-1": "Asia Pacific (Mumbai)",
"ca-central-1": "Canada (Central)",
"sa-east-1": "South America (Sao Paulo)",
}
# ---------------------------------------------------------------------------
# Active pricing & catalog (mutable — overwritten by refresh_pricing())
# ---------------------------------------------------------------------------
ACU_PRICE_STANDARD = _STATIC_ACU_PRICE_STANDARD
ACU_PRICE_IO_OPTIMIZED = _STATIC_ACU_PRICE_IO_OPTIMIZED
STORAGE_STANDARD_PER_GIB = _STATIC_STORAGE_STANDARD_PER_GIB
STORAGE_IO_OPT_PER_GIB = _STATIC_STORAGE_IO_OPT_PER_GIB
INSTANCE_SPECS = dict(_STATIC_INSTANCE_SPECS)
# Tracks where the active data came from
_pricing_source: dict[str, Any] = {
"source": "static_fallback",
"region": _STATIC_REGION,
"last_updated": _STATIC_LAST_UPDATED,
"details": "Built-in us-east-1 defaults",
}
# ---------------------------------------------------------------------------
# Live AWS API fetchers
# ---------------------------------------------------------------------------
def _fetch_instance_pricing(region: str) -> dict[str, float]:
"""Fetch on-demand hourly pricing for Aurora instances via the Pricing API.
The Pricing API is only available in us-east-1 and ap-south-1, but returns
pricing for any region. Queries aurora-postgresql (covers all instance types).
Returns dict: instance_type -> price_per_hour.
"""
import boto3
location = _REGION_NAMES.get(region)
if not location:
raise ValueError(
f"Unknown region '{region}'. Supported: {', '.join(sorted(_REGION_NAMES))}"
)
pricing = boto3.client("pricing", region_name="us-east-1")
filters = [
{"Type": "TERM_MATCH", "Field": "databaseEngine", "Value": "Aurora PostgreSQL"},
{"Type": "TERM_MATCH", "Field": "location", "Value": location},
{"Type": "TERM_MATCH", "Field": "deploymentOption", "Value": "Single-AZ"},
{"Type": "TERM_MATCH", "Field": "termType", "Value": "OnDemand"},
]
prices = {}
paginator = pricing.get_paginator("get_products")
for page in paginator.paginate(ServiceCode="AmazonRDS", Filters=filters):
for item_json in page["PriceList"]:
item = json.loads(item_json) if isinstance(item_json, str) else item_json
attrs = item.get("product", {}).get("attributes", {})
instance_type = attrs.get("instanceType", "")
if not instance_type.startswith("db."):
continue
# Skip I/O-Optimized SKUs
if "IOOptimized" in attrs.get("usagetype", ""):
continue
terms = item.get("terms", {}).get("OnDemand", {})
for term in terms.values():
for dim in term.get("priceDimensions", {}).values():
try:
price = float(dim.get("pricePerUnit", {}).get("USD", "0"))
except (ValueError, TypeError):
continue
if price > 0:
prices[instance_type] = price
return prices
def _fetch_instance_pricing_bulk(region: str) -> dict[str, float]:
"""Fetch on-demand Aurora PostgreSQL pricing from the public AWS Bulk Pricing CSV.
No IAM credentials required — this is a publicly accessible HTTPS endpoint.
Used as a fallback when the Pricing API is not accessible (AccessDeniedException).
Returns dict: instance_type -> price_per_hour (Aurora Standard only).
"""
import csv
import io
import urllib.request
url = (
f"https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/"
f"current/{region}/index.csv"
)
req = urllib.request.Request(url, headers={"Accept-Encoding": "identity"})
with urllib.request.urlopen(req, timeout=30) as resp:
# CSV has metadata rows before the header; find the header row
raw = resp.read().decode("utf-8")
# AWS pricing CSVs start with metadata lines (FormatVersion, Disclaimer, etc.)
# before the actual column header. Find the header row (starts with "SKU").
lines = raw.splitlines()
header_idx = 0
for i, line in enumerate(lines):
if line.startswith('"SKU"') or line.startswith("SKU"):
header_idx = i
break
reader = csv.DictReader(io.StringIO("\n".join(lines[header_idx:])))
prices = {}
for row in reader:
if row.get("Database Engine") != "Aurora PostgreSQL":
continue
if row.get("Deployment Option") != "Single-AZ":
continue
# On-demand hourly rates only. The CSV also carries Reserved rows
# (including fixed-fee Quantity rows with values like 2530), which would
# otherwise overwrite the real hourly price via last-write-wins.
if row.get("TermType") != "OnDemand" or row.get("Unit") != "Hrs":
continue
instance_type = row.get("Instance Type", "")
if not instance_type.startswith("db."):
continue
# Skip I/O-Optimized SKUs. The column is "usageType" (camelCase) in the
# AWS RDS bulk CSV; I/O-Optimized is encoded there as InstanceUsageIOOptimized:*.
usage_type = row.get("usageType", "")
if "IOOptimized" in usage_type:
continue
try:
price = float(row.get("PricePerUnit", "0"))
except (ValueError, TypeError):
continue
if price > 0:
prices[instance_type] = price
return prices
def _fetch_acu_and_storage_pricing(region: str) -> dict:
"""Fetch ACU and storage pricing from the Pricing API.
Returns dict with acu_standard, acu_io_optimized, storage_standard,
storage_io_optimized keys.
"""
import boto3
location = _REGION_NAMES.get(region)
if not location:
raise ValueError(f"Unknown region '{region}'")
pricing = boto3.client("pricing", region_name="us-east-1")
result = {}
# ACU pricing
acu_filters = [
{"Type": "TERM_MATCH", "Field": "databaseEngine", "Value": "Aurora PostgreSQL"},
{"Type": "TERM_MATCH", "Field": "location", "Value": location},
{"Type": "TERM_MATCH", "Field": "termType", "Value": "OnDemand"},
]
paginator = pricing.get_paginator("get_products")
for page in paginator.paginate(ServiceCode="AmazonRDS", Filters=acu_filters):
for item_json in page["PriceList"]:
item = json.loads(item_json) if isinstance(item_json, str) else item_json
attrs = item.get("product", {}).get("attributes", {})
usagetype = attrs.get("usagetype", "")
if "ServerlessV2Usage" in usagetype and "IOOptimized" not in usagetype:
terms = item.get("terms", {}).get("OnDemand", {})
for term in terms.values():
for dim in term.get("priceDimensions", {}).values():
price = float(dim.get("pricePerUnit", {}).get("USD", "0"))
if price > 0:
result["acu_standard"] = price
result["acu_io_optimized"] = round(price * IO_OPT_COMPUTE_MULTIPLIER, 4)
# Storage pricing
storage_filters = [
{"Type": "TERM_MATCH", "Field": "databaseEngine", "Value": "Aurora PostgreSQL"},
{"Type": "TERM_MATCH", "Field": "location", "Value": location},
{"Type": "TERM_MATCH", "Field": "termType", "Value": "OnDemand"},
{"Type": "TERM_MATCH", "Field": "productFamily", "Value": "Database Storage"},
]
for page in paginator.paginate(ServiceCode="AmazonRDS", Filters=storage_filters):
for item_json in page["PriceList"]:
item = json.loads(item_json) if isinstance(item_json, str) else item_json
attrs = item.get("product", {}).get("attributes", {})
usagetype = attrs.get("usagetype", "")
terms = item.get("terms", {}).get("OnDemand", {})
for term in terms.values():
for dim in term.get("priceDimensions", {}).values():
price = float(dim.get("pricePerUnit", {}).get("USD", "0"))
if price <= 0:
continue
if "IOOptimized" in usagetype:
result["storage_io_optimized"] = price
elif "Aurora:StorageUsage" in usagetype:
result["storage_standard"] = price
return result
def _fetch_instance_catalog(region: str) -> dict[str, tuple]:
"""Discover Aurora instance types via RDS + EC2 APIs.
Returns dict: instance_type -> (vcpus, memory_gib, 0.0).
Price is 0.0 here; caller merges with pricing data.
"""
import boto3
rds = boto3.client("rds", region_name=region)
instances = {}
for engine in ("aurora-postgresql",):
try:
paginator = rds.get_paginator("describe_orderable_db_instance_options")
for page in paginator.paginate(Engine=engine):
for opt in page.get("OrderableDBInstanceOptions", []):
name = opt.get("DBInstanceClass", "")
if name.startswith("db.") and name != "db.serverless":
instances[name] = {"vcpus": 0, "memory_gib": 0.0}
except Exception:
pass
if not instances:
return {}
# Get vCPU/memory from EC2 describe_instance_types
ec2 = boto3.client("ec2", region_name=region)
ec2_names = [name.replace("db.", "", 1) for name in instances]
for i in range(0, len(ec2_names), 100):
batch = ec2_names[i : i + 100]
try:
resp = ec2.describe_instance_types(InstanceTypes=batch)
for it in resp.get("InstanceTypes", []):
db_name = "db." + it["InstanceType"]
if db_name in instances:
instances[db_name]["vcpus"] = it.get("VCpuInfo", {}).get("DefaultVCpus", 0)
instances[db_name]["memory_gib"] = (
it.get("MemoryInfo", {}).get("SizeInMiB", 0) / 1024
)
except Exception:
# Try one by one for families EC2 doesn't know about
for ec2_name in batch:
try:
resp = ec2.describe_instance_types(InstanceTypes=[ec2_name])
for it in resp.get("InstanceTypes", []):
db_name = "db." + it["InstanceType"]
if db_name in instances:
instances[db_name]["vcpus"] = it.get("VCpuInfo", {}).get(
"DefaultVCpus", 0
)
instances[db_name]["memory_gib"] = (
it.get("MemoryInfo", {}).get("SizeInMiB", 0) / 1024
)
except Exception:
pass
# Convert to tuple format, drop entries missing vCPU/memory
catalog = {}
for name, spec in instances.items():
if spec["vcpus"] > 0 and spec["memory_gib"] > 0:
catalog[name] = (spec["vcpus"], spec["memory_gib"], 0.0)
return catalog
def refresh_pricing(region: str = "us-east-1") -> dict:
"""Refresh all pricing and instance data from AWS APIs.
Tries live APIs first. On any failure, falls back to static defaults
and reports what succeeded and what didn't.
Returns a summary dict describing the pricing source.
"""
global ACU_PRICE_STANDARD, ACU_PRICE_IO_OPTIMIZED
global STORAGE_STANDARD_PER_GIB, STORAGE_IO_OPT_PER_GIB
global INSTANCE_SPECS, _pricing_source
errors = []
live_instances = 0
live_prices = 0
live_acu = False
# 1. Try to fetch the instance catalog (RDS + EC2)
api_catalog = {}
try:
api_catalog = _fetch_instance_catalog(region)
live_instances = len(api_catalog)
except Exception as e:
errors.append(f"Instance catalog: {e}")
# 2. Try to fetch instance pricing (Pricing API, then public bulk CSV fallback)
instance_prices = {}
try:
instance_prices = _fetch_instance_pricing(region)
live_prices = len(instance_prices)
except Exception as e:
errors.append(f"Instance pricing (API): {e}")
# Fallback: public bulk pricing CSV (no IAM credentials needed)
try:
instance_prices = _fetch_instance_pricing_bulk(region)
live_prices = len(instance_prices)
if live_prices > 0:
errors[-1] += " [recovered via bulk pricing CSV]"
except Exception as e2:
errors.append(f"Instance pricing (bulk CSV): {e2}")
# 3. Try to fetch ACU + storage pricing
try:
acu_data = _fetch_acu_and_storage_pricing(region)
if "acu_standard" in acu_data:
ACU_PRICE_STANDARD = acu_data["acu_standard"]
ACU_PRICE_IO_OPTIMIZED = acu_data.get(
"acu_io_optimized",
round(acu_data["acu_standard"] * IO_OPT_COMPUTE_MULTIPLIER, 4),
)
live_acu = True
if "storage_standard" in acu_data:
STORAGE_STANDARD_PER_GIB = acu_data["storage_standard"]
if "storage_io_optimized" in acu_data:
STORAGE_IO_OPT_PER_GIB = acu_data["storage_io_optimized"]
except Exception as e:
errors.append(f"ACU/storage pricing: {e}")
# 4. Merge: start with static, overlay API catalog, overlay prices
merged = dict(_STATIC_INSTANCE_SPECS)
for name, (vcpus, mem, _) in api_catalog.items():
price = instance_prices.get(name, 0.0)
# If API didn't return a price, keep static price if we have one
if price == 0.0 and name in _STATIC_INSTANCE_SPECS:
price = _STATIC_INSTANCE_SPECS[name][2]
merged[name] = (vcpus, mem, price)
# For instances in static but not in API catalog, update price if available
for name in _STATIC_INSTANCE_SPECS:
if name not in api_catalog and name in instance_prices:
v, m, _ = _STATIC_INSTANCE_SPECS[name]
merged[name] = (v, m, instance_prices[name])
INSTANCE_SPECS = merged
# Determine source description
if not errors:
source = "live"
details = (
f"Live AWS APIs ({region}): {live_instances} instance types, "
f"{live_prices} prices, ACU=${ACU_PRICE_STANDARD}/hr"
)
elif live_prices > 0 or live_acu:
source = "partial_live"
details = (
f"Partial live data ({region}): {live_instances} instances, "
f"{live_prices} prices. Gaps filled from static defaults. "
f"Errors: {'; '.join(errors)}"
)
else:
# Full fallback
source = "static_fallback"
INSTANCE_SPECS = dict(_STATIC_INSTANCE_SPECS)
ACU_PRICE_STANDARD = _STATIC_ACU_PRICE_STANDARD
ACU_PRICE_IO_OPTIMIZED = _STATIC_ACU_PRICE_IO_OPTIMIZED
STORAGE_STANDARD_PER_GIB = _STATIC_STORAGE_STANDARD_PER_GIB
STORAGE_IO_OPT_PER_GIB = _STATIC_STORAGE_IO_OPT_PER_GIB
details = (
f"Static fallback (us-east-1, {_STATIC_LAST_UPDATED}). "
f"Live fetch failed: {'; '.join(errors)}"
)
_pricing_source = {
"source": source,
"region": region,
"last_updated": _STATIC_LAST_UPDATED if source == "static_fallback" else "now",
"details": details,
"instance_count": len(INSTANCE_SPECS),
"acu_price_standard": ACU_PRICE_STANDARD,
"storage_price_standard": STORAGE_STANDARD_PER_GIB,
}
if errors:
_pricing_source["errors"] = errors
return _pricing_source
def get_pricing_source() -> dict:
"""Return metadata about the active pricing data source."""
return dict(_pricing_source)
# ---------------------------------------------------------------------------
# Core calculation functions
# ---------------------------------------------------------------------------
def round_up_to_half(value: float) -> float:
"""Round up to nearest 0.5 ACU."""
return math.ceil(value * 2) / 2
def family_ratio(instance_type: str) -> int:
"""Get ACU ratio for an instance family."""
m = re.match(r"db\.([a-z])", instance_type)
if m:
return ACU_FAMILY_RATIO.get(m.group(1), 4)
return 4
def get_instance_specs(instance_type: str) -> tuple:
"""Get (vcpus, memory_gib, price_per_hour) for an instance type."""
if instance_type in INSTANCE_SPECS:
return INSTANCE_SPECS[instance_type]
raise ValueError(
f"Unknown instance type: {instance_type}. "
f"Supported: {', '.join(sorted(INSTANCE_SPECS.keys()))}"
)
def estimate_acu(
cpu_p95: float,
cpu_max: float,
vcpus: int,
instance_type: str,
cpu_avg: float = 0,
) -> dict:
"""Estimate ACU needed for a workload.
Returns dict with typical ACU, min/max recommendations, and breakdown.
"""
ratio = family_ratio(instance_type)
# Typical ACU: weighted 95/5 blend
weighted_cpu = (cpu_p95 * 0.95 + cpu_max * 0.05) / 100
raw_typical = weighted_cpu * vcpus * ratio
typical_acu = round_up_to_half(raw_typical)
typical_acu = max(ACU_MIN, min(typical_acu, ACU_MAX))
# Peak ACU
raw_peak = (cpu_max / 100) * vcpus * ratio
peak_acu = round_up_to_half(raw_peak)
# Average ACU (for min recommendation)
if cpu_avg > 0:
avg_acu = round_up_to_half((cpu_avg / 100) * vcpus * ratio)
else:
# Estimate average as 60% of P95 when not provided
avg_acu = round_up_to_half((cpu_p95 * 0.6 / 100) * vcpus * ratio)
exceeds_capacity = raw_typical > ACU_MAX or raw_peak > ACU_MAX
return {
"typical_acu": typical_acu,
"peak_acu": peak_acu,
"avg_acu": avg_acu,
"raw_typical": round(raw_typical, 2),
"raw_peak": round(raw_peak, 2),
"family_ratio": ratio,
"exceeds_capacity": exceeds_capacity,
}
def recommend_min_max(
acu_result: dict,
connections: int = 0,
working_set_gib: float = 0,
) -> dict:
"""Recommend min/max ACU settings."""
avg_acu = acu_result["avg_acu"]
typical_acu = acu_result["typical_acu"]
peak_acu = acu_result["peak_acu"]
# Connection floor
conn_mem_gib = connections * 10 / 1024 # ~10 MB per connection average
conn_acu = round_up_to_half(conn_mem_gib / GIB_PER_ACU)
# Memory floor (advisory — working set)
mem_acu = round_up_to_half(working_set_gib / GIB_PER_ACU) if working_set_gib > 0 else 0
# Min: based on avg CPU + connection floor (uncapped first, so we can detect
# a baseline that already exceeds serverless limits).
raw_min = max(ACU_MIN, avg_acu, conn_acu)
# Max: peak + 30% headroom, at least 1.5x typical
recommended_max = round_up_to_half(peak_acu * 1.3)
recommended_max = max(recommended_max, round_up_to_half(typical_acu * 1.5))
recommended_max = min(recommended_max, ACU_MAX)
# The workload's baseline doesn't fit a single serverless instance when the
# uncapped min exceeds the ACU ceiling or the (capped) max — flag it, mirroring
# estimate_acu's exceeds_capacity.
exceeds_capacity = raw_min > ACU_MAX or raw_min > recommended_max
# Cap min at ACU_MAX and enforce the invariant: min must never exceed max.
recommended_min = min(raw_min, ACU_MAX, recommended_max)
# Memory advisory
memory_advisory = None
if mem_acu > recommended_min:
memory_advisory = (
f"Working set needs {mem_acu} ACU ({working_set_gib:.1f} GiB / "
f"{GIB_PER_ACU} GiB per ACU). Your min ACU ({recommended_min}) is below this. "
f"Setting min to {mem_acu} ACU keeps the working set cached and avoids "
f"cold-cache I/O penalties on scale-up. Trade-off: higher baseline cost."
)
return {
"recommended_min": recommended_min,
"recommended_max": recommended_max,
"connection_floor_acu": conn_acu,
"memory_floor_acu": mem_acu,
"memory_advisory": memory_advisory,
"exceeds_capacity": exceeds_capacity,
}
def calculate_costs(
typical_acu: float,
min_acu: float,
max_acu: float,
storage_gib: float,
provisioned_instance: str,
num_provisioned_instances: int = 1,
exceeds_capacity: bool = False,
) -> dict:
"""Calculate and compare serverless vs provisioned costs."""
_, _, price_per_hour = get_instance_specs(provisioned_instance)
# Provisioned cost
prov_compute = price_per_hour * HOURS_PER_MONTH * num_provisioned_instances
prov_storage = storage_gib * STORAGE_STANDARD_PER_GIB
prov_total = prov_compute + prov_storage
# Serverless cost (typical steady-state)
sv_compute = typical_acu * ACU_PRICE_STANDARD * HOURS_PER_MONTH
sv_storage = storage_gib * STORAGE_STANDARD_PER_GIB
sv_total = sv_compute + sv_storage
# Serverless cost range
sv_low = min_acu * ACU_PRICE_STANDARD * HOURS_PER_MONTH + sv_storage
sv_high = max_acu * ACU_PRICE_STANDARD * HOURS_PER_MONTH + sv_storage
# Savings
savings = prov_total - sv_total
savings_pct = (savings / prov_total * 100) if prov_total > 0 else 0
# Recommendation logic
if exceeds_capacity:
recommendation = "not_recommended"
reason = (
f"Workload's baseline/peak demand exceeds the {ACU_MAX:.0f} ACU serverless "
f"maximum. Stay with provisioned or split across multiple serverless clusters."
)
elif savings_pct > 10 and sv_high <= prov_total * 2:
recommendation = "recommended"
reason = (
f"Serverless saves ${savings:.0f}/mo ({savings_pct:.0f}%) vs provisioned. "
f"Cost range: ${sv_low:.0f}–${sv_high:.0f}/mo."
)
elif savings_pct > 10:
recommendation = "consider"
reason = (
f"Typical cost is lower (${sv_total:.0f} vs ${prov_total:.0f}/mo), but "
f"peak cost could reach ${sv_high:.0f}/mo. Variable workloads benefit; "
f"sustained peaks may not."
)
elif savings_pct > -5:
recommendation = "consider"
reason = (
f"Similar cost (${sv_total:.0f} vs ${prov_total:.0f}/mo). Choose serverless "
f"for auto-scaling and zero management overhead."
)
elif savings_pct > -30:
recommendation = "more_expensive"
reason = (
f"Serverless costs ${abs(savings):.0f}/mo more than provisioned "
f"(${sv_total:.0f} vs ${prov_total:.0f}/mo)."
)
else:
recommendation = "not_recommended"
reason = (
f"Serverless at ${sv_total:.0f}/mo is {abs(savings_pct):.0f}% more expensive "
f"than provisioned at ${prov_total:.0f}/mo. Sustained workloads are cheaper "
f"on provisioned instances."
)
return {
"provisioned": {
"instance_type": provisioned_instance,
"num_instances": num_provisioned_instances,
"compute_monthly": round(prov_compute, 2),
"storage_monthly": round(prov_storage, 2),
"total_monthly": round(prov_total, 2),
},
"serverless": {
"typical_acu": typical_acu,
"compute_monthly": round(sv_compute, 2),
"storage_monthly": round(sv_storage, 2),
"total_monthly": round(sv_total, 2),
"cost_range": {
"low": round(sv_low, 2),
"typical": round(sv_total, 2),
"high": round(sv_high, 2),
},
},
"savings_monthly": round(savings, 2),
"savings_pct": round(savings_pct, 1),
"recommendation": recommendation,
"reason": reason,
}
def format_table(result: dict) -> str:
"""Format result as a readable text table."""
lines = []
source = result.get("pricing_source", _pricing_source)
tag = source.get("source", "static_fallback").replace("_", " ").title()
lines.append("=" * 65)
lines.append(" Aurora Serverless v2 — ACU Estimate & Cost Comparison")
lines.append(f" Pricing: {tag} ({source.get('region', '?')})")
lines.append("=" * 65)
# ACU settings
acu = result["acu_settings"]
lines.append("")
lines.append(" ACU Configuration")
lines.append(" " + "-" * 45)
lines.append(f" Recommended Min ACU: {acu['recommended_min']:.1f}")
lines.append(f" Recommended Max ACU: {acu['recommended_max']:.1f}")
lines.append(f" Typical ACU: {acu['typical_acu']:.1f}")
lines.append(f" Peak ACU: {acu['peak_acu']:.1f}")
if acu.get("connection_floor_acu", 0) > 0:
lines.append(f" Connection floor: {acu['connection_floor_acu']:.1f} ACU")
if acu.get("memory_floor_acu", 0) > 0:
lines.append(f" Memory floor: {acu['memory_floor_acu']:.1f} ACU (advisory)")
if acu.get("memory_advisory"):
lines.append(f" NOTE: {acu['memory_advisory']}")
# Cost comparison
costs = result["cost_comparison"]
prov = costs["provisioned"]
sv = costs["serverless"]
lines.append("")
lines.append(" Monthly Cost Comparison")
lines.append(" " + "-" * 45)
lines.append(f" {'':30s} {'Provisioned':>14s} {'Serverless':>14s}")
lines.append(
f" {'Compute':30s} {'$'+str(prov['compute_monthly']):>14s} {'$'+str(sv['compute_monthly']):>14s}"
)
lines.append(
f" {'Storage':30s} {'$'+str(prov['storage_monthly']):>14s} {'$'+str(sv['storage_monthly']):>14s}"
)
lines.append(
f" {'Total':30s} {'$'+str(prov['total_monthly']):>14s} {'$'+str(sv['total_monthly']):>14s}"
)
lines.append("")
lines.append(
f" Serverless cost range: ${sv['cost_range']['low']:.0f} – ${sv['cost_range']['high']:.0f}/mo"
)
lines.append(f" Savings: ${costs['savings_monthly']:.0f}/mo ({costs['savings_pct']:.0f}%)")
# Recommendation
lines.append("")
lines.append(f" Recommendation: {costs['recommendation'].upper()}")
lines.append(f" {costs['reason']}")
lines.append("")
lines.append("=" * 65)
return "\n".join(lines)
def run_estimate(args) -> dict:
"""Run full estimation from CLI arguments."""
vcpus, memory_gib, price = get_instance_specs(args.instance)
acu_result = estimate_acu(
cpu_p95=args.cpu_p95,
cpu_max=args.cpu_max,
vcpus=vcpus,
instance_type=args.instance,
cpu_avg=args.cpu_avg,
)
min_max = recommend_min_max(
acu_result,
connections=args.connections,
working_set_gib=args.working_set,
)
# Workload overflows serverless if EITHER signal trips: estimate_acu's
# typical/peak check, or recommend_min_max's baseline-min check.
exceeds_capacity = acu_result["exceeds_capacity"] or min_max["exceeds_capacity"]
costs = calculate_costs(
typical_acu=acu_result["typical_acu"],
min_acu=min_max["recommended_min"],
max_acu=min_max["recommended_max"],
storage_gib=args.storage,
provisioned_instance=args.instance,
num_provisioned_instances=args.num_instances,
exceeds_capacity=exceeds_capacity,
)
return {
"input": {
"instance_type": args.instance,
"vcpus": vcpus,
"memory_gib": memory_gib,
"cpu_p95": args.cpu_p95,
"cpu_max": args.cpu_max,
"cpu_avg": args.cpu_avg,
"connections": args.connections,
"working_set_gib": args.working_set,
"storage_gib": args.storage,
"num_instances": args.num_instances,
},
"acu_settings": {
"recommended_min": min_max["recommended_min"],
"recommended_max": min_max["recommended_max"],
"typical_acu": acu_result["typical_acu"],
"peak_acu": acu_result["peak_acu"],
"avg_acu": acu_result["avg_acu"],
"connection_floor_acu": min_max["connection_floor_acu"],
"memory_floor_acu": min_max["memory_floor_acu"],
"memory_advisory": min_max["memory_advisory"],
"exceeds_capacity": exceeds_capacity,
},
"cost_comparison": costs,
"pricing_source": get_pricing_source(),
}
def main():
# Shared flags accepted both before the subcommand and after it (so e.g.
# `... estimate --region X --offline` and `... --region X estimate` both work).
# Defaults are SUPPRESSed here so a subparser copy does NOT re-apply its own
# default and clobber a value the user passed before the subcommand; the real
# defaults are resolved once, after parsing, below.
common = argparse.ArgumentParser(add_help=False)
common.add_argument(
"--region",
default=argparse.SUPPRESS,
help="AWS region for pricing (default: us-east-1). "
"Live pricing requires boto3 + AWS credentials.",
)
common.add_argument(
"--offline",
action="store_true",
default=argparse.SUPPRESS,
help="Skip live API calls, use static fallback data only.",
)
parser = argparse.ArgumentParser(
description="Aurora Serverless v2 ACU Calculator", parents=[common]
)
sub = parser.add_subparsers(dest="command")
# estimate command
est = sub.add_parser("estimate", parents=[common], help="Estimate ACU sizing and compare costs")
est.add_argument(
"--instance", required=True, help="Current provisioned instance type (e.g., db.r6g.xlarge)"
)
est.add_argument("--cpu-p95", type=float, required=True, help="P95 CPU utilization (0-100)")
est.add_argument("--cpu-max", type=float, required=True, help="Maximum CPU utilization (0-100)")
est.add_argument(
"--cpu-avg",
type=float,
default=0,
help="Average CPU utilization (0-100), estimated if omitted",
)
est.add_argument("--connections", type=int, default=0, help="Peak connection count")
est.add_argument("--working-set", type=float, default=0, help="Working set size in GiB")
est.add_argument("--storage", type=float, default=10, help="Storage in GiB")
est.add_argument(
"--num-instances",
type=int,
default=1,
help="Number of provisioned instances (for cost comparison)",
)
est.add_argument("--format", choices=["json", "table"], default="json", help="Output format")
# list-instances command
sub.add_parser(
"list-instances",
parents=[common],
help="List supported instance types with specs and pricing",
)
# pricing-source command
sub.add_parser(
"pricing-source", parents=[common], help="Show where pricing data is coming from"
)
args = parser.parse_args()
# Resolve shared-flag defaults once (they were SUPPRESSed on both the main and
# subparsers so neither position clobbers the other; an explicit flag in either
# position lands in the namespace, otherwise we apply the default here).
if not hasattr(args, "region"):
args.region = "us-east-1"
if not hasattr(args, "offline"):
args.offline = False
# Refresh pricing (live or offline)
if not args.offline:
source = refresh_pricing(region=args.region)
if args.command != "pricing-source":
# Brief status line to stderr so it doesn't pollute JSON output
tag = (
"LIVE"
if source["source"] == "live"
else ("PARTIAL" if source["source"] == "partial_live" else "STATIC")
)
print(
f"[Pricing: {tag} — {source['region']}, "
f"{source['instance_count']} instances, "
f"ACU=${source['acu_price_standard']}/hr]",
file=sys.stderr,
)
if args.command == "estimate":
result = run_estimate(args)
if args.format == "table":
print(format_table(result))
else:
print(json.dumps(result, indent=2))
elif args.command == "list-instances":
source = get_pricing_source()
print(f"Pricing source: {source['source']} ({source['region']})")
print(f"{'Instance Type':<25s} {'vCPUs':>6s} {'Memory':>8s} {'$/hr':>8s} {'$/mo':>10s}")
print("-" * 62)
for name in sorted(INSTANCE_SPECS.keys()):
v, m, p = INSTANCE_SPECS[name]
print(f"{name:<25s} {v:>6d} {m:>6.0f} GiB {p:>8.3f} {p*730:>10.2f}")
print(f"\nTotal: {len(INSTANCE_SPECS)} instance types")
elif args.command == "pricing-source":
print(json.dumps(get_pricing_source(), indent=2))
else:
parser.print_help()
if __name__ == "__main__":
main()
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs Python
Security
What our scanner noticed· Low risk
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · skills/specialized-skills/database-skills/amazon-aurora-postgresql · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS or AWS.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download amazon-aurora-postgresql.zip