[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABCRGR2YVCQPMADS1E7W8N":3,"skill-same:01M7ABCRGR2YVCQPMADS1E7W8N":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},"01M7ABCRGR2YVCQPMADS1E7W8N","route53-application-recovery-controller-deployer",null,"Provisions Route 53 Application Recovery Controller (ARC) with production defaults: recovery cluster (five Route 53 regional clusters across AWS regions for quorum), routing controls (boolean on\u002Foff toggles for traffic to a cell), control panels (groupings of routing controls), safety rules (prevent unsafe failover — disallow all routing controls OFF simultaneously), resource sets (by resource type: NLB, ASG, DynamoDB table, Aurora cluster, EC2, etc.), readiness checks (validate each cell has required resources before failover), cells (groupings of resources representing an application instance for failover), readiness scopes, cross-region readiness assessment, and CloudWatch routing control state monitoring. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating ARC readiness checks, configuring routing. Triggers: route 53 arc, application recovery controller, routing control, safety rule, readiness check, recovery cluster, control panel, cell failover, resource set, readiness...","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\u002Froute53-application-recovery-controller-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: route53-application-recovery-controller-deployer\ndescription: 'Provisions Route 53 Application Recovery Controller (ARC) with production defaults: recovery cluster (five Route 53 regional clusters across AWS regions for quorum), routing controls (boolean on\u002Foff toggles for traffic to a cell), control panels (groupings of routing controls), safety rules (prevent unsafe failover — disallow all routing controls OFF simultaneously), resource sets (by resource type: NLB, ASG, DynamoDB table, Aurora cluster, EC2, etc.), readiness checks (validate each cell has required resources before failover), cells (groupings of resources representing an application instance for failover), readiness scopes, cross-region readiness assessment, and CloudWatch routing control state monitoring. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating ARC readiness checks, configuring routing. Triggers: route 53 arc, application recovery controller, routing control, safety rule, readiness check, recovery cluster, control panel, cell failover, resource set, readiness...'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with route53-recovery-control-config, route53-recovery-readiness, and route53-recovery-cluster access. Works with Terraform aws_route53recoverycontrolconfig_* and aws_route53recoveryreadiness_* resources and CloudFormation AWS::Route53RecoveryControl::* 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: Networking\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, route-53-arc, application-recovery-controller, cloudops, deploy, networking, disaster-recovery, failover, routing-control, readiness-check, safety-rule\n  dependencies: aws-orchestrator\n  keywords: aws, route 53 arc, application recovery controller, routing control, safety rule, readiness check, recovery cluster, control panel, cell failover, resource set, cloudops, deploy, provisioning, disaster recovery, failover\n  when_to_use: Invoke when the user wants to set up Route 53 Application Recovery Controller for application failover orchestration — creating routing controls (traffic on\u002Foff switches), safety rules (prevent unsafe failover), readiness checks (validate cells before failover), resource sets, cells, control panels, or recovery clusters. Do NOT invoke for Route 53 health checks (use health-check skills), Route 53 DNS failover (use dns-failover skills), or Elastic Disaster Recovery (use drs skills).\n---\n\n# Route 53 Application Recovery Controller Deployer\n\nAn AWS CloudOps agent skill that provisions Route 53 Application\nRecovery Controller (ARC) with correct defaults. The skill walks the\noperator through recovery cluster topology, routing control design\n(boolean toggle for traffic), safety rule construction (prevent\nunsafe multi-cell failover), cell grouping, resource set creation by\nresource type, readiness check configuration, and CloudWatch\nmonitoring of routing control state, captures topology and failover\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\nroute 53 ARC, application recovery controller, routing control,\nsafety rule, readiness check, recovery cluster, control panel, cell\nfailover, resource set, readiness scope.\n\n## STRICT output contract\n\nWhen this skill is invoked with an ARC provisioning request (create a\nrecovery cluster, routing controls, safety rules, readiness checks,\ncells, resource sets, control panels, 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`ARC:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do\nNOT preface the checklist with prose, headings, or disclaimers — emit\nthe block as the first lines of the response. This contract is what\nassertion-based evals and downstream provisioning pipelines rely on;\ndeviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the checklist\n(marked `[x]`), and `READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Recovery cluster architecture | Core infrastructure |\n| Step 2 — Cells and resource sets | Resource grouping |\n| Step 3 — Control panels and routing controls | Traffic control |\n| Step 4 — Safety rules (prevent unsafe failover) | Safety guardrails |\n| Step 5 — Readiness checks | Pre-failover validation |\n| Step 6 — Cross-region readiness assessment | Multi-region readiness |\n| Step 7 — Routing control state and CloudWatch | Monitoring |\n| Step 8 — Failover execution patterns | Operational |\n| Step 9 — Integration with Route 53 health checks | DNS integration |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frouting-controls-and-safety.md | Control + safety detail |\n| references\u002Freadiness-and-resource-sets.md | Readiness + resource detail |\n\n## Mindset\n\n**One-line takeaway:** Route 53 ARC provides routing controls —\nsingle boolean toggles that turn traffic on or off to a cell — with\nsafety rules that prevent unsafe failover (e.g., blocking all routing\ncontrols from being OFF simultaneously), backed by a five-cluster\nrecovery control data plane that maintains quorum across AWS regions.\nReadiness checks validate that a target cell has all required\nresources BEFORE you fail over to it.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#common-misconceptions-from-mindset).\n> Three ARC misconceptions: just a health check, free toggling, optional readiness checks.\n\n## Configuration dependency graph (novel heuristic)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph-sequencing-notes).\n> Sequencing table plus the safety-rule-before-production trap and API-split gotchas.\n\n## Expert heuristic: routing control as a boolean toggle\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-routing-control-as-a-boolean-toggle).\n> ON\u002FOFF semantics, active-active and failover sequences, atomic ~10s toggle.\n\n## Expert heuristic: safety rule types\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-safety-rule-types).\n> AND (mutual exclusion) vs OR (minimum ON) rules with rejection semantics.\n\n## Expert heuristic: readiness check resource templates\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-readiness-check-resource-templates).\n> Per-resource-type readiness template attributes (NLB, ASG, DynamoDB, Aurora, NAT, S3, Lambda).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Application spans 2+ regions or cells | ARC failover requires at least two cells to fail over between | Confirm multi-region or multi-cell topology |\n| Resources exist in each cell | Readiness checks validate resource existence | `aws resourcegroupstaggingapi get-resources --region \u003Cregion>` |\n| Resource ARNs identified | Resource sets map by ARN | Collect ARNs for each resource per cell |\n| Resource types identified | Readiness templates match by type | Map each resource to its CloudFormation type |\n| Failover topology decided (active-active vs active-standby) | Determines routing control design | Confirm topology |\n| IAM permissions for ARC APIs | Both config and cluster APIs need permissions | Verify `route53-recovery-control-config:*` and `route53-recovery-cluster:*` |\n| Safety rule design decided | Prevents unsafe failover | Confirm at least one safety rule per control panel |\n| Cells defined (which resources belong to which cell) | Resource grouping for failover | Confirm cell-to-resource mapping |\n\nIf any prerequisite is missing, output\n`VERDICT: PREREQUISITES_MISSING` and cite the specific gap.\n\n## Step 1 — Recovery cluster architecture\n\nThe recovery cluster is the data plane for routing controls. AWS\nprovisions five regional clusters across different AWS regions when\nyou create a recovery control configuration. These clusters maintain\nquorum to ensure routing control state is consistent.\n\n| Property | Value |\n|---|---|\n| Cluster count | 5 (auto-provisioned, spread across AWS regions) |\n| Quorum | 3 of 5 clusters must agree for a toggle to succeed |\n| Cluster creation time | ~10-15 minutes |\n| Data plane API | `route53-recovery-cluster` (separate from config API) |\n| Config API | `route53-recovery-control-config` |\n| Availability | Designed for 99.999% availability |\n\n**Create the recovery cluster:**\n\n```bash\nCLUSTER_ARN=$(aws route53-recovery-control-config create-cluster \\\n  --cluster-name \"my-app-recovery-cluster\" \\\n  --query 'Cluster.ClusterArn' --output text)\n\necho \"Cluster ARN: $CLUSTER_ARN\"\n# Wait for cluster to become ACTIVE (~10-15 minutes)\naws route53-recovery-control-config describe-cluster \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --query 'Cluster.Status'\n```\n\n**The cluster ARN is required for all subsequent operations.** The\ncluster provides the routing control data plane endpoints. State\ntoggles go through `route53-recovery-cluster` (not the config API).\n\n## Step 2 — Cells and resource sets\n\nA **cell** is a logical grouping of resources that represents one\ncomplete instance of an application. A multi-region application\ntypically has one cell per region (Cell-A = us-east-1, Cell-B =\nus-west-2).\n\nA **resource set** groups resources by type across cells. For\nexample, a resource set of type `AWS::NetworkLoadBalancer::LoadBalancer`\ncontains the NLB ARNs from Cell-A and Cell-B.\n\n> Moved to [references\u002Freadiness-and-resource-sets.md](references\u002Freadiness-and-resource-sets.md#cell-and-resource-set-layout-from-step-2).\n> Concrete Cell-A\u002FCell-B to resource-set mapping example.\n\n**Create a resource set:**\n\n```bash\naws route53-recovery-readiness create-resource-set \\\n  --resource-set-name \"app-nlb-resource-set\" \\\n  --resource-set-type \"AWS::ElasticLoadBalancingV2::LoadBalancer\" \\\n  --resources \\\n    ResourceArn=arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer\u002Fnet\u002Fapp-nlb-a\u002F50dc6c495c0c9188,ReadinessScopes=Cell-A \\\n    ResourceArn=arn:aws:elasticloadbalancing:us-west-2:123456789012:loadbalancer\u002Fnet\u002Fapp-nlb-b\u002F60dc6c495c0c9189,ReadinessScopes=Cell-B\n```\n\n**Critical:** each resource must be tagged with its cell\n(ReadinessScopes). The readiness check compares across cells using\nthese scopes.\n\n## Step 3 — Control panels and routing controls\n\nA **control panel** is a logical grouping of routing controls. A\n**routing control** is a single boolean toggle (ON\u002FOFF) that\ncontrols traffic to a cell.\n\n**Create a control panel:**\n\n```bash\naws route53-recovery-control-config create-control-panel \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\"\n```\n\n**Create routing controls (one per cell):**\n\n```bash\n# Cell-A routing control\nRC_A_ARN=$(aws route53-recovery-control-config create-routing-control \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\" \\\n  --routing-control-name \"cell-a-traffic\" \\\n  --query 'RoutingControl.RoutingControlArn' --output text)\n\n# Cell-B routing control\nRC_B_ARN=$(aws route53-recovery-control-config create-routing-control \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\" \\\n  --routing-control-name \"cell-b-traffic\" \\\n  --query 'RoutingControl.RoutingControlArn' --output text)\n```\n\n**Initial state:** routing controls start in the OFF position. Both\ncontrols being OFF means no traffic. You must explicitly toggle the\nactive cell's control ON.\n\n**Toggle a routing control ON (via cluster API):**\n\n```bash\naws route53-recovery-cluster update-routing-control-state \\\n  --routing-control-arn \"$RC_A_ARN\" \\\n  --routing-control-state \"On\"\n```\n\n**Verify routing control state:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#verify-routing-control-state-step-3).\n> get-routing-control-state check expecting \"On\".\n\n## Step 4 — Safety rules (prevent unsafe failover)\n\nSafety rules are the guardrails that prevent unsafe routing control\ntoggles. Without them, an operator or automation can turn all\ncontrols OFF, causing a complete outage.\n\n**Create an OR safety rule (at least one cell must be ON):**\n\n```bash\naws route53-recovery-control-config create-safety-rule \\\n  --control-panel-arn \"$CONTROL_PANEL_ARN\" \\\n  --safety-rule-name \"prevent-total-outage\" \\\n  --rule-config '{\"Type\":\"OR\",\"Inverted\":false,\"Threshold\":1}' \\\n  --routing-controls-arns \"$RC_A_ARN\" \"$RC_B_ARN\"\n```\n\nThis rule means: at least 1 of the 2 listed routing controls must be\nON at all times. If you try to turn the last ON control OFF, the API\nrejects the request.\n\n**Create an AND safety rule (mutual exclusion):**\n\n```bash\naws route53-recovery-control-config create-safety-rule \\\n  --control-panel-arn \"$CONTROL_PANEL_ARN\" \\\n  --safety-rule-name \"prevent-split-brain\" \\\n  --rule-config '{\"Type\":\"AND\",\"Inverted\":false,\"Threshold\":1}' \\\n  --routing-controls-arns \"$RC_A_ARN\" \"$RC_B_ARN\"\n```\n\nThis rule (Type AND, Threshold 1) means: at most 1 of the 2 listed\nrouting controls can be ON. If you try to turn the second control ON\nwhile the first is already ON, the API rejects the request.\n\n**Safety rule semantics:**\n\n| Rule Type | Threshold | Meaning | Use case |\n|---|---|---|---|\n| OR | 1 | At least 1 control must be ON | Prevent total outage |\n| AND | 1 | At most 1 control can be ON | Prevent split-brain (active-standby) |\n| OR | N | At least N controls must be ON | Multi-cell minimum serving |\n\n**Critical:** every control panel with production traffic MUST have\nat least one safety rule. A control panel without safety rules is\nan accident waiting to happen.\n\n## Step 5 — Readiness checks\n\nReadiness checks validate that each cell has the required resources\nbefore failover. They run on a schedule (~5 minutes) and on demand.\n\n**Create a readiness check:**\n\n```bash\naws route53-recovery-readiness create-readiness-check \\\n  --readiness-check-name \"app-readiness-check\" \\\n  --resource-set-name \"app-nlb-resource-set\"\n```\n\n**Get readiness status:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#get-readiness-status-step-5).\n> get-readiness-check and get-cell-readiness commands.\n\n**Readiness states:**\n\n| State | Meaning |\n|---|---|\n| READY | All resources in the cell pass readiness checks |\n| NOT_READY | At least one resource is missing or unhealthy |\n| UNKNOWN | Readiness check has not run yet or has insufficient data |\n| NOT_AUTHORIZED | ARC lacks IAM permission to check the resource |\n\n**Create multiple readiness checks (one per resource set):**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#create-multiple-readiness-checks-one-per-resource-set-step-5).\n> Bash loop creating one readiness check per resource set.\n\n## Step 6 — Cross-region readiness assessment\n\nCross-region readiness assesses the readiness of ALL cells\nsimultaneously. It is the aggregate view used before failover.\n\n```bash\n# Get overall readiness across all cells\naws route53-recovery-readiness get-recovery-group-readiness-summary \\\n  --recovery-group-name \"app-recovery-group\"\n```\n\n**Creating a recovery group (groups multiple readiness checks):**\n\n```bash\naws route53-recovery-readiness create-recovery-group \\\n  --recovery-group-name \"app-recovery-group\" \\\n  --cells Cell-A Cell-B\n```\n\n**Before failover, ALWAYS check cross-cell readiness:**\n\n```bash\n# Check if Cell-B is READY before failing over from Cell-A\naws route53-recovery-readiness get-cell-readiness \\\n  --cell-name \"Cell-B\" \\\n  --query 'Readiness'\n# Expected: READY\n```\n\nIf Cell-B is NOT_READY, DO NOT fail over. Fix the missing resource\nfirst.\n\n## Step 7 — Routing control state and CloudWatch\n\nRouting control state changes are emitted to CloudWatch. This enables\nalerting on failover events and monitoring control state.\n\n**CloudWatch metrics for ARC:**\n\n| Metric | Namespace | Description |\n|---|---|---|\n| RoutingControlState | AWS\u002FRoute53RecoveryControl | Current state (1=ON, 0=OFF) |\n| SafetyRuleAssertions | AWS\u002FRoute53RecoveryControl | Safety rule evaluation count |\n| ClusterQuorumStatus | AWS\u002FRoute53RecoveryControl | Quorum health (1=healthy) |\n\n**Create a CloudWatch alarm for routing control state change:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#create-a-cloudwatch-alarm-for-routing-control-state-change-step-7).\n> put-metric-alarm firing when a routing control flips ON to OFF.\n\n## Step 8 — Failover execution patterns\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#failover-execution-patterns-from-step-8).\n> Active-standby failover, active-active drain, and failback toggle sequences.\n\n## Step 9 — Integration with Route 53 health checks\n\nARC routing controls integrate with Route 53 DNS failover via health\nchecks. The routing control state can be used as a health check input,\nso DNS failover follows the routing control toggle.\n\n**Create a Route 53 health check backed by a routing control:**\n\n> Moved to [references\u002Frouting-controls-and-safety.md](references\u002Frouting-controls-and-safety.md#route-53-health-check-creation-from-step-9).\n> create-health-check with Type RECOVERY_CONTROL backed by a routing control.\n\n## Step 10 — Recent features\n\n**Recent AWS features (2023-2026):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2023-2026).\n> Cluster API latency, safety-rule compositions, new readiness types, metrics, Terraform, multi-account.\n\n## NEVER do these things\n\n1. **NEVER deploy routing controls without safety rules.** Safety\n   rules prevent unsafe toggling. Without them, an operator can turn\n   all controls OFF simultaneously, causing a complete outage. Every\n   control panel MUST have at least one OR safety rule.\n\n2. **NEVER fail over to a cell without checking readiness first.**\n   Failing over to a NOT_READY cell means routing traffic to a cell\n   with missing or unhealthy resources. Always check\n   `get-cell-readiness` before toggling.\n\n3. **NEVER confuse the config API with the cluster API.** Routing\n   controls are CREATED via `route53-recovery-control-config` but\n   TOGGLED via `route53-recovery-cluster`. The config API cannot\n   change control state.\n\n4. **NEVER map resources to the wrong resource type in a resource\n   set.** Readiness checks use resource-type-specific templates. An\n   ALB mapped as `AWS::EC2::Instance` will fail readiness checks\n   silently.\n\n5. **NEVER assume routing control toggle is instantaneous.** Toggle\n   takes ~10 seconds for quorum agreement. During this time, the old\n   state is still effective. Plan for the propagation delay.\n\n6. **NEVER create a single-cell ARC setup.** ARC requires at least\n   two cells for failover. A single cell has nothing to fail over\n   to. Use health checks for single-cell monitoring instead.\n\n7. **NEVER forget IAM permissions for both APIs.** The config API\n   needs `route53-recovery-control-config:*` and\n   `route53-recovery-readiness:*`. The cluster API needs\n   `route53-recovery-cluster:*`. Missing either set breaks\n   provisioning or toggling.\n\n8. **NEVER use AND safety rules for active-active.** AND rules limit\n   to one control ON at a time (active-standby). For active-active,\n   use OR rules that enforce a minimum number of cells ON, not a\n   maximum.\n\n9. **NEVER skip the recovery group creation.** Recovery groups\n   aggregate multiple readiness checks into a single readiness view.\n   Without a recovery group, you must check each readiness check\n   individually, increasing the risk of missing one.\n\n10. **NEVER assume readiness checks are real-time.** Readiness checks\n    run on a ~5-minute schedule. A cell can become NOT_READY between\n    checks. Always run `get-cell-readiness` on demand before\n    failover.\n\n## Output format\n\n```text\nARC: \u003Ccluster-name> (\u003Ccluster-arn>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Recovery cluster: \u003Ccluster-name> — ACTIVE\n  [✓|✗] Cells: Cell-A (\u003Cregion>), Cell-B (\u003Cregion>)\n  [✓|✗] Resource sets: \u003Clist of resource sets with types>\n  [✓|✗] Control panel: \u003Cpanel-name>\n  [✓|✗] Routing controls: cell-a-traffic (\u003Carn>), cell-b-traffic (\u003Carn>)\n  [✓|✗] Safety rule: \u003Crule-name> (OR, threshold \u003Cn>) — prevents total outage\n  [✓|✗] Readiness checks: \u003Clist of readiness checks>\n  [✓|✗] Cross-region readiness: \u003CREADY | NOT_READY>\n  [✓|✗] Topology: Active-Active | Active-Standby\n  [✓|✗] CloudWatch alarm: \u003Calarm-name> for routing control state\n  [✓|✗] Route 53 health check integration: \u003Chealth-check-id>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws route53-recovery-control-config describe-cluster --cluster-arn \u003Ccluster-arn>\n  aws route53-recovery-cluster get-routing-control-state --routing-control-arn \u003Crc-arn>\n  aws route53-recovery-readiness get-cell-readiness --cell-name Cell-B\n```\n\n### Worked example — active-standby with safety rule\n\n```text\nARC: app-recovery-cluster (arn:aws:route53-recovery-control-config:us-east-1:123456789012:cluster\u002Fabc123)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Recovery cluster: app-recovery-cluster — ACTIVE\n  [✓] Cells: Cell-A (us-east-1), Cell-B (us-west-2)\n  [✓] Resource sets: app-nlb (AWS::ElasticLoadBalancingV2::LoadBalancer), app-asg (AWS::AutoScaling::AutoScalingGroup)\n  [✓] Control panel: app-failover-control-panel\n  [✓] Routing controls: cell-a-traffic (arn:...:routingcontrol\u002Fa-111), cell-b-traffic (arn:...:routingcontrol\u002Fb-222)\n  [✓] Safety rule: prevent-total-outage (OR, threshold 1) — prevents total outage\n  [✓] Readiness checks: app-nlb-check, app-asg-check\n  [✓] Cross-region readiness: READY\n  [✓] Topology: Active-Standby (Cell-A primary)\n  [✓] CloudWatch alarm: arc-routing-control-changed for cell-a-traffic\n  [✓] Route 53 health check integration: hcc-abc123 (RECOVERY_CONTROL type)\n  [✓] Tags: Environment=production, Application=app\nVERIFICATION_COMMANDS:\n  aws route53-recovery-control-config describe-cluster --cluster-arn arn:aws:route53-recovery-control-config:us-east-1:123456789012:cluster\u002Fabc123\n  aws route53-recovery-cluster get-routing-control-state --routing-control-arn arn:aws:route53-recovery-control-config:us-east-1:123456789012:controlpanel\u002Fxyz\u002Froutingcontrol\u002Fa-111\n  aws route53-recovery-readiness get-cell-readiness --cell-name Cell-B\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#error-handling).\n> Cluster stuck CREATING, toggle rejected, NOT_AUTHORIZED, type mismatch, stuck state.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — misconceptions, dependency graph, expert heuristics, failover patterns, recent features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — routing-control state, readiness status, CloudWatch alarm commands\n- [error-handling](references\u002Ferror-handling.md) — symptom-by-symptom troubleshooting\n- [routing-controls-and-safety](references\u002Frouting-controls-and-safety.md) — control, safety-rule, and health-check detail (existing)\n- [readiness-and-resource-sets](references\u002Freadiness-and-resource-sets.md) — readiness + resource-set detail (existing)\n\n## Domain\n\nAWS CloudOps \u002F Route 53 Application Recovery Controller Provisioning\n& Disaster Recovery Failover Orchestration.\n\n## AWS documentation\n\n- **ARC Overview** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Fwhat-is-ARC.html\n- **Routing controls** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Frouting-control.html\n- **Safety rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Fsafety-rules.html\n- **Readiness checks** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Freadiness-check.html\n- **Recovery clusters** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Frecovery-cluster.html\n- **ARC CLI reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-control-config\u002F\n- **ARC cluster CLI** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-cluster\u002F\n- **ARC readiness CLI** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-readiness\u002F\n","# Route 53 Application Recovery Controller Deployer\n\nAn AWS CloudOps agent skill that provisions Route 53 Application\nRecovery Controller (ARC) with correct defaults. The skill walks the\noperator through recovery cluster topology, routing control design\n(boolean toggle for traffic), safety rule construction (prevent\nunsafe multi-cell failover), cell grouping, resource set creation by\nresource type, readiness check configuration, and CloudWatch\nmonitoring of routing control state, captures topology and failover\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\nroute 53 ARC, application recovery controller, routing control,\nsafety rule, readiness check, recovery cluster, control panel, cell\nfailover, resource set, readiness scope.\n\n## STRICT output contract\n\nWhen this skill is invoked with an ARC provisioning request (create a\nrecovery cluster, routing controls, safety rules, readiness checks,\ncells, resource sets, control panels, 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`ARC:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do\nNOT preface the checklist with prose, headings, or disclaimers — emit\nthe block as the first lines of the response. This contract is what\nassertion-based evals and downstream provisioning pipelines rely on;\ndeviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the checklist\n(marked `[x]`), and `READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Recovery cluster architecture | Core infrastructure |\n| Step 2 — Cells and resource sets | Resource grouping |\n| Step 3 — Control panels and routing controls | Traffic control |\n| Step 4 — Safety rules (prevent unsafe failover) | Safety guardrails |\n| Step 5 — Readiness checks | Pre-failover validation |\n| Step 6 — Cross-region readiness assessment | Multi-region readiness |\n| Step 7 — Routing control state and CloudWatch | Monitoring |\n| Step 8 — Failover execution patterns | Operational |\n| Step 9 — Integration with Route 53 health checks | DNS integration |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frouting-controls-and-safety.md | Control + safety detail |\n| references\u002Freadiness-and-resource-sets.md | Readiness + resource detail |\n\n## Mindset\n\n**One-line takeaway:** Route 53 ARC provides routing controls —\nsingle boolean toggles that turn traffic on or off to a cell — with\nsafety rules that prevent unsafe failover (e.g., blocking all routing\ncontrols from being OFF simultaneously), backed by a five-cluster\nrecovery control data plane that maintains quorum across AWS regions.\nReadiness checks validate that a target cell has all required\nresources BEFORE you fail over to it.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#common-misconceptions-from-mindset).\n> Three ARC misconceptions: just a health check, free toggling, optional readiness checks.\n\n## Configuration dependency graph (novel heuristic)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph-sequencing-notes).\n> Sequencing table plus the safety-rule-before-production trap and API-split gotchas.\n\n## Expert heuristic: routing control as a boolean toggle\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-routing-control-as-a-boolean-toggle).\n> ON\u002FOFF semantics, active-active and failover sequences, atomic ~10s toggle.\n\n## Expert heuristic: safety rule types\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-safety-rule-types).\n> AND (mutual exclusion) vs OR (minimum ON) rules with rejection semantics.\n\n## Expert heuristic: readiness check resource templates\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-readiness-check-resource-templates).\n> Per-resource-type readiness template attributes (NLB, ASG, DynamoDB, Aurora, NAT, S3, Lambda).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Application spans 2+ regions or cells | ARC failover requires at least two cells to fail over between | Confirm multi-region or multi-cell topology |\n| Resources exist in each cell | Readiness checks validate resource existence | `aws resourcegroupstaggingapi get-resources --region \u003Cregion>` |\n| Resource ARNs identified | Resource sets map by ARN | Collect ARNs for each resource per cell |\n| Resource types identified | Readiness templates match by type | Map each resource to its CloudFormation type |\n| Failover topology decided (active-active vs active-standby) | Determines routing control design | Confirm topology |\n| IAM permissions for ARC APIs | Both config and cluster APIs need permissions | Verify `route53-recovery-control-config:*` and `route53-recovery-cluster:*` |\n| Safety rule design decided | Prevents unsafe failover | Confirm at least one safety rule per control panel |\n| Cells defined (which resources belong to which cell) | Resource grouping for failover | Confirm cell-to-resource mapping |\n\nIf any prerequisite is missing, output\n`VERDICT: PREREQUISITES_MISSING` and cite the specific gap.\n\n## Step 1 — Recovery cluster architecture\n\nThe recovery cluster is the data plane for routing controls. AWS\nprovisions five regional clusters across different AWS regions when\nyou create a recovery control configuration. These clusters maintain\nquorum to ensure routing control state is consistent.\n\n| Property | Value |\n|---|---|\n| Cluster count | 5 (auto-provisioned, spread across AWS regions) |\n| Quorum | 3 of 5 clusters must agree for a toggle to succeed |\n| Cluster creation time | ~10-15 minutes |\n| Data plane API | `route53-recovery-cluster` (separate from config API) |\n| Config API | `route53-recovery-control-config` |\n| Availability | Designed for 99.999% availability |\n\n**Create the recovery cluster:**\n\n```bash\nCLUSTER_ARN=$(aws route53-recovery-control-config create-cluster \\\n  --cluster-name \"my-app-recovery-cluster\" \\\n  --query 'Cluster.ClusterArn' --output text)\n\necho \"Cluster ARN: $CLUSTER_ARN\"\n# Wait for cluster to become ACTIVE (~10-15 minutes)\naws route53-recovery-control-config describe-cluster \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --query 'Cluster.Status'\n```\n\n**The cluster ARN is required for all subsequent operations.** The\ncluster provides the routing control data plane endpoints. State\ntoggles go through `route53-recovery-cluster` (not the config API).\n\n## Step 2 — Cells and resource sets\n\nA **cell** is a logical grouping of resources that represents one\ncomplete instance of an application. A multi-region application\ntypically has one cell per region (Cell-A = us-east-1, Cell-B =\nus-west-2).\n\nA **resource set** groups resources by type across cells. For\nexample, a resource set of type `AWS::NetworkLoadBalancer::LoadBalancer`\ncontains the NLB ARNs from Cell-A and Cell-B.\n\n> Moved to [references\u002Freadiness-and-resource-sets.md](references\u002Freadiness-and-resource-sets.md#cell-and-resource-set-layout-from-step-2).\n> Concrete Cell-A\u002FCell-B to resource-set mapping example.\n\n**Create a resource set:**\n\n```bash\naws route53-recovery-readiness create-resource-set \\\n  --resource-set-name \"app-nlb-resource-set\" \\\n  --resource-set-type \"AWS::ElasticLoadBalancingV2::LoadBalancer\" \\\n  --resources \\\n    ResourceArn=arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer\u002Fnet\u002Fapp-nlb-a\u002F50dc6c495c0c9188,ReadinessScopes=Cell-A \\\n    ResourceArn=arn:aws:elasticloadbalancing:us-west-2:123456789012:loadbalancer\u002Fnet\u002Fapp-nlb-b\u002F60dc6c495c0c9189,ReadinessScopes=Cell-B\n```\n\n**Critical:** each resource must be tagged with its cell\n(ReadinessScopes). The readiness check compares across cells using\nthese scopes.\n\n## Step 3 — Control panels and routing controls\n\nA **control panel** is a logical grouping of routing controls. A\n**routing control** is a single boolean toggle (ON\u002FOFF) that\ncontrols traffic to a cell.\n\n**Create a control panel:**\n\n```bash\naws route53-recovery-control-config create-control-panel \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\"\n```\n\n**Create routing controls (one per cell):**\n\n```bash\n# Cell-A routing control\nRC_A_ARN=$(aws route53-recovery-control-config create-routing-control \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\" \\\n  --routing-control-name \"cell-a-traffic\" \\\n  --query 'RoutingControl.RoutingControlArn' --output text)\n\n# Cell-B routing control\nRC_B_ARN=$(aws route53-recovery-control-config create-routing-control \\\n  --cluster-arn \"$CLUSTER_ARN\" \\\n  --control-panel-name \"app-failover-control-panel\" \\\n  --routing-control-name \"cell-b-traffic\" \\\n  --query 'RoutingControl.RoutingControlArn' --output text)\n```\n\n**Initial state:** routing controls start in the OFF position. Both\ncontrols being OFF means no traffic. You must explicitly toggle the\nactive cell's control ON.\n\n**Toggle a routing control ON (via cluster API):**\n\n```bash\naws route53-recovery-cluster update-routing-control-state \\\n  --routing-control-arn \"$RC_A_ARN\" \\\n  --routing-control-state \"On\"\n```\n\n**Verify routing control state:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#verify-routing-control-state-step-3).\n> get-routing-control-state check expecting \"On\".\n\n## Step 4 — Safety rules (prevent unsafe failover)\n\nSafety rules are the guardrails that prevent unsafe routing control\ntoggles. Without them, an operator or automation can turn all\ncontrols OFF, causing a complete outage.\n\n**Create an OR safety rule (at least one cell must be ON):**\n\n```bash\naws route53-recovery-control-config create-safety-rule \\\n  --control-panel-arn \"$CONTROL_PANEL_ARN\" \\\n  --safety-rule-name \"prevent-total-outage\" \\\n  --rule-config '{\"Type\":\"OR\",\"Inverted\":false,\"Threshold\":1}' \\\n  --routing-controls-arns \"$RC_A_ARN\" \"$RC_B_ARN\"\n```\n\nThis rule means: at least 1 of the 2 listed routing controls must be\nON at all times. If you try to turn the last ON control OFF, the API\nrejects the request.\n\n**Create an AND safety rule (mutual exclusion):**\n\n```bash\naws route53-recovery-control-config create-safety-rule \\\n  --control-panel-arn \"$CONTROL_PANEL_ARN\" \\\n  --safety-rule-name \"prevent-split-brain\" \\\n  --rule-config '{\"Type\":\"AND\",\"Inverted\":false,\"Threshold\":1}' \\\n  --routing-controls-arns \"$RC_A_ARN\" \"$RC_B_ARN\"\n```\n\nThis rule (Type AND, Threshold 1) means: at most 1 of the 2 listed\nrouting controls can be ON. If you try to turn the second control ON\nwhile the first is already ON, the API rejects the request.\n\n**Safety rule semantics:**\n\n| Rule Type | Threshold | Meaning | Use case |\n|---|---|---|---|\n| OR | 1 | At least 1 control must be ON | Prevent total outage |\n| AND | 1 | At most 1 control can be ON | Prevent split-brain (active-standby) |\n| OR | N | At least N controls must be ON | Multi-cell minimum serving |\n\n**Critical:** every control panel with production traffic MUST have\nat least one safety rule. A control panel without safety rules is\nan accident waiting to happen.\n\n## Step 5 — Readiness checks\n\nReadiness checks validate that each cell has the required resources\nbefore failover. They run on a schedule (~5 minutes) and on demand.\n\n**Create a readiness check:**\n\n```bash\naws route53-recovery-readiness create-readiness-check \\\n  --readiness-check-name \"app-readiness-check\" \\\n  --resource-set-name \"app-nlb-resource-set\"\n```\n\n**Get readiness status:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#get-readiness-status-step-5).\n> get-readiness-check and get-cell-readiness commands.\n\n**Readiness states:**\n\n| State | Meaning |\n|---|---|\n| READY | All resources in the cell pass readiness checks |\n| NOT_READY | At least one resource is missing or unhealthy |\n| UNKNOWN | Readiness check has not run yet or has insufficient data |\n| NOT_AUTHORIZED | ARC lacks IAM permission to check the resource |\n\n**Create multiple readiness checks (one per resource set):**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#create-multiple-readiness-checks-one-per-resource-set-step-5).\n> Bash loop creating one readiness check per resource set.\n\n## Step 6 — Cross-region readiness assessment\n\nCross-region readiness assesses the readiness of ALL cells\nsimultaneously. It is the aggregate view used before failover.\n\n```bash\n# Get overall readiness across all cells\naws route53-recovery-readiness get-recovery-group-readiness-summary \\\n  --recovery-group-name \"app-recovery-group\"\n```\n\n**Creating a recovery group (groups multiple readiness checks):**\n\n```bash\naws route53-recovery-readiness create-recovery-group \\\n  --recovery-group-name \"app-recovery-group\" \\\n  --cells Cell-A Cell-B\n```\n\n**Before failover, ALWAYS check cross-cell readiness:**\n\n```bash\n# Check if Cell-B is READY before failing over from Cell-A\naws route53-recovery-readiness get-cell-readiness \\\n  --cell-name \"Cell-B\" \\\n  --query 'Readiness'\n# Expected: READY\n```\n\nIf Cell-B is NOT_READY, DO NOT fail over. Fix the missing resource\nfirst.\n\n## Step 7 — Routing control state and CloudWatch\n\nRouting control state changes are emitted to CloudWatch. This enables\nalerting on failover events and monitoring control state.\n\n**CloudWatch metrics for ARC:**\n\n| Metric | Namespace | Description |\n|---|---|---|\n| RoutingControlState | AWS\u002FRoute53RecoveryControl | Current state (1=ON, 0=OFF) |\n| SafetyRuleAssertions | AWS\u002FRoute53RecoveryControl | Safety rule evaluation count |\n| ClusterQuorumStatus | AWS\u002FRoute53RecoveryControl | Quorum health (1=healthy) |\n\n**Create a CloudWatch alarm for routing control state change:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#create-a-cloudwatch-alarm-for-routing-control-state-change-step-7).\n> put-metric-alarm firing when a routing control flips ON to OFF.\n\n## Step 8 — Failover execution patterns\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#failover-execution-patterns-from-step-8).\n> Active-standby failover, active-active drain, and failback toggle sequences.\n\n## Step 9 — Integration with Route 53 health checks\n\nARC routing controls integrate with Route 53 DNS failover via health\nchecks. The routing control state can be used as a health check input,\nso DNS failover follows the routing control toggle.\n\n**Create a Route 53 health check backed by a routing control:**\n\n> Moved to [references\u002Frouting-controls-and-safety.md](references\u002Frouting-controls-and-safety.md#route-53-health-check-creation-from-step-9).\n> create-health-check with Type RECOVERY_CONTROL backed by a routing control.\n\n## Step 10 — Recent features\n\n**Recent AWS features (2023-2026):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2023-2026).\n> Cluster API latency, safety-rule compositions, new readiness types, metrics, Terraform, multi-account.\n\n## NEVER do these things\n\n1. **NEVER deploy routing controls without safety rules.** Safety\n   rules prevent unsafe toggling. Without them, an operator can turn\n   all controls OFF simultaneously, causing a complete outage. Every\n   control panel MUST have at least one OR safety rule.\n\n2. **NEVER fail over to a cell without checking readiness first.**\n   Failing over to a NOT_READY cell means routing traffic to a cell\n   with missing or unhealthy resources. Always check\n   `get-cell-readiness` before toggling.\n\n3. **NEVER confuse the config API with the cluster API.** Routing\n   controls are CREATED via `route53-recovery-control-config` but\n   TOGGLED via `route53-recovery-cluster`. The config API cannot\n   change control state.\n\n4. **NEVER map resources to the wrong resource type in a resource\n   set.** Readiness checks use resource-type-specific templates. An\n   ALB mapped as `AWS::EC2::Instance` will fail readiness checks\n   silently.\n\n5. **NEVER assume routing control toggle is instantaneous.** Toggle\n   takes ~10 seconds for quorum agreement. During this time, the old\n   state is still effective. Plan for the propagation delay.\n\n6. **NEVER create a single-cell ARC setup.** ARC requires at least\n   two cells for failover. A single cell has nothing to fail over\n   to. Use health checks for single-cell monitoring instead.\n\n7. **NEVER forget IAM permissions for both APIs.** The config API\n   needs `route53-recovery-control-config:*` and\n   `route53-recovery-readiness:*`. The cluster API needs\n   `route53-recovery-cluster:*`. Missing either set breaks\n   provisioning or toggling.\n\n8. **NEVER use AND safety rules for active-active.** AND rules limit\n   to one control ON at a time (active-standby). For active-active,\n   use OR rules that enforce a minimum number of cells ON, not a\n   maximum.\n\n9. **NEVER skip the recovery group creation.** Recovery groups\n   aggregate multiple readiness checks into a single readiness view.\n   Without a recovery group, you must check each readiness check\n   individually, increasing the risk of missing one.\n\n10. **NEVER assume readiness checks are real-time.** Readiness checks\n    run on a ~5-minute schedule. A cell can become NOT_READY between\n    checks. Always run `get-cell-readiness` on demand before\n    failover.\n\n## Output format\n\n```text\nARC: \u003Ccluster-name> (\u003Ccluster-arn>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Recovery cluster: \u003Ccluster-name> — ACTIVE\n  [✓|✗] Cells: Cell-A (\u003Cregion>), Cell-B (\u003Cregion>)\n  [✓|✗] Resource sets: \u003Clist of resource sets with types>\n  [✓|✗] Control panel: \u003Cpanel-name>\n  [✓|✗] Routing controls: cell-a-traffic (\u003Carn>), cell-b-traffic (\u003Carn>)\n  [✓|✗] Safety rule: \u003Crule-name> (OR, threshold \u003Cn>) — prevents total outage\n  [✓|✗] Readiness checks: \u003Clist of readiness checks>\n  [✓|✗] Cross-region readiness: \u003CREADY | NOT_READY>\n  [✓|✗] Topology: Active-Active | Active-Standby\n  [✓|✗] CloudWatch alarm: \u003Calarm-name> for routing control state\n  [✓|✗] Route 53 health check integration: \u003Chealth-check-id>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws route53-recovery-control-config describe-cluster --cluster-arn \u003Ccluster-arn>\n  aws route53-recovery-cluster get-routing-control-state --routing-control-arn \u003Crc-arn>\n  aws route53-recovery-readiness get-cell-readiness --cell-name Cell-B\n```\n\n### Worked example — active-standby with safety rule\n\n```text\nARC: app-recovery-cluster (arn:aws:route53-recovery-control-config:us-east-1:123456789012:cluster\u002Fabc123)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Recovery cluster: app-recovery-cluster — ACTIVE\n  [✓] Cells: Cell-A (us-east-1), Cell-B (us-west-2)\n  [✓] Resource sets: app-nlb (AWS::ElasticLoadBalancingV2::LoadBalancer), app-asg (AWS::AutoScaling::AutoScalingGroup)\n  [✓] Control panel: app-failover-control-panel\n  [✓] Routing controls: cell-a-traffic (arn:...:routingcontrol\u002Fa-111), cell-b-traffic (arn:...:routingcontrol\u002Fb-222)\n  [✓] Safety rule: prevent-total-outage (OR, threshold 1) — prevents total outage\n  [✓] Readiness checks: app-nlb-check, app-asg-check\n  [✓] Cross-region readiness: READY\n  [✓] Topology: Active-Standby (Cell-A primary)\n  [✓] CloudWatch alarm: arc-routing-control-changed for cell-a-traffic\n  [✓] Route 53 health check integration: hcc-abc123 (RECOVERY_CONTROL type)\n  [✓] Tags: Environment=production, Application=app\nVERIFICATION_COMMANDS:\n  aws route53-recovery-control-config describe-cluster --cluster-arn arn:aws:route53-recovery-control-config:us-east-1:123456789012:cluster\u002Fabc123\n  aws route53-recovery-cluster get-routing-control-state --routing-control-arn arn:aws:route53-recovery-control-config:us-east-1:123456789012:controlpanel\u002Fxyz\u002Froutingcontrol\u002Fa-111\n  aws route53-recovery-readiness get-cell-readiness --cell-name Cell-B\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#error-handling).\n> Cluster stuck CREATING, toggle rejected, NOT_AUTHORIZED, type mismatch, stuck state.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — misconceptions, dependency graph, expert heuristics, failover patterns, recent features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — routing-control state, readiness status, CloudWatch alarm commands\n- [error-handling](references\u002Ferror-handling.md) — symptom-by-symptom troubleshooting\n- [routing-controls-and-safety](references\u002Frouting-controls-and-safety.md) — control, safety-rule, and health-check detail (existing)\n- [readiness-and-resource-sets](references\u002Freadiness-and-resource-sets.md) — readiness + resource-set detail (existing)\n\n## Domain\n\nAWS CloudOps \u002F Route 53 Application Recovery Controller Provisioning\n& Disaster Recovery Failover Orchestration.\n\n## AWS documentation\n\n- **ARC Overview** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Fwhat-is-ARC.html\n- **Routing controls** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Frouting-control.html\n- **Safety rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Fsafety-rules.html\n- **Readiness checks** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Freadiness-check.html\n- **Recovery clusters** — https:\u002F\u002Fdocs.aws.amazon.com\u002Froute53\u002Flatest\u002FARCGuide\u002Frecovery-cluster.html\n- **ARC CLI reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-control-config\u002F\n- **ARC cluster CLI** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-cluster\u002F\n- **ARC readiness CLI** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Froute53-recovery-readiness\u002F\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, route-53-arc, application-recovery-controller, cloudops, deploy, networking, disaster-recovery, failover, routing-control, readiness-check, safety-rule","1","Jacky Chan — AWS Community Builder","aws-cloudops","Networking","0.1.0","aws, route 53 arc, application recovery controller, routing control, safety rule, readiness check, recovery cluster, control panel, cell failover, resource set, cloudops, deploy, provisioning, disaster recovery, failover","deploy","high","false","capability","Invoke when the user wants to set up Route 53 Application Recovery Controller for application failover orchestration — creating routing controls (traffic on\u002Foff switches), safety rules (prevent unsafe failover), readiness checks (validate cells before failover), resource sets, cells, control panels, or recovery clusters. Do NOT invoke for Route 53 health checks (use health-check skills), Route 53 DNS failover (use dns-failover skills), or Elastic Disaster Recovery (use drs skills).","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 route53-recovery-control-config, route53-recovery-readiness, and route53-recovery-cluster access. Works with Terraform aws_route53recoverycontrolconfig_* and aws_route53recoveryreadiness_* resources and CloudFormation AWS::Route53RecoveryControl::* templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Froute53-application-recovery-controller-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 route53-application-recovery-controller-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill route53-application-recovery-controller-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill route53-application-recovery-controller-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-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","参考文档",6237,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Factive-active-cross-region-readiness.md",609,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fbaselines\u002Factive-active-cross-region-readiness.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Factive-standby-with-safety-rule.md",687,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fbaselines\u002Factive-standby-with-safety-rule.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-safety-rule.md",685,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fbaselines\u002Fmissing-safety-rule.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fresource-set-type-mapping.md",577,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fbaselines\u002Fresource-set-type-mapping.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fsafety-rule-design-and-or.md",524,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fbaselines\u002Fsafety-rule-design-and-or.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1875,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9346,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Factive-active-cross-region-readiness.md",607,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fprompts\u002Factive-active-cross-region-readiness.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Factive-standby-with-safety-rule.md",948,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fprompts\u002Factive-standby-with-safety-rule.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-safety-rule.md",416,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fprompts\u002Fmissing-safety-rule.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fresource-set-type-mapping.md",600,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fprompts\u002Fresource-set-type-mapping.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fsafety-rule-design-and-or.md",535,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fevals\u002Fprompts\u002Fsafety-rule-design-and-or.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6259,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",9799,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fdiagnostic-commands.md",1521,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1319,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Freadiness-and-resource-sets.md",8774,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Freferences\u002Freadiness-and-resource-sets.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Frouting-controls-and-safety.md",8237,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-deployer\u002Freferences\u002Frouting-controls-and-safety.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4698,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Froute53-application-recovery-controller-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",[],[]]