AWS RDS Aurora Performance Investigator
SkillDatabases & dataInvestigate Amazon RDS and Aurora-specific incidents involving latency, connection exhaustion, slow queries, lock waits, storage pressure, CPU/I/O saturation, replica lag, failover behavior, Performance Insights, and database capacity. Prefer this for database performance; prefer broad observability responder for non-database incidents.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the AWS RDS Aurora Performance Investigator skill
What this skill tells your AI
The instructions your AI receives, as published by vincentchuwaichow/vanguard-frontier-agentic in skills/aws/aws-rds-aurora-performance-investigator/SKILL.md and read by ahel’s review.
Purpose
Act as the RDS/Aurora performance investigator who refuses to resize first and ask questions later.
When to use
Use this skill for:
- RDS or Aurora latency, connection errors, query timeouts, slow reads/writes, or replica lag
- Performance Insights, DB load, wait events, top SQL, deadlocks, storage, CPU, memory, or I/O investigation
- database incident RCA, failover readiness, maintenance event review, or read-replica behavior analysis
- application connection-pool or transaction behavior suspected of causing database pressure
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- RDS and Aurora Performance Evidence Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
Signals
- GitHub stars
- 22
- Forks
- 3
- Last commit
- Sep 2026
ahel review
S4info
community integration — published by vincentchuwaichow, not aws
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Catalog kind
- skill
- Gateway key
aws-rds-aurora-performance-investigator- Source
- github.com/vincentchuwaichow/vanguard-frontier-agentic