[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAWMVPPC336F502CNEF4H1":3,"skill-same:01M7AAWMVPPC336F502CNEF4H1":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7AAWMVPPC336F502CNEF4H1","rds-bluegreen-deployer",null,"Deploys Amazon RDS Blue\u002FGreen Deployments with production defaults: blue\u002Fgreen creation (create-blue-green-deployment — source to staging clone), switchover (1-minute downtime via DNS update), traffic rerouting, switchover timeout configuration, green environment validation, database changes in green (major version upgrade, parameter group changes, schema changes), replication from blue to green (logical replication), delete green after successful switch, Aurora MySQL\u002FPostgreSQL support, Blue\u002FGreen limitations (engine version constraints, storage type, read replica topology), monitoring during green validation (CloudWatch Enhanced Monitoring), application connection string update. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating an RDS blue\u002Fgreen deployment, performing. Triggers: create blue green deployment, rds blue green switchover, zero downtime database upgrade, aurora blue green, rds major version upgrade green, green environment validation, switch over blue green.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rds-bluegreen-deployer\ndescription: 'Deploys Amazon RDS Blue\u002FGreen Deployments with production defaults: blue\u002Fgreen creation (create-blue-green-deployment — source to staging clone), switchover (1-minute downtime via DNS update), traffic rerouting, switchover timeout configuration, green environment validation, database changes in green (major version upgrade, parameter group changes, schema changes), replication from blue to green (logical replication), delete green after successful switch, Aurora MySQL\u002FPostgreSQL support, Blue\u002FGreen limitations (engine version constraints, storage type, read replica topology), monitoring during green validation (CloudWatch Enhanced Monitoring), application connection string update. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating an RDS blue\u002Fgreen deployment, performing. Triggers: create blue green deployment, rds blue green switchover, zero downtime database upgrade, aurora blue green, rds major version upgrade green, green environment validation, switch over blue green.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with RDS access. Works with Terraform aws_rds_blue_green_deployment resource and CloudFormation AWS::RDS::BlueGreenDeployment templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Databases\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, rds, blue-green, cloudops, deploy, databases, aurora, switchover, zero-downtime, upgrades\n  dependencies: aws-orchestrator\n  keywords: aws, rds, blue green, blue\u002Fgreen deployment, cloudops, deploy, zero downtime, switchover, aurora, major version upgrade, parameter group, schema change, green environment, staging clone, dns switch\n  when_to_use: Invoke when the user wants to create an RDS Blue\u002FGreen Deployment, perform a zero-downtime database upgrade (major version, parameter group, or schema changes), switch over a blue\u002Fgreen deployment, validate the green environment before switchover, delete a green environment after successful switchover, or understand Blue\u002FGreen limitations. Do NOT invoke for standard RDS modifications without Blue\u002FGreen (use modify-db-instance directly), Aurora Global Database failover, or Multi-AZ failover.\n---\n\n# RDS Blue\u002FGreen Deployer\n\nAn AWS CloudOps agent skill that deploys Amazon RDS Blue\u002FGreen\nDeployments with correct defaults. The skill walks the operator\nthrough blue\u002Fgreen creation (source to staging clone), database\nchanges in the green environment (major version upgrade, parameter\nchanges, schema changes), green validation, switchover (1-minute\ndowntime via DNS update), application connection string implications,\nand green cleanup, captures upgrade decisions, explains why each\ndefault matters, and emits a READY_TO_DEPLOY checklist with copy-\npasteable verification commands.\n\n## Activation keywords\n\ncreate blue green deployment, RDS blue green switchover, zero downtime\ndatabase upgrade, Aurora blue green, RDS major version upgrade green,\ngreen environment validation, switch over blue green.\n\n## STRICT output contract\n\nWhen this skill is invoked with an RDS Blue\u002FGreen Deployment request\n(create a blue\u002Fgreen deployment, perform zero-downtime upgrade,\nswitchover, validate green, delete green, or a partial configuration),\nthe agent MUST respond with the READY_TO_DEPLOY checklist defined in\nthe \"Output format\" section using the literal all-caps labels\n`BLUE_GREEN:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface the checklist with prose, headings, or disclaimers —\nemit the block as the first lines of the response. This contract is\nwhat assertion-based evals and downstream deployment pipelines rely\non; deviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before deploying |\n| Step 1 — Blue\u002FGreen model (source to staging clone) | Core deployment model |\n| Step 2 — Engine and version support | Aurora MySQL\u002FPostgreSQL, RDS MySQL\u002FPostgreSQL |\n| Step 3 — Create the blue\u002Fgreen deployment | Creation step |\n| Step 4 — Database changes in green | Major version, parameter, schema changes |\n| Step 5 — Green environment validation | Pre-switchover validation |\n| Step 6 — Switchover (1-minute downtime) | DNS-based traffic rerouting |\n| Step 7 — Switchover timeout configuration | Timeout control |\n| Step 8 — Application connection string update | DNS\u002FCNAME implications |\n| Step 9 — Delete green after successful switch | Cleanup |\n| Step 10 — Blue\u002FGreen limitations | Engine version, storage, topology constraints |\n| Step 11 — Monitoring during green validation | CloudWatch metrics |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fswitchover-and-dns.md | Switchover + DNS detail |\n| references\u002Fgreen-validation-and-changes.md | Validation + changes detail |\n\n## Mindset\n\n**One-line takeaway:** Blue\u002FGreen creates a full staging clone\n(green) of your production database (blue), replicates changes from\nblue to green, lets you make destructive changes (major version\nupgrade, parameter changes) in green without touching production,\nvalidates green, then switches traffic in about 1 minute via a DNS\nupdate. The green environment is a full clone — it costs 2x during\nvalidation.\n\nThree misconceptions dominate RDS Blue\u002FGreen misdesign at deployment\ntime:\n\n- **\"Blue\u002FGreen is zero-downtime.\"** It is near-zero-downtime. The\n  switchover takes approximately 1 minute, during which existing\n  connections are briefly dropped and re-established. Applications\n  MUST use connection retry logic. The DNS switch is transparent to\n  applications that resolve the endpoint at connection time, but\n  long-lived connections will break and need reconnect.\n\n- **\"I can make changes in blue while green is being created.\"** You\n  should NOT. The green environment is a point-in-time clone of blue.\n  Changes made to blue after green creation are replicated via logical\n  replication, but DDL changes (schema changes) in blue during the\n  Blue\u002FGreen lifecycle can break replication. Make changes ONLY in\n  green. Blue stays untouched until switchover.\n\n- **\"Green is free — it is just a staging copy.\"** Green is a FULL\n  clone — complete instance\u002Fstorage\u002FIO. You pay 2x database costs\n  during the entire Blue\u002FGreen lifecycle. Delete green promptly after\n  successful switchover to stop the duplicate billing. The cost is the\n  trade-off for zero-downtime upgrades.\n\n## Configuration dependency graph (novel heuristic)\n\nThe configuration dependency graph and cross-dependency gotchas moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: the 2x cost window\n\nThe 2x cost window timeline and key implication moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: what changes go in green vs blue\n\nThe green-vs-blue change matrix moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: switchover downtime characteristics\n\nSwitchover downtime phase breakdown and retry guidance moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Prerequisites (verify before deploying)\n\nBefore emitting deployment commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Source DB (blue) exists | Blue\u002FGreen clones an existing DB | `aws rds describe-db-instances --db-instance-identifier \u003Cid>` |\n| Engine supports Blue\u002FGreen | Not all engines\u002Fversions support it | Check supported engines (Aurora MySQL, Aurora PostgreSQL, RDS MySQL, RDS PostgreSQL) |\n| DB is not RDS Custom | RDS Custom does NOT support Blue\u002FGreen | Check `--db-instance-class` is not `custom-*` |\n| No pending maintenance actions | Pending maintenance can interfere | `aws rds describe-pending-maintenance-actions` |\n| Blue DB is AVAILABLE | Must be healthy before cloning | `aws rds describe-db-instances` — Status = available |\n| Major version upgrade path supported | Green upgrade must be a valid path | Check AWS docs for supported upgrade paths |\n| Application has retry logic | Switchover causes brief connection drops | Verify application connection retry configuration |\n| Switchover timeout decided | Controls how long switchover can run | Decide timeout (default 300 seconds) |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Blue\u002FGreen model (source to staging clone)\n\nBlue\u002FGreen Deployment creates a staging environment (green) that is a\nfull clone of the production environment (blue). Changes are made to\ngreen while blue continues to serve production traffic.\n\n| Component | Blue (production) | Green (staging) |\n|---|---|---|\n| Role | Active production DB | Full clone of blue |\n| Traffic | Serves all application traffic | No traffic (isolated) |\n| Changes | FROZEN (no changes during lifecycle) | ALL changes go here |\n| Replication | Source (writes replicated to green) | Destination (receives blue's changes) |\n| Cost | Normal | Additional (2x total during lifecycle) |\n\n**The green environment includes:**\n- Primary DB instance (clone of blue primary)\n- All read replicas (cloned from blue's read replicas)\n- Parameter groups (copied from blue)\n- Option groups (copied from blue)\n- Subnet groups and security groups (separate from blue)\n\n## Step 2 — Engine and version support\n\n| Engine | Blue\u002FGreen Support | Major Version Upgrade in Green |\n|---|---|---|\n| Aurora MySQL | Yes (all supported versions) | Yes (e.g., 5.7 → 8.0) |\n| Aurora PostgreSQL | Yes (all supported versions) | Yes (e.g., 12 → 14, 13 → 15) |\n| RDS MySQL | Yes (MySQL 5.7, 8.0) | Yes (5.7 → 8.0) |\n| RDS PostgreSQL | Yes (PostgreSQL 12 and later) | Yes (12 → 13, 13 → 14, etc.) |\n| RDS Custom | NO | N\u002FA — use standard modify-db-instance |\n| Other engines (SQL Server, Oracle, etc.) | NO | N\u002FA |\n\n**Critical:** Blue\u002FGreen is supported ONLY for Aurora MySQL, Aurora\nPostgreSQL, RDS MySQL, and RDS PostgreSQL. Other engines (SQL Server,\nOracle, MariaDB, Db2) do NOT support Blue\u002FGreen Deployments.\n\n## Step 3 — Create the blue\u002Fgreen deployment\n\n```bash\n# Create a Blue\u002FGreen Deployment\nBG_ID=$(aws rds create-blue-green-deployment \\\n  --blue-green-deployment-name \"bg-prod-upgrade-2026\" \\\n  --source arn:aws:rds:us-east-1:123456789012:db:prod-mysql-db \\\n  --target-engine-version \"8.0\" \\\n  --target-db-parameter-group-name \"prod-mysql80-params\" \\\n  --region us-east-1 \\\n  --query 'BlueGreenDeploymentIdentifier' --output text)\n\necho \"Blue\u002FGreen Deployment ID: $BG_ID\"\n```\n\n**Key parameters:**\n- `--source`: ARN of the blue DB instance or Aurora cluster\n- `--target-engine-version`: The new engine version for green (e.g.,\n  \"8.0\" for MySQL 8.0 upgrade)\n- `--target-db-parameter-group-name`: New parameter group for green\n  (must match the target engine version)\n- `--target-db-cluster-parameter-group-name`: For Aurora clusters\n\n**Creation time:** The green environment is provisioned as a full\nclone. Creation time depends on database size (minutes for small DBs,\nhours for multi-TB databases).\n\n**Verify creation:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].{Status:Status,Green:Target}' \\\n  --region us-east-1\n# Expected: Status = \"PROVISIONING\" → \"AVAILABLE\" → \"SWITCHOVER_IN_PROGRESS\" → \"SWITCHOVER_COMPLETED\"\n```\n\n## Step 4 — Database changes in green\n\nAfter green is AVAILABLE, make changes ONLY in green. Blue stays\nfrozen.\n\n### Major version upgrade in green\n\nThe `--target-engine-version` at creation time specifies the major\nversion for green. The upgrade happens during green provisioning.\nAfter green is AVAILABLE, it runs the target version.\n\n```bash\n# Verify green is running the target version\naws rds describe-db-instances \\\n  --db-instance-identifier \"green-prod-mysql-db\" \\\n  --query 'DBInstances[0].{Engine:Engine,EngineVersion:EngineVersion,Status:DBInstanceStatus}' \\\n  --region us-east-1\n# Expected: EngineVersion = \"8.0\" (the target)\n```\n\n### Parameter group changes in green\n\nParameter-group change CLI for green moved verbatim to\n[references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md).\n\n### Schema changes (DDL) in green\n\nGreen-only DDL execution example and the never-run-DDL-on-blue warning moved verbatim to\n[references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md).\n\n## Step 5 — Green environment validation\n\nBefore switchover, validate green thoroughly. This is the most\nimportant step — it is your last chance to catch issues before green\nbecomes production.\n\n| Validation | What to check | How |\n|---|---|---|\n| Engine version | Green runs target version | `describe-db-instances` on green |\n| Data freshness | Replication lag is near-zero | Check CloudWatch `ReplicaLag` or Blue\u002FGreen status |\n| Schema correctness | DDL changes applied successfully | Query green for expected schema |\n| Query performance | No regression vs blue | Run representative queries on green |\n| Parameter changes | Parameters applied correctly | `describe-db-parameters` on green |\n| Application tests | App works against green | Point a staging app at green endpoint |\n| Connections | Green accepts connections | Test connect to green endpoint |\n\n**Check replication lag:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].Status' \\\n  --region us-east-1\n# Status should be \"AVAILABLE\" (not \"PROVISIONING\" or \"UPGRADING\")\n```\n\n**Run validation queries on green:**\n\n```bash\n# Connect to GREEN endpoint (verify schema changes applied)\nmysql -h green-prod-mysql-db.cluster-xxx.us-east-1.rds.amazonaws.com \\\n  -u admin -p \\\n  -e \"SELECT COUNT(*) FROM information_schema.columns WHERE table_name='orders' AND column_name='status_code';\"\n# Expected: 1 (column exists)\n```\n\n## Step 6 — Switchover (1-minute downtime)\n\nSwitchover reroutes traffic from blue to green by updating the DNS\nendpoints. The blue endpoint and green endpoint are swapped.\n\n```bash\n# Initiate switchover\naws rds switchover-blue-green-deployment \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --switchover-timeout 300 \\\n  --region us-east-1\n```\n\n**What happens during switchover:**\n1. Replication from blue to green is stopped.\n2. Any remaining replicated changes are applied to green.\n3. Endpoints are swapped: the blue CNAME now points to green (new\n   production), and the green CNAME now points to blue (former\n   production).\n4. Applications reconnecting use the new endpoint automatically.\n\n**Switchover takes approximately 1 minute.** Applications with\nconnection retry logic experience a sub-second blip. Applications\nwithout retry logic may see 1-60 seconds of errors.\n\n**Verify switchover:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].{Status:Status,SwitchoverTime:SwitchoverConfigured}' \\\n  --region us-east-1\n# Expected: Status = \"SWITCHOVER_COMPLETED\"\n```\n\n## Step 7 — Switchover timeout configuration\n\nSwitchover timeout CLI and size-based timeout guidance moved verbatim to\n[references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md).\n\n## Step 8 — Application connection string update\n\nThe endpoint\u002FCNAME swap walkthrough and app-attention list moved verbatim to\n[references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md).\n\n## Step 9 — Delete green after successful switch\n\nAfter switchover, the former blue is now the new green. It continues\nrunning (and billing). Delete it to stop the 2x cost.\n\n```bash\n# Delete the Blue\u002FGreen Deployment (cleans up the former blue \u002F new green)\naws rds delete-blue-green-deployment \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --delete-target \\\n  --region us-east-1\n```\n\n**Critical:** `--delete-target` deletes the former blue database\n(now the new green after switchover). This is the standard cleanup.\nIf you want to keep the former blue as a fallback, omit\n`--delete-target` and delete manually later.\n\n**Verify deletion:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --region us-east-1 2>&1\n# Expected: BlueGreenDeployment NotFound (deleted successfully)\n```\n\n## Step 10 — Blue\u002FGreen limitations\n\nThe Blue\u002FGreen limitations table and engine-support caveat moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Step 11 — Monitoring during green validation\n\nGreen-validation CloudWatch metrics table and monitoring CLI moved verbatim to\n[references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 12 — Recent features\n\nRecent AWS feature notes (2023-2026) moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER make DDL changes in blue during the Blue\u002FGreen lifecycle.**\n   Blue is frozen. DDL in blue breaks logical replication to green.\n   Make ALL changes in green only.\n\n2. **NEVER skip green validation.** Always validate green (engine\n   version, data freshness, schema, query performance, application\n   tests) before switchover. Validation is the last chance to catch\n   issues before green becomes production.\n\n3. **NEVER assume switchover is truly zero-downtime.** Switchover\n   takes ~1 minute. Applications MUST have connection retry logic.\n   Long-lived connections will break and need to reconnect.\n\n4. **NEVER leave green running after switchover without deleting.**\n   After switchover, the former blue becomes the new green and\n   continues billing. Delete it (with `--delete-target`) to stop the\n   2x cost.\n\n5. **NEVER use Blue\u002FGreen for unsupported engines.** Only Aurora\n   MySQL\u002FPostgreSQL and RDS MySQL\u002FPostgreSQL support Blue\u002FGreen. SQL\n   Server, Oracle, MariaDB, and Db2 do NOT. RDS Custom does NOT.\n\n6. **NEVER initiate switchover with high replication lag.** High\n   replication lag means green is not in sync with blue. Wait for lag\n   to drop to near-zero before switching. High lag during switchover\n   increases downtime.\n\n7. **NEVER attempt to skip more than one major version in a single\n   Blue\u002FGreen.** Unsupported upgrade paths fail at green creation.\n   Upgrade incrementally (e.g., 12→13, then 13→14 in a second Blue\u002F\n   Green lifecycle).\n\n8. **NEVER forget the switchover timeout.** The default (300 seconds)\n   may be too short for large databases. Set an appropriate timeout\n   based on database size to avoid rollback during switchover.\n\n9. **NEVER point applications at the green endpoint directly.**\n   Applications should use the blue endpoint CNAME. After switchover,\n   the CNAME follows to green automatically. Pointing at green\n   directly defeats the purpose of the DNS switch.\n\n10. **NEVER create a Blue\u002FGreen Deployment without verifying pending\n    maintenance actions.** Pending maintenance on blue can interfere\n    with green provisioning and switchover. Resolve pending\n    maintenance before creating the Blue\u002FGreen Deployment.\n\n## Output format\n\n```text\nBLUE_GREEN: \u003Cblue-db-id> → \u003Cgreen-db-id> (\u003Cbg-deployment-id>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Source DB (blue): \u003Cdb-id> (\u003Cengine> \u003Cengine-version>)\n  [✓|✗] Engine support: Supported (\u003Cengine>) | Unsupported (\u003Cengine>)\n  [✓|✗] Blue status: AVAILABLE | \u003Cother-status>\n  [✓|✗] Blue\u002FGreen deployment: \u003Cbg-id> — AVAILABLE\n  [✓|✗] Green environment: \u003Cgreen-db-id> (\u003Ctarget-engine-version>)\n  [✓|✗] Major version upgrade: \u003Cfrom-version> → \u003Cto-version> (in green)\n  [✓|✗] Parameter group change: \u003Cpg-name> (applied to green)\n  [✓|✗] Schema changes: \u003Clist> (applied to green)\n  [✓|✗] Green validation: PASSED | PENDING\n  [✓|✗] Replication (blue → green): ACTIVE, lag \u003C 1s | lag \u003Cvalue>\n  [✓|✗] Switchover timeout: \u003Cseconds> seconds\n  [✓|✗] Application retry logic: Configured | NOT configured (risk)\n  [✓|✗] Endpoint strategy: CNAME auto-follow (no app change needed)\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws rds describe-blue-green-deployments --blue-green-deployment-identifier \u003Cbg-id> --region \u003Cregion>\n  aws rds describe-db-instances --db-instance-identifier \u003Cgreen-db-id> --region \u003Cregion>\n```\n\n### Worked example — Aurora MySQL major version upgrade via Blue\u002FGreen\n\n```text\nBLUE_GREEN: prod-mysql-db → green-prod-mysql-db (bg-prod-upgrade-2026)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Source DB (blue): prod-mysql-db (aurora-mysql 5.7.mysql_aurora.2.11.0)\n  [✓] Engine support: Supported (aurora-mysql)\n  [✓] Blue status: AVAILABLE\n  [✓] Blue\u002FGreen deployment: bg-prod-upgrade-2026 — AVAILABLE\n  [✓] Green environment: green-prod-mysql-db (8.0.mysql_aurora.3.04.0)\n  [✓] Major version upgrade: 5.7 → 8.0 (in green)\n  [✓] Parameter group change: prod-mysql80-params (applied to green)\n  [✓] Schema changes: ALTER TABLE orders ADD status_code INT (applied to green)\n  [✓] Green validation: PASSED (engine version confirmed, schema verified, query performance within baseline)\n  [✓] Replication (blue → green): ACTIVE, lag \u003C 1s\n  [✓] Switchover timeout: 300 seconds\n  [✓] Application retry logic: Configured (connection pool with retry)\n  [✓] Endpoint strategy: CNAME auto-follow (no app change needed)\n  [✓] Tags: Environment=production, Upgrade=mysql57-to-80\nVERIFICATION_COMMANDS:\n  aws rds describe-blue-green-deployments --blue-green-deployment-identifier bg-prod-upgrade-2026 --region us-east-1\n  aws rds describe-db-instances --db-instance-identifier green-prod-mysql-db --region us-east-1\n```\n\n## Error handling\n\nFailure modes and their fixes (green creation, replication lag, switchover\ntimeout, post-switchover app errors, 2x billing) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — configuration dependency graph, 2x cost window, green-vs-blue change matrix, switchover downtime characteristics, limitations table, recent AWS features (moved from this file)\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Step 11 green-validation CloudWatch metrics and monitoring CLI (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — failure modes: green creation fails, replication lag, switchover timeout, application errors after switchover, green left running (moved from this file)\n- [references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md) — switchover + DNS detail; extended with Step 7 timeout configuration and Step 8 connection-string update\n- [references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md) — green validation and database-changes detail; extended with the Step 4 parameter-group and schema-change (DDL) procedures\n\n## Domain\n\nAWS CloudOps \u002F Amazon RDS Blue\u002FGreen Deployments & Zero-Downtime\nDatabase Upgrades.\n\n## AWS documentation\n\n- **RDS Blue\u002FGreen Deployments** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments.html\n- **Creating a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-creating.html\n- **Switching over a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-switching-over.html\n- **Deleting a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-deleting.html\n- **Blue\u002FGreen limitations** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-limitations.html\n- **Aurora Blue\u002FGreen** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FAuroraUserGuide\u002Fblue-green-deployments.html\n- **RDS major version upgrades** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002FUSER_UpgradeDBInstance.Upgrading.html\n- **CloudWatch RDS metrics** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002FOverview.Monitoring.html\n","# RDS Blue\u002FGreen Deployer\n\nAn AWS CloudOps agent skill that deploys Amazon RDS Blue\u002FGreen\nDeployments with correct defaults. The skill walks the operator\nthrough blue\u002Fgreen creation (source to staging clone), database\nchanges in the green environment (major version upgrade, parameter\nchanges, schema changes), green validation, switchover (1-minute\ndowntime via DNS update), application connection string implications,\nand green cleanup, captures upgrade decisions, explains why each\ndefault matters, and emits a READY_TO_DEPLOY checklist with copy-\npasteable verification commands.\n\n## Activation keywords\n\ncreate blue green deployment, RDS blue green switchover, zero downtime\ndatabase upgrade, Aurora blue green, RDS major version upgrade green,\ngreen environment validation, switch over blue green.\n\n## STRICT output contract\n\nWhen this skill is invoked with an RDS Blue\u002FGreen Deployment request\n(create a blue\u002Fgreen deployment, perform zero-downtime upgrade,\nswitchover, validate green, delete green, or a partial configuration),\nthe agent MUST respond with the READY_TO_DEPLOY checklist defined in\nthe \"Output format\" section using the literal all-caps labels\n`BLUE_GREEN:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface the checklist with prose, headings, or disclaimers —\nemit the block as the first lines of the response. This contract is\nwhat assertion-based evals and downstream deployment pipelines rely\non; deviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before deploying |\n| Step 1 — Blue\u002FGreen model (source to staging clone) | Core deployment model |\n| Step 2 — Engine and version support | Aurora MySQL\u002FPostgreSQL, RDS MySQL\u002FPostgreSQL |\n| Step 3 — Create the blue\u002Fgreen deployment | Creation step |\n| Step 4 — Database changes in green | Major version, parameter, schema changes |\n| Step 5 — Green environment validation | Pre-switchover validation |\n| Step 6 — Switchover (1-minute downtime) | DNS-based traffic rerouting |\n| Step 7 — Switchover timeout configuration | Timeout control |\n| Step 8 — Application connection string update | DNS\u002FCNAME implications |\n| Step 9 — Delete green after successful switch | Cleanup |\n| Step 10 — Blue\u002FGreen limitations | Engine version, storage, topology constraints |\n| Step 11 — Monitoring during green validation | CloudWatch metrics |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fswitchover-and-dns.md | Switchover + DNS detail |\n| references\u002Fgreen-validation-and-changes.md | Validation + changes detail |\n\n## Mindset\n\n**One-line takeaway:** Blue\u002FGreen creates a full staging clone\n(green) of your production database (blue), replicates changes from\nblue to green, lets you make destructive changes (major version\nupgrade, parameter changes) in green without touching production,\nvalidates green, then switches traffic in about 1 minute via a DNS\nupdate. The green environment is a full clone — it costs 2x during\nvalidation.\n\nThree misconceptions dominate RDS Blue\u002FGreen misdesign at deployment\ntime:\n\n- **\"Blue\u002FGreen is zero-downtime.\"** It is near-zero-downtime. The\n  switchover takes approximately 1 minute, during which existing\n  connections are briefly dropped and re-established. Applications\n  MUST use connection retry logic. The DNS switch is transparent to\n  applications that resolve the endpoint at connection time, but\n  long-lived connections will break and need reconnect.\n\n- **\"I can make changes in blue while green is being created.\"** You\n  should NOT. The green environment is a point-in-time clone of blue.\n  Changes made to blue after green creation are replicated via logical\n  replication, but DDL changes (schema changes) in blue during the\n  Blue\u002FGreen lifecycle can break replication. Make changes ONLY in\n  green. Blue stays untouched until switchover.\n\n- **\"Green is free — it is just a staging copy.\"** Green is a FULL\n  clone — complete instance\u002Fstorage\u002FIO. You pay 2x database costs\n  during the entire Blue\u002FGreen lifecycle. Delete green promptly after\n  successful switchover to stop the duplicate billing. The cost is the\n  trade-off for zero-downtime upgrades.\n\n## Configuration dependency graph (novel heuristic)\n\nThe configuration dependency graph and cross-dependency gotchas moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: the 2x cost window\n\nThe 2x cost window timeline and key implication moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: what changes go in green vs blue\n\nThe green-vs-blue change matrix moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: switchover downtime characteristics\n\nSwitchover downtime phase breakdown and retry guidance moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Prerequisites (verify before deploying)\n\nBefore emitting deployment commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Source DB (blue) exists | Blue\u002FGreen clones an existing DB | `aws rds describe-db-instances --db-instance-identifier \u003Cid>` |\n| Engine supports Blue\u002FGreen | Not all engines\u002Fversions support it | Check supported engines (Aurora MySQL, Aurora PostgreSQL, RDS MySQL, RDS PostgreSQL) |\n| DB is not RDS Custom | RDS Custom does NOT support Blue\u002FGreen | Check `--db-instance-class` is not `custom-*` |\n| No pending maintenance actions | Pending maintenance can interfere | `aws rds describe-pending-maintenance-actions` |\n| Blue DB is AVAILABLE | Must be healthy before cloning | `aws rds describe-db-instances` — Status = available |\n| Major version upgrade path supported | Green upgrade must be a valid path | Check AWS docs for supported upgrade paths |\n| Application has retry logic | Switchover causes brief connection drops | Verify application connection retry configuration |\n| Switchover timeout decided | Controls how long switchover can run | Decide timeout (default 300 seconds) |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Blue\u002FGreen model (source to staging clone)\n\nBlue\u002FGreen Deployment creates a staging environment (green) that is a\nfull clone of the production environment (blue). Changes are made to\ngreen while blue continues to serve production traffic.\n\n| Component | Blue (production) | Green (staging) |\n|---|---|---|\n| Role | Active production DB | Full clone of blue |\n| Traffic | Serves all application traffic | No traffic (isolated) |\n| Changes | FROZEN (no changes during lifecycle) | ALL changes go here |\n| Replication | Source (writes replicated to green) | Destination (receives blue's changes) |\n| Cost | Normal | Additional (2x total during lifecycle) |\n\n**The green environment includes:**\n- Primary DB instance (clone of blue primary)\n- All read replicas (cloned from blue's read replicas)\n- Parameter groups (copied from blue)\n- Option groups (copied from blue)\n- Subnet groups and security groups (separate from blue)\n\n## Step 2 — Engine and version support\n\n| Engine | Blue\u002FGreen Support | Major Version Upgrade in Green |\n|---|---|---|\n| Aurora MySQL | Yes (all supported versions) | Yes (e.g., 5.7 → 8.0) |\n| Aurora PostgreSQL | Yes (all supported versions) | Yes (e.g., 12 → 14, 13 → 15) |\n| RDS MySQL | Yes (MySQL 5.7, 8.0) | Yes (5.7 → 8.0) |\n| RDS PostgreSQL | Yes (PostgreSQL 12 and later) | Yes (12 → 13, 13 → 14, etc.) |\n| RDS Custom | NO | N\u002FA — use standard modify-db-instance |\n| Other engines (SQL Server, Oracle, etc.) | NO | N\u002FA |\n\n**Critical:** Blue\u002FGreen is supported ONLY for Aurora MySQL, Aurora\nPostgreSQL, RDS MySQL, and RDS PostgreSQL. Other engines (SQL Server,\nOracle, MariaDB, Db2) do NOT support Blue\u002FGreen Deployments.\n\n## Step 3 — Create the blue\u002Fgreen deployment\n\n```bash\n# Create a Blue\u002FGreen Deployment\nBG_ID=$(aws rds create-blue-green-deployment \\\n  --blue-green-deployment-name \"bg-prod-upgrade-2026\" \\\n  --source arn:aws:rds:us-east-1:123456789012:db:prod-mysql-db \\\n  --target-engine-version \"8.0\" \\\n  --target-db-parameter-group-name \"prod-mysql80-params\" \\\n  --region us-east-1 \\\n  --query 'BlueGreenDeploymentIdentifier' --output text)\n\necho \"Blue\u002FGreen Deployment ID: $BG_ID\"\n```\n\n**Key parameters:**\n- `--source`: ARN of the blue DB instance or Aurora cluster\n- `--target-engine-version`: The new engine version for green (e.g.,\n  \"8.0\" for MySQL 8.0 upgrade)\n- `--target-db-parameter-group-name`: New parameter group for green\n  (must match the target engine version)\n- `--target-db-cluster-parameter-group-name`: For Aurora clusters\n\n**Creation time:** The green environment is provisioned as a full\nclone. Creation time depends on database size (minutes for small DBs,\nhours for multi-TB databases).\n\n**Verify creation:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].{Status:Status,Green:Target}' \\\n  --region us-east-1\n# Expected: Status = \"PROVISIONING\" → \"AVAILABLE\" → \"SWITCHOVER_IN_PROGRESS\" → \"SWITCHOVER_COMPLETED\"\n```\n\n## Step 4 — Database changes in green\n\nAfter green is AVAILABLE, make changes ONLY in green. Blue stays\nfrozen.\n\n### Major version upgrade in green\n\nThe `--target-engine-version` at creation time specifies the major\nversion for green. The upgrade happens during green provisioning.\nAfter green is AVAILABLE, it runs the target version.\n\n```bash\n# Verify green is running the target version\naws rds describe-db-instances \\\n  --db-instance-identifier \"green-prod-mysql-db\" \\\n  --query 'DBInstances[0].{Engine:Engine,EngineVersion:EngineVersion,Status:DBInstanceStatus}' \\\n  --region us-east-1\n# Expected: EngineVersion = \"8.0\" (the target)\n```\n\n### Parameter group changes in green\n\nParameter-group change CLI for green moved verbatim to\n[references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md).\n\n### Schema changes (DDL) in green\n\nGreen-only DDL execution example and the never-run-DDL-on-blue warning moved verbatim to\n[references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md).\n\n## Step 5 — Green environment validation\n\nBefore switchover, validate green thoroughly. This is the most\nimportant step — it is your last chance to catch issues before green\nbecomes production.\n\n| Validation | What to check | How |\n|---|---|---|\n| Engine version | Green runs target version | `describe-db-instances` on green |\n| Data freshness | Replication lag is near-zero | Check CloudWatch `ReplicaLag` or Blue\u002FGreen status |\n| Schema correctness | DDL changes applied successfully | Query green for expected schema |\n| Query performance | No regression vs blue | Run representative queries on green |\n| Parameter changes | Parameters applied correctly | `describe-db-parameters` on green |\n| Application tests | App works against green | Point a staging app at green endpoint |\n| Connections | Green accepts connections | Test connect to green endpoint |\n\n**Check replication lag:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].Status' \\\n  --region us-east-1\n# Status should be \"AVAILABLE\" (not \"PROVISIONING\" or \"UPGRADING\")\n```\n\n**Run validation queries on green:**\n\n```bash\n# Connect to GREEN endpoint (verify schema changes applied)\nmysql -h green-prod-mysql-db.cluster-xxx.us-east-1.rds.amazonaws.com \\\n  -u admin -p \\\n  -e \"SELECT COUNT(*) FROM information_schema.columns WHERE table_name='orders' AND column_name='status_code';\"\n# Expected: 1 (column exists)\n```\n\n## Step 6 — Switchover (1-minute downtime)\n\nSwitchover reroutes traffic from blue to green by updating the DNS\nendpoints. The blue endpoint and green endpoint are swapped.\n\n```bash\n# Initiate switchover\naws rds switchover-blue-green-deployment \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --switchover-timeout 300 \\\n  --region us-east-1\n```\n\n**What happens during switchover:**\n1. Replication from blue to green is stopped.\n2. Any remaining replicated changes are applied to green.\n3. Endpoints are swapped: the blue CNAME now points to green (new\n   production), and the green CNAME now points to blue (former\n   production).\n4. Applications reconnecting use the new endpoint automatically.\n\n**Switchover takes approximately 1 minute.** Applications with\nconnection retry logic experience a sub-second blip. Applications\nwithout retry logic may see 1-60 seconds of errors.\n\n**Verify switchover:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --query 'BlueGreenDeployments[0].{Status:Status,SwitchoverTime:SwitchoverConfigured}' \\\n  --region us-east-1\n# Expected: Status = \"SWITCHOVER_COMPLETED\"\n```\n\n## Step 7 — Switchover timeout configuration\n\nSwitchover timeout CLI and size-based timeout guidance moved verbatim to\n[references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md).\n\n## Step 8 — Application connection string update\n\nThe endpoint\u002FCNAME swap walkthrough and app-attention list moved verbatim to\n[references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md).\n\n## Step 9 — Delete green after successful switch\n\nAfter switchover, the former blue is now the new green. It continues\nrunning (and billing). Delete it to stop the 2x cost.\n\n```bash\n# Delete the Blue\u002FGreen Deployment (cleans up the former blue \u002F new green)\naws rds delete-blue-green-deployment \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --delete-target \\\n  --region us-east-1\n```\n\n**Critical:** `--delete-target` deletes the former blue database\n(now the new green after switchover). This is the standard cleanup.\nIf you want to keep the former blue as a fallback, omit\n`--delete-target` and delete manually later.\n\n**Verify deletion:**\n\n```bash\naws rds describe-blue-green-deployments \\\n  --blue-green-deployment-identifier \"$BG_ID\" \\\n  --region us-east-1 2>&1\n# Expected: BlueGreenDeployment NotFound (deleted successfully)\n```\n\n## Step 10 — Blue\u002FGreen limitations\n\nThe Blue\u002FGreen limitations table and engine-support caveat moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Step 11 — Monitoring during green validation\n\nGreen-validation CloudWatch metrics table and monitoring CLI moved verbatim to\n[references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 12 — Recent features\n\nRecent AWS feature notes (2023-2026) moved verbatim to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER make DDL changes in blue during the Blue\u002FGreen lifecycle.**\n   Blue is frozen. DDL in blue breaks logical replication to green.\n   Make ALL changes in green only.\n\n2. **NEVER skip green validation.** Always validate green (engine\n   version, data freshness, schema, query performance, application\n   tests) before switchover. Validation is the last chance to catch\n   issues before green becomes production.\n\n3. **NEVER assume switchover is truly zero-downtime.** Switchover\n   takes ~1 minute. Applications MUST have connection retry logic.\n   Long-lived connections will break and need to reconnect.\n\n4. **NEVER leave green running after switchover without deleting.**\n   After switchover, the former blue becomes the new green and\n   continues billing. Delete it (with `--delete-target`) to stop the\n   2x cost.\n\n5. **NEVER use Blue\u002FGreen for unsupported engines.** Only Aurora\n   MySQL\u002FPostgreSQL and RDS MySQL\u002FPostgreSQL support Blue\u002FGreen. SQL\n   Server, Oracle, MariaDB, and Db2 do NOT. RDS Custom does NOT.\n\n6. **NEVER initiate switchover with high replication lag.** High\n   replication lag means green is not in sync with blue. Wait for lag\n   to drop to near-zero before switching. High lag during switchover\n   increases downtime.\n\n7. **NEVER attempt to skip more than one major version in a single\n   Blue\u002FGreen.** Unsupported upgrade paths fail at green creation.\n   Upgrade incrementally (e.g., 12→13, then 13→14 in a second Blue\u002F\n   Green lifecycle).\n\n8. **NEVER forget the switchover timeout.** The default (300 seconds)\n   may be too short for large databases. Set an appropriate timeout\n   based on database size to avoid rollback during switchover.\n\n9. **NEVER point applications at the green endpoint directly.**\n   Applications should use the blue endpoint CNAME. After switchover,\n   the CNAME follows to green automatically. Pointing at green\n   directly defeats the purpose of the DNS switch.\n\n10. **NEVER create a Blue\u002FGreen Deployment without verifying pending\n    maintenance actions.** Pending maintenance on blue can interfere\n    with green provisioning and switchover. Resolve pending\n    maintenance before creating the Blue\u002FGreen Deployment.\n\n## Output format\n\n```text\nBLUE_GREEN: \u003Cblue-db-id> → \u003Cgreen-db-id> (\u003Cbg-deployment-id>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Source DB (blue): \u003Cdb-id> (\u003Cengine> \u003Cengine-version>)\n  [✓|✗] Engine support: Supported (\u003Cengine>) | Unsupported (\u003Cengine>)\n  [✓|✗] Blue status: AVAILABLE | \u003Cother-status>\n  [✓|✗] Blue\u002FGreen deployment: \u003Cbg-id> — AVAILABLE\n  [✓|✗] Green environment: \u003Cgreen-db-id> (\u003Ctarget-engine-version>)\n  [✓|✗] Major version upgrade: \u003Cfrom-version> → \u003Cto-version> (in green)\n  [✓|✗] Parameter group change: \u003Cpg-name> (applied to green)\n  [✓|✗] Schema changes: \u003Clist> (applied to green)\n  [✓|✗] Green validation: PASSED | PENDING\n  [✓|✗] Replication (blue → green): ACTIVE, lag \u003C 1s | lag \u003Cvalue>\n  [✓|✗] Switchover timeout: \u003Cseconds> seconds\n  [✓|✗] Application retry logic: Configured | NOT configured (risk)\n  [✓|✗] Endpoint strategy: CNAME auto-follow (no app change needed)\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws rds describe-blue-green-deployments --blue-green-deployment-identifier \u003Cbg-id> --region \u003Cregion>\n  aws rds describe-db-instances --db-instance-identifier \u003Cgreen-db-id> --region \u003Cregion>\n```\n\n### Worked example — Aurora MySQL major version upgrade via Blue\u002FGreen\n\n```text\nBLUE_GREEN: prod-mysql-db → green-prod-mysql-db (bg-prod-upgrade-2026)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Source DB (blue): prod-mysql-db (aurora-mysql 5.7.mysql_aurora.2.11.0)\n  [✓] Engine support: Supported (aurora-mysql)\n  [✓] Blue status: AVAILABLE\n  [✓] Blue\u002FGreen deployment: bg-prod-upgrade-2026 — AVAILABLE\n  [✓] Green environment: green-prod-mysql-db (8.0.mysql_aurora.3.04.0)\n  [✓] Major version upgrade: 5.7 → 8.0 (in green)\n  [✓] Parameter group change: prod-mysql80-params (applied to green)\n  [✓] Schema changes: ALTER TABLE orders ADD status_code INT (applied to green)\n  [✓] Green validation: PASSED (engine version confirmed, schema verified, query performance within baseline)\n  [✓] Replication (blue → green): ACTIVE, lag \u003C 1s\n  [✓] Switchover timeout: 300 seconds\n  [✓] Application retry logic: Configured (connection pool with retry)\n  [✓] Endpoint strategy: CNAME auto-follow (no app change needed)\n  [✓] Tags: Environment=production, Upgrade=mysql57-to-80\nVERIFICATION_COMMANDS:\n  aws rds describe-blue-green-deployments --blue-green-deployment-identifier bg-prod-upgrade-2026 --region us-east-1\n  aws rds describe-db-instances --db-instance-identifier green-prod-mysql-db --region us-east-1\n```\n\n## Error handling\n\nFailure modes and their fixes (green creation, replication lag, switchover\ntimeout, post-switchover app errors, 2x billing) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — configuration dependency graph, 2x cost window, green-vs-blue change matrix, switchover downtime characteristics, limitations table, recent AWS features (moved from this file)\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Step 11 green-validation CloudWatch metrics and monitoring CLI (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — failure modes: green creation fails, replication lag, switchover timeout, application errors after switchover, green left running (moved from this file)\n- [references\u002Fswitchover-and-dns.md](references\u002Fswitchover-and-dns.md) — switchover + DNS detail; extended with Step 7 timeout configuration and Step 8 connection-string update\n- [references\u002Fgreen-validation-and-changes.md](references\u002Fgreen-validation-and-changes.md) — green validation and database-changes detail; extended with the Step 4 parameter-group and schema-change (DDL) procedures\n\n## Domain\n\nAWS CloudOps \u002F Amazon RDS Blue\u002FGreen Deployments & Zero-Downtime\nDatabase Upgrades.\n\n## AWS documentation\n\n- **RDS Blue\u002FGreen Deployments** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments.html\n- **Creating a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-creating.html\n- **Switching over a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-switching-over.html\n- **Deleting a Blue\u002FGreen Deployment** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-deleting.html\n- **Blue\u002FGreen limitations** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002Fblue-green-deployments-limitations.html\n- **Aurora Blue\u002FGreen** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FAuroraUserGuide\u002Fblue-green-deployments.html\n- **RDS major version upgrades** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002FUSER_UpgradeDBInstance.Upgrading.html\n- **CloudWatch RDS metrics** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide\u002FOverview.Monitoring.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, rds, blue-green, cloudops, deploy, databases, aurora, switchover, zero-downtime, upgrades","1","Jacky Chan — AWS Community Builder","aws-cloudops","Databases","0.1.0","aws, rds, blue green, blue\u002Fgreen deployment, cloudops, deploy, zero downtime, switchover, aurora, major version upgrade, parameter group, schema change, green environment, staging clone, dns switch","deploy","high","false","capability","Invoke when the user wants to create an RDS Blue\u002FGreen Deployment, perform a zero-downtime database upgrade (major version, parameter group, or schema changes), switch over a blue\u002Fgreen deployment, validate the green environment before switchover, delete a green environment after successful switchover, or understand Blue\u002FGreen limitations. Do NOT invoke for standard RDS modifications without Blue\u002FGreen (use modify-db-instance directly), Aurora Global Database failover, or Multi-AZ failover.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with RDS access. Works with Terraform aws_rds_blue_green_deployment resource and CloudFormation AWS::RDS::BlueGreenDeployment templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Frds-bluegreen-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill rds-bluegreen-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill rds-bluegreen-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill rds-bluegreen-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5824,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Faurora-mysql-major-version-upgrade.md",821,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fbaselines\u002Faurora-mysql-major-version-upgrade.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Frds-postgres-parameter-change.md",723,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fbaselines\u002Frds-postgres-parameter-change.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fschema-change-in-green.md",859,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fbaselines\u002Fschema-change-in-green.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fswitchover-with-validation.md",641,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fbaselines\u002Fswitchover-with-validation.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Funsupported-engine-sqlserver.md",713,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fbaselines\u002Funsupported-engine-sqlserver.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1834,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",11291,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Faurora-mysql-major-version-upgrade.md",679,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fprompts\u002Faurora-mysql-major-version-upgrade.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Frds-postgres-parameter-change.md",599,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fprompts\u002Frds-postgres-parameter-change.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fschema-change-in-green.md",588,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fprompts\u002Fschema-change-in-green.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fswitchover-with-validation.md",678,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fprompts\u002Fswitchover-with-validation.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Funsupported-engine-sqlserver.md",469,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fevals\u002Fprompts\u002Funsupported-engine-sqlserver.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7199,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",7380,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fdiagnostic-commands.md",1435,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1385,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fgreen-validation-and-changes.md",12802,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Freferences\u002Fgreen-validation-and-changes.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fswitchover-and-dns.md",11072,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Freferences\u002Fswitchover-and-dns.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4609,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frds-bluegreen-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]