[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-arc-region-switch":3,"mdc--rxxd1u-key":35,"related-repo-aws-arc-region-switch":1319,"related-org-aws-arc-region-switch":1425},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"arc-region-switch","manage Amazon ARC region switches","Answers questions about Amazon Application Recovery Controller (ARC) Region switch including architecture, plans, execution blocks, workflows, triggers, active\u002Factive vs active\u002Fpassive, cross-account support, recovery time, dashboards, and customer positioning. Applicable when users ask about ARC Region switch adoption, design, or troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"aws","AWS (Amazon)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Faws.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Architecture","architecture",{"name":20,"slug":21,"type":15},"Monitoring","monitoring",{"name":23,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-25T05:56:38.085915",null,157,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS","https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws\u002Ftree\u002FHEAD\u002Fskills\u002Fspecialized-skills\u002Fresilience-skills\u002Farc-region-switch","---\nname: arc-region-switch\ndescription: \"Answers questions about Amazon Application Recovery Controller (ARC) Region switch including architecture, plans, execution blocks, workflows, triggers, active\u002Factive vs active\u002Fpassive, cross-account support, recovery time, dashboards, and customer positioning. Applicable when users ask about ARC Region switch adoption, design, or troubleshooting.\"\nversion: 1\n---\n\n# ARC Region switch Expert\n\n## Overview\n\nMakes the agent an expert on **Amazon Application Recovery Controller (ARC) Region switch** — the feature for orchestrating cross-Region workload failover and switchover. Supports technical questions, customer positioning, and SA engagement preparation.\n\nRegion switch orchestrates recovery for applications already deployed multi-Region. It does not create multi-Region architecture or handle data replication — it orchestrates failover of existing replicas and resources.\n\n## Guardrail — where this skill's own files live (MCP vs local install)\n\nBefore reading a reference file, determine how this skill was loaded:\n\n- **Loaded via the AWS MCP `retrieve_skill` tool:** the skill's reference files are not on the local filesystem. Fetch each one through `retrieve_skill` with the `file` parameter (e.g. `file=\"references\u002Fpositioning.md\"` or `file=\"references\u002Fdoc-links.md\"`) — do NOT `file_read` these paths locally or search the filesystem for them.\n- **Installed locally** (e.g. `.kiro\u002Fskills\u002Farc-region-switch\u002F` or `~\u002F.claude\u002Fskills\u002Farc-region-switch\u002F`): read reference files from the local skill directory using the relative paths shown here.\n\nThis applies only to the skill's own reference files; always read and write user or session data in the working directory, never through `retrieve_skill`.\n\n## When Not to Use\n\n- **In-Region failover** — Region switch is for cross-Region recovery only. Use AZ-level mechanisms (ALB, Auto Scaling) for in-Region resilience.\n- **Data replication design** — Region switch orchestrates failover of existing replicas; it does not set up or manage replication. Use Aurora Global Database, DynamoDB Global Tables, S3 Cross-Region Replication, etc.\n- **AZ-level resiliency** — For Availability Zone failures within a single Region, use multi-AZ architecture patterns instead.\n\n## Terminology Constraints\n\n- ALWAYS use \"Region switch\" (lowercase 's') for the product name\n- Use \"Routing Controls\" only when referring to the Routing Controls execution block or the legacy cluster-based approach — do not use it as a synonym for Region switch\n- Do NOT conflate **triggers** (CloudWatch alarms that start execution) with **application health alarms** (measure actual recovery time)\n- Region switch orchestrates failover — it does NOT replicate data\n\n## Critical Warnings\n\n- **Irreversible in-progress steps**: Plan executions can be paused or cancelled, but any step that is already started cannot be reversed without another plan execution.\n- **Monitor during events**: Customers should still monitor their application health during an event, even if they configure plan triggers to automatically start a plan execution.\n- **Regional endpoint matters**: When deactivating a Region, call `start-plan-execution` from the healthy Region, not the Region being deactivated. When activating a Region, call from the Region being activated. See [StartPlanExecution API](https:\u002F\u002Fdocs.aws.amazon.com\u002Farc-region-switch\u002Flatest\u002Fapi\u002FAPI_StartPlanExecution.html).\n\n## Workflow\n\n1. Classify the question: technical architecture, customer positioning, how-to, troubleshooting, or comparison\n2. Answer from embedded knowledge in this skill\n3. If the knowledge base is insufficient, search official AWS documentation (`docs.aws.amazon.com`)\n4. Format the response for the audience (engineer, SA, customer)\n\nAlways validate:\n\n- Correct terminology (Region switch, not routing controls for plan-based features)\n- Include doc links where helpful (see Documentation Links section)\n- Use positioning language from the Positioning section\n\n## Architecture\n\n### Components\n\n| Component | Description |\n|-----------|-------------|\n| **Plan** | Top-level resource scoped to a multi-Region application. Contains workflows. |\n| **Child Plan** | A self-contained plan nested within a parent plan (one level deep). |\n| **Workflow** | Ordered sequence of steps within a plan. Defines activation\u002Fdeactivation logic. |\n| **Step** | Container for one or more execution blocks, run in parallel or sequence. |\n| **Execution Block** | Performs a specific recovery action (e.g., scale up, reroute traffic, failover DB). |\n| **Trigger** | CloudWatch alarm-based automation that initiates plan execution. |\n| **Application Health Alarms** | CloudWatch alarms indicating app health per Region; used to calculate actual recovery time. |\n| **Post-recovery Workflow** | Optional workflow that runs after recovery to prepare for future events. |\n| **Plan Evaluation** | Automated checks verifying plan execution readiness. Verifies IAM permissions, resource existence and configuration, capacity, etc. |\n| **Automatic Execution Reports** | PDF reports delivered to S3 after each plan execution for compliance\u002Faudit. |\n\n### Execution Modes\n\nRecommend using graceful execution unless not possible (e.g., when an execution block has a dependency on the impaired Region — such as Aurora\u002FDocumentDB\u002FNeptune switchover requiring connectivity to the impaired Region, or a Custom Action Lambda deployed in the impaired Region).\n\n- **Graceful**: Runs all steps in orderly sequence. Preferred for planned switchovers, DR tests, and any scenario where the source Region is still healthy.\n- **Ungraceful**: Skips or modifies certain execution blocks — only critical steps run. Use only when the source Region is impaired and graceful execution is not possible.\n- **Post-recovery**: Runs after successful recovery in the previously-impaired Region. Requires both Regions to be healthy. Supports a subset of execution blocks — see the [Add execution blocks](https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Fworking-with-rs-execution-blocks.html) documentation for the current set.\n\n### Active\u002FPassive vs Active\u002FActive\n\n| Approach | Workflows Needed | Behavior |\n|----------|-----------------|----------|\n| **Active\u002FPassive** | 1 activation workflow (either Region) OR 2 separate activation workflows (one per Region) | Failover from primary to standby; failback when primary recovers |\n| **Active\u002FActive** | 1 activation workflow + 1 deactivation workflow per Region | Shift-away from impaired Region + return when healthy |\n\n### Supported Execution Blocks\n\nExecution blocks are the individual step types a Region switch workflow is composed of — each performs one recovery action, spanning traffic\u002FDNS rerouting, compute scaling, database failover, custom-action Lambdas, manual-approval gates, and nested child plans.\n\n**Do not rely on a hardcoded list of block types** — ARC adds and changes execution blocks over time. Retrieve the current supported set at query time from the [Components & concepts](https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Fcomponents-rs.html) and [Add execution blocks](https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Fworking-with-rs-execution-blocks.html) documentation.\n\n### Recovery Time Tracking\n\n- **Recovery Time Objective (RTO)**: Set when creating a plan\n- **Actual Recovery Time**: Plan execution time + time for application health alarms to return to green\n- Visible on plan execution details page for comparison against RTO\n\n### Plan Evaluation\n\n- Validates: IAM permissions, resource configurations, running capacity\n- Warnings surfaced in console, EventBridge, and API\n- Passing evaluation alone is NOT sufficient — always test by executing plans\n\n### Automatic Execution Reports\n\n- PDF reports generated after each plan execution\n- Delivered to customer-specified S3 bucket (within ~30 min)\n- Customers must configure the S3 bucket and update permissions for the PlanExecutionRole to enable reporting\n- Contents: executive summary, plan config, execution timeline, resource states, alarm history, child plan details, glossary\n- Useful for regulatory compliance and DR audit evidence\n- See Security Considerations for encryption and access control guidance\n\n## Cross-Account Support\n\nPlans can orchestrate resources across multiple AWS accounts via IAM roles with cross-account trust policies. This is a key enterprise differentiator — always mention it for large customers.\n\nWhen configuring cross-account trust policies:\n\n- Include condition keys (`aws:SourceArn`, `aws:SourceAccount`, `sts:ExternalId`) to prevent confused deputy attacks\n- Scope IAM policies to least privilege — avoid `*` resource wildcards and `FullAccess` managed policies\n- Scope permissions to only the specific resources (ASG ARNs, Aurora cluster ARNs, Route 53 health check ARNs, etc.) referenced in execution blocks\n\n## Regional Availability\n\nAvailable in multiple commercial AWS Regions and AWS GovCloud (US) Regions — always verify the current list before stating availability to a customer, as Region coverage changes over time. Each Region has its own data-plane endpoint (`arc-region-switch.\u003Cregion>.api.aws`), ensuring execution doesn't depend on the impaired Region.\n\n> Verify the complete list of available regions\u002Fendpoints at [AWS Regions & endpoints](https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Faws-regions-rs.html).\n\n## Security Considerations\n\n### IAM Least Privilege\n\n- Scope cross-account IAM roles to only the specific resources referenced in execution blocks (ASG ARNs, Aurora cluster ARNs, Route 53 health check ARNs, Lambda function ARNs, etc.)\n- Avoid `*` resource wildcards and `FullAccess` managed policies\n- Include condition keys (`aws:SourceArn`, `aws:SourceAccount`, `sts:ExternalId`) in cross-account trust policies to prevent confused deputy attacks\n\n### Execution Reports S3 Bucket\n\n- Enable default encryption (SSE-KMS preferred) on the reports S3 bucket\n- Add a bucket policy denying requests where `aws:SecureTransport` is `false` (enforce TLS)\n- Restrict bucket access to authorized personnel only — reports contain sensitive infrastructure details (plan config, execution timeline, resource states, alarm history)\n- Enable S3 bucket versioning and MFA Delete for tamper protection\n- Ensure the bucket is not publicly accessible\n\n### Custom Action Lambda Security\n\n- Apply least-privilege execution roles to Custom Action Lambda functions\n- Validate inputs within Lambda functions\n- Do not embed secrets in Lambda environment variables — use Secrets Manager or Parameter Store\n\n### Notification & Event Targets\n\n- Restrict EventBridge rule targets (SNS topics, Lambda functions, etc.) that receive plan-evaluation warnings and execution events to authorized recipients only\n- Lock down SNS topic subscription policies and Lambda resource policies so sensitive infrastructure details (plan configuration, resource ARNs, execution state) are not exposed to unauthorized parties\n\n### Logging and Monitoring\n\n- Enable AWS CloudTrail for auditing all ARC Region switch API calls\n- Configure CloudWatch alarms for unexpected or unauthorized plan executions\n- Enable S3 access logging on the execution reports bucket\n- See [Logging and monitoring for Region switch](https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Flogging-and-monitoring-rs.html)\n\n## Positioning\n\nCustomer-facing framing, the Region switch vs Routing Controls comparison, analyst talking\npoints, and per-audience conversation guidance are maintained in\n**[Positioning](references\u002Fpositioning.md)**. Load that reference for any customer-positioning,\ncompetitive-comparison, or analyst-briefing question. Key rules that always apply:\n\n- Use \"Region switch\" (plan-based orchestration) framing; do NOT present legacy \"routing controls\"\n  \u002F \"ARC clusters\" language as the Region switch (plan-based) approach.\n- Always mention **cross-account** support and **data-plane-per-Region** isolation for enterprise customers.\n\n## Documentation Links\n\nThe curated documentation index and the \"when to link which doc\" guidance live in\n**[Documentation Links](references\u002Fdoc-links.md)**. Load that reference to attach the right AWS\ndoc to an answer (overview, components & concepts, execution blocks, API\u002FCLI, security & IAM,\nlogging & monitoring, quotas, Terraform provider).\n\n## Troubleshooting\n\n### Customer confuses triggers with health alarms\nTriggers are CloudWatch alarms that **start** plan execution. Application health alarms **measure** when recovery is complete. They serve different purposes and are configured separately.\n\n### Customer assumes Region switch handles data sync\nClarify: Region switch orchestrates failover of existing replicas (e.g., Aurora Global DB promotion). The customer must set up multi-Region data replication independently.\n\n### Cross-account execution fails\nUsually missing IAM permissions. Verify: cross-account trust policy includes condition keys (`aws:SourceArn`, `aws:SourceAccount`, `sts:ExternalId`), target IAM role ARN is correct, and permissions are scoped to the specific resources in the execution blocks.\n\n### Plan evaluation warnings\nWarnings indicate IAM, resource, or capacity issues. Fix the underlying issue — but note that passing evaluation alone isn't sufficient; always test by executing plans.\n\n### Wrong Regional endpoint used\nWhen deactivating a Region, `start-plan-execution` MUST be called from the healthy Region. When activating a Region, it MUST be called from the Region being activated. Using the wrong endpoint will fail or produce unexpected behavior. See [StartPlanExecution API](https:\u002F\u002Fdocs.aws.amazon.com\u002Farc-region-switch\u002Flatest\u002Fapi\u002FAPI_StartPlanExecution.html).\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,50,57,71,76,82,87,175,187,193,226,232,269,275,326,332,364,369,387,391,398,585,591,596,638,644,713,719,724,750,756,784,789,807,812,845,851,856,861,918,924,937,954,960,966,1014,1020,1064,1070,1088,1094,1107,1113,1143,1149,1164,1191,1197,1212,1218,1224,1243,1249,1254,1260,1284,1290,1295,1301],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"arc-region-switch-expert",[47],{"type":48,"value":49},"text","ARC Region switch Expert",{"type":42,"tag":51,"props":52,"children":54},"h2",{"id":53},"overview",[55],{"type":48,"value":56},"Overview",{"type":42,"tag":58,"props":59,"children":60},"p",{},[61,63,69],{"type":48,"value":62},"Makes the agent an expert on ",{"type":42,"tag":64,"props":65,"children":66},"strong",{},[67],{"type":48,"value":68},"Amazon Application Recovery Controller (ARC) Region switch",{"type":48,"value":70}," — the feature for orchestrating cross-Region workload failover and switchover. Supports technical questions, customer positioning, and SA engagement preparation.",{"type":42,"tag":58,"props":72,"children":73},{},[74],{"type":48,"value":75},"Region switch orchestrates recovery for applications already deployed multi-Region. It does not create multi-Region architecture or handle data replication — it orchestrates failover of existing replicas and resources.",{"type":42,"tag":51,"props":77,"children":79},{"id":78},"guardrail-where-this-skills-own-files-live-mcp-vs-local-install",[80],{"type":48,"value":81},"Guardrail — where this skill's own files live (MCP vs local install)",{"type":42,"tag":58,"props":83,"children":84},{},[85],{"type":48,"value":86},"Before reading a reference file, determine how this skill was loaded:",{"type":42,"tag":88,"props":89,"children":90},"ul",{},[91,150],{"type":42,"tag":92,"props":93,"children":94},"li",{},[95,109,111,116,118,124,126,132,134,140,142,148],{"type":42,"tag":64,"props":96,"children":97},{},[98,100,107],{"type":48,"value":99},"Loaded via the AWS MCP ",{"type":42,"tag":101,"props":102,"children":104},"code",{"className":103},[],[105],{"type":48,"value":106},"retrieve_skill",{"type":48,"value":108}," tool:",{"type":48,"value":110}," the skill's reference files are not on the local filesystem. Fetch each one through ",{"type":42,"tag":101,"props":112,"children":114},{"className":113},[],[115],{"type":48,"value":106},{"type":48,"value":117}," with the ",{"type":42,"tag":101,"props":119,"children":121},{"className":120},[],[122],{"type":48,"value":123},"file",{"type":48,"value":125}," parameter (e.g. ",{"type":42,"tag":101,"props":127,"children":129},{"className":128},[],[130],{"type":48,"value":131},"file=\"references\u002Fpositioning.md\"",{"type":48,"value":133}," or ",{"type":42,"tag":101,"props":135,"children":137},{"className":136},[],[138],{"type":48,"value":139},"file=\"references\u002Fdoc-links.md\"",{"type":48,"value":141},") — do NOT ",{"type":42,"tag":101,"props":143,"children":145},{"className":144},[],[146],{"type":48,"value":147},"file_read",{"type":48,"value":149}," these paths locally or search the filesystem for them.",{"type":42,"tag":92,"props":151,"children":152},{},[153,158,160,166,167,173],{"type":42,"tag":64,"props":154,"children":155},{},[156],{"type":48,"value":157},"Installed locally",{"type":48,"value":159}," (e.g. ",{"type":42,"tag":101,"props":161,"children":163},{"className":162},[],[164],{"type":48,"value":165},".kiro\u002Fskills\u002Farc-region-switch\u002F",{"type":48,"value":133},{"type":42,"tag":101,"props":168,"children":170},{"className":169},[],[171],{"type":48,"value":172},"~\u002F.claude\u002Fskills\u002Farc-region-switch\u002F",{"type":48,"value":174},"): read reference files from the local skill directory using the relative paths shown here.",{"type":42,"tag":58,"props":176,"children":177},{},[178,180,185],{"type":48,"value":179},"This applies only to the skill's own reference files; always read and write user or session data in the working directory, never through ",{"type":42,"tag":101,"props":181,"children":183},{"className":182},[],[184],{"type":48,"value":106},{"type":48,"value":186},".",{"type":42,"tag":51,"props":188,"children":190},{"id":189},"when-not-to-use",[191],{"type":48,"value":192},"When Not to Use",{"type":42,"tag":88,"props":194,"children":195},{},[196,206,216],{"type":42,"tag":92,"props":197,"children":198},{},[199,204],{"type":42,"tag":64,"props":200,"children":201},{},[202],{"type":48,"value":203},"In-Region failover",{"type":48,"value":205}," — Region switch is for cross-Region recovery only. Use AZ-level mechanisms (ALB, Auto Scaling) for in-Region resilience.",{"type":42,"tag":92,"props":207,"children":208},{},[209,214],{"type":42,"tag":64,"props":210,"children":211},{},[212],{"type":48,"value":213},"Data replication design",{"type":48,"value":215}," — Region switch orchestrates failover of existing replicas; it does not set up or manage replication. Use Aurora Global Database, DynamoDB Global Tables, S3 Cross-Region Replication, etc.",{"type":42,"tag":92,"props":217,"children":218},{},[219,224],{"type":42,"tag":64,"props":220,"children":221},{},[222],{"type":48,"value":223},"AZ-level resiliency",{"type":48,"value":225}," — For Availability Zone failures within a single Region, use multi-AZ architecture patterns instead.",{"type":42,"tag":51,"props":227,"children":229},{"id":228},"terminology-constraints",[230],{"type":48,"value":231},"Terminology Constraints",{"type":42,"tag":88,"props":233,"children":234},{},[235,240,245,264],{"type":42,"tag":92,"props":236,"children":237},{},[238],{"type":48,"value":239},"ALWAYS use \"Region switch\" (lowercase 's') for the product name",{"type":42,"tag":92,"props":241,"children":242},{},[243],{"type":48,"value":244},"Use \"Routing Controls\" only when referring to the Routing Controls execution block or the legacy cluster-based approach — do not use it as a synonym for Region switch",{"type":42,"tag":92,"props":246,"children":247},{},[248,250,255,257,262],{"type":48,"value":249},"Do NOT conflate ",{"type":42,"tag":64,"props":251,"children":252},{},[253],{"type":48,"value":254},"triggers",{"type":48,"value":256}," (CloudWatch alarms that start execution) with ",{"type":42,"tag":64,"props":258,"children":259},{},[260],{"type":48,"value":261},"application health alarms",{"type":48,"value":263}," (measure actual recovery time)",{"type":42,"tag":92,"props":265,"children":266},{},[267],{"type":48,"value":268},"Region switch orchestrates failover — it does NOT replicate data",{"type":42,"tag":51,"props":270,"children":272},{"id":271},"critical-warnings",[273],{"type":48,"value":274},"Critical Warnings",{"type":42,"tag":88,"props":276,"children":277},{},[278,288,298],{"type":42,"tag":92,"props":279,"children":280},{},[281,286],{"type":42,"tag":64,"props":282,"children":283},{},[284],{"type":48,"value":285},"Irreversible in-progress steps",{"type":48,"value":287},": Plan executions can be paused or cancelled, but any step that is already started cannot be reversed without another plan execution.",{"type":42,"tag":92,"props":289,"children":290},{},[291,296],{"type":42,"tag":64,"props":292,"children":293},{},[294],{"type":48,"value":295},"Monitor during events",{"type":48,"value":297},": Customers should still monitor their application health during an event, even if they configure plan triggers to automatically start a plan execution.",{"type":42,"tag":92,"props":299,"children":300},{},[301,306,308,314,316,325],{"type":42,"tag":64,"props":302,"children":303},{},[304],{"type":48,"value":305},"Regional endpoint matters",{"type":48,"value":307},": When deactivating a Region, call ",{"type":42,"tag":101,"props":309,"children":311},{"className":310},[],[312],{"type":48,"value":313},"start-plan-execution",{"type":48,"value":315}," from the healthy Region, not the Region being deactivated. When activating a Region, call from the Region being activated. See ",{"type":42,"tag":317,"props":318,"children":322},"a",{"href":319,"rel":320},"https:\u002F\u002Fdocs.aws.amazon.com\u002Farc-region-switch\u002Flatest\u002Fapi\u002FAPI_StartPlanExecution.html",[321],"nofollow",[323],{"type":48,"value":324},"StartPlanExecution API",{"type":48,"value":186},{"type":42,"tag":51,"props":327,"children":329},{"id":328},"workflow",[330],{"type":48,"value":331},"Workflow",{"type":42,"tag":333,"props":334,"children":335},"ol",{},[336,341,346,359],{"type":42,"tag":92,"props":337,"children":338},{},[339],{"type":48,"value":340},"Classify the question: technical architecture, customer positioning, how-to, troubleshooting, or comparison",{"type":42,"tag":92,"props":342,"children":343},{},[344],{"type":48,"value":345},"Answer from embedded knowledge in this skill",{"type":42,"tag":92,"props":347,"children":348},{},[349,351,357],{"type":48,"value":350},"If the knowledge base is insufficient, search official AWS documentation (",{"type":42,"tag":101,"props":352,"children":354},{"className":353},[],[355],{"type":48,"value":356},"docs.aws.amazon.com",{"type":48,"value":358},")",{"type":42,"tag":92,"props":360,"children":361},{},[362],{"type":48,"value":363},"Format the response for the audience (engineer, SA, customer)",{"type":42,"tag":58,"props":365,"children":366},{},[367],{"type":48,"value":368},"Always validate:",{"type":42,"tag":88,"props":370,"children":371},{},[372,377,382],{"type":42,"tag":92,"props":373,"children":374},{},[375],{"type":48,"value":376},"Correct terminology (Region switch, not routing controls for plan-based features)",{"type":42,"tag":92,"props":378,"children":379},{},[380],{"type":48,"value":381},"Include doc links where helpful (see Documentation Links section)",{"type":42,"tag":92,"props":383,"children":384},{},[385],{"type":48,"value":386},"Use positioning language from the Positioning section",{"type":42,"tag":51,"props":388,"children":389},{"id":18},[390],{"type":48,"value":17},{"type":42,"tag":392,"props":393,"children":395},"h3",{"id":394},"components",[396],{"type":48,"value":397},"Components",{"type":42,"tag":399,"props":400,"children":401},"table",{},[402,421],{"type":42,"tag":403,"props":404,"children":405},"thead",{},[406],{"type":42,"tag":407,"props":408,"children":409},"tr",{},[410,416],{"type":42,"tag":411,"props":412,"children":413},"th",{},[414],{"type":48,"value":415},"Component",{"type":42,"tag":411,"props":417,"children":418},{},[419],{"type":48,"value":420},"Description",{"type":42,"tag":422,"props":423,"children":424},"tbody",{},[425,442,458,473,489,505,521,537,553,569],{"type":42,"tag":407,"props":426,"children":427},{},[428,437],{"type":42,"tag":429,"props":430,"children":431},"td",{},[432],{"type":42,"tag":64,"props":433,"children":434},{},[435],{"type":48,"value":436},"Plan",{"type":42,"tag":429,"props":438,"children":439},{},[440],{"type":48,"value":441},"Top-level resource scoped to a multi-Region application. Contains workflows.",{"type":42,"tag":407,"props":443,"children":444},{},[445,453],{"type":42,"tag":429,"props":446,"children":447},{},[448],{"type":42,"tag":64,"props":449,"children":450},{},[451],{"type":48,"value":452},"Child Plan",{"type":42,"tag":429,"props":454,"children":455},{},[456],{"type":48,"value":457},"A self-contained plan nested within a parent plan (one level deep).",{"type":42,"tag":407,"props":459,"children":460},{},[461,468],{"type":42,"tag":429,"props":462,"children":463},{},[464],{"type":42,"tag":64,"props":465,"children":466},{},[467],{"type":48,"value":331},{"type":42,"tag":429,"props":469,"children":470},{},[471],{"type":48,"value":472},"Ordered sequence of steps within a plan. Defines activation\u002Fdeactivation logic.",{"type":42,"tag":407,"props":474,"children":475},{},[476,484],{"type":42,"tag":429,"props":477,"children":478},{},[479],{"type":42,"tag":64,"props":480,"children":481},{},[482],{"type":48,"value":483},"Step",{"type":42,"tag":429,"props":485,"children":486},{},[487],{"type":48,"value":488},"Container for one or more execution blocks, run in parallel or sequence.",{"type":42,"tag":407,"props":490,"children":491},{},[492,500],{"type":42,"tag":429,"props":493,"children":494},{},[495],{"type":42,"tag":64,"props":496,"children":497},{},[498],{"type":48,"value":499},"Execution Block",{"type":42,"tag":429,"props":501,"children":502},{},[503],{"type":48,"value":504},"Performs a specific recovery action (e.g., scale up, reroute traffic, failover DB).",{"type":42,"tag":407,"props":506,"children":507},{},[508,516],{"type":42,"tag":429,"props":509,"children":510},{},[511],{"type":42,"tag":64,"props":512,"children":513},{},[514],{"type":48,"value":515},"Trigger",{"type":42,"tag":429,"props":517,"children":518},{},[519],{"type":48,"value":520},"CloudWatch alarm-based automation that initiates plan execution.",{"type":42,"tag":407,"props":522,"children":523},{},[524,532],{"type":42,"tag":429,"props":525,"children":526},{},[527],{"type":42,"tag":64,"props":528,"children":529},{},[530],{"type":48,"value":531},"Application Health Alarms",{"type":42,"tag":429,"props":533,"children":534},{},[535],{"type":48,"value":536},"CloudWatch alarms indicating app health per Region; used to calculate actual recovery time.",{"type":42,"tag":407,"props":538,"children":539},{},[540,548],{"type":42,"tag":429,"props":541,"children":542},{},[543],{"type":42,"tag":64,"props":544,"children":545},{},[546],{"type":48,"value":547},"Post-recovery Workflow",{"type":42,"tag":429,"props":549,"children":550},{},[551],{"type":48,"value":552},"Optional workflow that runs after recovery to prepare for future events.",{"type":42,"tag":407,"props":554,"children":555},{},[556,564],{"type":42,"tag":429,"props":557,"children":558},{},[559],{"type":42,"tag":64,"props":560,"children":561},{},[562],{"type":48,"value":563},"Plan Evaluation",{"type":42,"tag":429,"props":565,"children":566},{},[567],{"type":48,"value":568},"Automated checks verifying plan execution readiness. Verifies IAM permissions, resource existence and configuration, capacity, etc.",{"type":42,"tag":407,"props":570,"children":571},{},[572,580],{"type":42,"tag":429,"props":573,"children":574},{},[575],{"type":42,"tag":64,"props":576,"children":577},{},[578],{"type":48,"value":579},"Automatic Execution Reports",{"type":42,"tag":429,"props":581,"children":582},{},[583],{"type":48,"value":584},"PDF reports delivered to S3 after each plan execution for compliance\u002Faudit.",{"type":42,"tag":392,"props":586,"children":588},{"id":587},"execution-modes",[589],{"type":48,"value":590},"Execution Modes",{"type":42,"tag":58,"props":592,"children":593},{},[594],{"type":48,"value":595},"Recommend using graceful execution unless not possible (e.g., when an execution block has a dependency on the impaired Region — such as Aurora\u002FDocumentDB\u002FNeptune switchover requiring connectivity to the impaired Region, or a Custom Action Lambda deployed in the impaired Region).",{"type":42,"tag":88,"props":597,"children":598},{},[599,609,619],{"type":42,"tag":92,"props":600,"children":601},{},[602,607],{"type":42,"tag":64,"props":603,"children":604},{},[605],{"type":48,"value":606},"Graceful",{"type":48,"value":608},": Runs all steps in orderly sequence. Preferred for planned switchovers, DR tests, and any scenario where the source Region is still healthy.",{"type":42,"tag":92,"props":610,"children":611},{},[612,617],{"type":42,"tag":64,"props":613,"children":614},{},[615],{"type":48,"value":616},"Ungraceful",{"type":48,"value":618},": Skips or modifies certain execution blocks — only critical steps run. Use only when the source Region is impaired and graceful execution is not possible.",{"type":42,"tag":92,"props":620,"children":621},{},[622,627,629,636],{"type":42,"tag":64,"props":623,"children":624},{},[625],{"type":48,"value":626},"Post-recovery",{"type":48,"value":628},": Runs after successful recovery in the previously-impaired Region. Requires both Regions to be healthy. Supports a subset of execution blocks — see the ",{"type":42,"tag":317,"props":630,"children":633},{"href":631,"rel":632},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Fworking-with-rs-execution-blocks.html",[321],[634],{"type":48,"value":635},"Add execution blocks",{"type":48,"value":637}," documentation for the current set.",{"type":42,"tag":392,"props":639,"children":641},{"id":640},"activepassive-vs-activeactive",[642],{"type":48,"value":643},"Active\u002FPassive vs Active\u002FActive",{"type":42,"tag":399,"props":645,"children":646},{},[647,668],{"type":42,"tag":403,"props":648,"children":649},{},[650],{"type":42,"tag":407,"props":651,"children":652},{},[653,658,663],{"type":42,"tag":411,"props":654,"children":655},{},[656],{"type":48,"value":657},"Approach",{"type":42,"tag":411,"props":659,"children":660},{},[661],{"type":48,"value":662},"Workflows Needed",{"type":42,"tag":411,"props":664,"children":665},{},[666],{"type":48,"value":667},"Behavior",{"type":42,"tag":422,"props":669,"children":670},{},[671,692],{"type":42,"tag":407,"props":672,"children":673},{},[674,682,687],{"type":42,"tag":429,"props":675,"children":676},{},[677],{"type":42,"tag":64,"props":678,"children":679},{},[680],{"type":48,"value":681},"Active\u002FPassive",{"type":42,"tag":429,"props":683,"children":684},{},[685],{"type":48,"value":686},"1 activation workflow (either Region) OR 2 separate activation workflows (one per Region)",{"type":42,"tag":429,"props":688,"children":689},{},[690],{"type":48,"value":691},"Failover from primary to standby; failback when primary recovers",{"type":42,"tag":407,"props":693,"children":694},{},[695,703,708],{"type":42,"tag":429,"props":696,"children":697},{},[698],{"type":42,"tag":64,"props":699,"children":700},{},[701],{"type":48,"value":702},"Active\u002FActive",{"type":42,"tag":429,"props":704,"children":705},{},[706],{"type":48,"value":707},"1 activation workflow + 1 deactivation workflow per Region",{"type":42,"tag":429,"props":709,"children":710},{},[711],{"type":48,"value":712},"Shift-away from impaired Region + return when healthy",{"type":42,"tag":392,"props":714,"children":716},{"id":715},"supported-execution-blocks",[717],{"type":48,"value":718},"Supported Execution Blocks",{"type":42,"tag":58,"props":720,"children":721},{},[722],{"type":48,"value":723},"Execution blocks are the individual step types a Region switch workflow is composed of — each performs one recovery action, spanning traffic\u002FDNS rerouting, compute scaling, database failover, custom-action Lambdas, manual-approval gates, and nested child plans.",{"type":42,"tag":58,"props":725,"children":726},{},[727,732,734,741,743,748],{"type":42,"tag":64,"props":728,"children":729},{},[730],{"type":48,"value":731},"Do not rely on a hardcoded list of block types",{"type":48,"value":733}," — ARC adds and changes execution blocks over time. Retrieve the current supported set at query time from the ",{"type":42,"tag":317,"props":735,"children":738},{"href":736,"rel":737},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Fcomponents-rs.html",[321],[739],{"type":48,"value":740},"Components & concepts",{"type":48,"value":742}," and ",{"type":42,"tag":317,"props":744,"children":746},{"href":631,"rel":745},[321],[747],{"type":48,"value":635},{"type":48,"value":749}," documentation.",{"type":42,"tag":392,"props":751,"children":753},{"id":752},"recovery-time-tracking",[754],{"type":48,"value":755},"Recovery Time Tracking",{"type":42,"tag":88,"props":757,"children":758},{},[759,769,779],{"type":42,"tag":92,"props":760,"children":761},{},[762,767],{"type":42,"tag":64,"props":763,"children":764},{},[765],{"type":48,"value":766},"Recovery Time Objective (RTO)",{"type":48,"value":768},": Set when creating a plan",{"type":42,"tag":92,"props":770,"children":771},{},[772,777],{"type":42,"tag":64,"props":773,"children":774},{},[775],{"type":48,"value":776},"Actual Recovery Time",{"type":48,"value":778},": Plan execution time + time for application health alarms to return to green",{"type":42,"tag":92,"props":780,"children":781},{},[782],{"type":48,"value":783},"Visible on plan execution details page for comparison against RTO",{"type":42,"tag":392,"props":785,"children":787},{"id":786},"plan-evaluation",[788],{"type":48,"value":563},{"type":42,"tag":88,"props":790,"children":791},{},[792,797,802],{"type":42,"tag":92,"props":793,"children":794},{},[795],{"type":48,"value":796},"Validates: IAM permissions, resource configurations, running capacity",{"type":42,"tag":92,"props":798,"children":799},{},[800],{"type":48,"value":801},"Warnings surfaced in console, EventBridge, and API",{"type":42,"tag":92,"props":803,"children":804},{},[805],{"type":48,"value":806},"Passing evaluation alone is NOT sufficient — always test by executing plans",{"type":42,"tag":392,"props":808,"children":810},{"id":809},"automatic-execution-reports",[811],{"type":48,"value":579},{"type":42,"tag":88,"props":813,"children":814},{},[815,820,825,830,835,840],{"type":42,"tag":92,"props":816,"children":817},{},[818],{"type":48,"value":819},"PDF reports generated after each plan execution",{"type":42,"tag":92,"props":821,"children":822},{},[823],{"type":48,"value":824},"Delivered to customer-specified S3 bucket (within ~30 min)",{"type":42,"tag":92,"props":826,"children":827},{},[828],{"type":48,"value":829},"Customers must configure the S3 bucket and update permissions for the PlanExecutionRole to enable reporting",{"type":42,"tag":92,"props":831,"children":832},{},[833],{"type":48,"value":834},"Contents: executive summary, plan config, execution timeline, resource states, alarm history, child plan details, glossary",{"type":42,"tag":92,"props":836,"children":837},{},[838],{"type":48,"value":839},"Useful for regulatory compliance and DR audit evidence",{"type":42,"tag":92,"props":841,"children":842},{},[843],{"type":48,"value":844},"See Security Considerations for encryption and access control guidance",{"type":42,"tag":51,"props":846,"children":848},{"id":847},"cross-account-support",[849],{"type":48,"value":850},"Cross-Account Support",{"type":42,"tag":58,"props":852,"children":853},{},[854],{"type":48,"value":855},"Plans can orchestrate resources across multiple AWS accounts via IAM roles with cross-account trust policies. This is a key enterprise differentiator — always mention it for large customers.",{"type":42,"tag":58,"props":857,"children":858},{},[859],{"type":48,"value":860},"When configuring cross-account trust policies:",{"type":42,"tag":88,"props":862,"children":863},{},[864,892,913],{"type":42,"tag":92,"props":865,"children":866},{},[867,869,875,877,883,884,890],{"type":48,"value":868},"Include condition keys (",{"type":42,"tag":101,"props":870,"children":872},{"className":871},[],[873],{"type":48,"value":874},"aws:SourceArn",{"type":48,"value":876},", ",{"type":42,"tag":101,"props":878,"children":880},{"className":879},[],[881],{"type":48,"value":882},"aws:SourceAccount",{"type":48,"value":876},{"type":42,"tag":101,"props":885,"children":887},{"className":886},[],[888],{"type":48,"value":889},"sts:ExternalId",{"type":48,"value":891},") to prevent confused deputy attacks",{"type":42,"tag":92,"props":893,"children":894},{},[895,897,903,905,911],{"type":48,"value":896},"Scope IAM policies to least privilege — avoid ",{"type":42,"tag":101,"props":898,"children":900},{"className":899},[],[901],{"type":48,"value":902},"*",{"type":48,"value":904}," resource wildcards and ",{"type":42,"tag":101,"props":906,"children":908},{"className":907},[],[909],{"type":48,"value":910},"FullAccess",{"type":48,"value":912}," managed policies",{"type":42,"tag":92,"props":914,"children":915},{},[916],{"type":48,"value":917},"Scope permissions to only the specific resources (ASG ARNs, Aurora cluster ARNs, Route 53 health check ARNs, etc.) referenced in execution blocks",{"type":42,"tag":51,"props":919,"children":921},{"id":920},"regional-availability",[922],{"type":48,"value":923},"Regional Availability",{"type":42,"tag":58,"props":925,"children":926},{},[927,929,935],{"type":48,"value":928},"Available in multiple commercial AWS Regions and AWS GovCloud (US) Regions — always verify the current list before stating availability to a customer, as Region coverage changes over time. Each Region has its own data-plane endpoint (",{"type":42,"tag":101,"props":930,"children":932},{"className":931},[],[933],{"type":48,"value":934},"arc-region-switch.\u003Cregion>.api.aws",{"type":48,"value":936},"), ensuring execution doesn't depend on the impaired Region.",{"type":42,"tag":938,"props":939,"children":940},"blockquote",{},[941],{"type":42,"tag":58,"props":942,"children":943},{},[944,946,953],{"type":48,"value":945},"Verify the complete list of available regions\u002Fendpoints at ",{"type":42,"tag":317,"props":947,"children":950},{"href":948,"rel":949},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Faws-regions-rs.html",[321],[951],{"type":48,"value":952},"AWS Regions & endpoints",{"type":48,"value":186},{"type":42,"tag":51,"props":955,"children":957},{"id":956},"security-considerations",[958],{"type":48,"value":959},"Security Considerations",{"type":42,"tag":392,"props":961,"children":963},{"id":962},"iam-least-privilege",[964],{"type":48,"value":965},"IAM Least Privilege",{"type":42,"tag":88,"props":967,"children":968},{},[969,974,991],{"type":42,"tag":92,"props":970,"children":971},{},[972],{"type":48,"value":973},"Scope cross-account IAM roles to only the specific resources referenced in execution blocks (ASG ARNs, Aurora cluster ARNs, Route 53 health check ARNs, Lambda function ARNs, etc.)",{"type":42,"tag":92,"props":975,"children":976},{},[977,979,984,985,990],{"type":48,"value":978},"Avoid ",{"type":42,"tag":101,"props":980,"children":982},{"className":981},[],[983],{"type":48,"value":902},{"type":48,"value":904},{"type":42,"tag":101,"props":986,"children":988},{"className":987},[],[989],{"type":48,"value":910},{"type":48,"value":912},{"type":42,"tag":92,"props":992,"children":993},{},[994,995,1000,1001,1006,1007,1012],{"type":48,"value":868},{"type":42,"tag":101,"props":996,"children":998},{"className":997},[],[999],{"type":48,"value":874},{"type":48,"value":876},{"type":42,"tag":101,"props":1002,"children":1004},{"className":1003},[],[1005],{"type":48,"value":882},{"type":48,"value":876},{"type":42,"tag":101,"props":1008,"children":1010},{"className":1009},[],[1011],{"type":48,"value":889},{"type":48,"value":1013},") in cross-account trust policies to prevent confused deputy attacks",{"type":42,"tag":392,"props":1015,"children":1017},{"id":1016},"execution-reports-s3-bucket",[1018],{"type":48,"value":1019},"Execution Reports S3 Bucket",{"type":42,"tag":88,"props":1021,"children":1022},{},[1023,1028,1049,1054,1059],{"type":42,"tag":92,"props":1024,"children":1025},{},[1026],{"type":48,"value":1027},"Enable default encryption (SSE-KMS preferred) on the reports S3 bucket",{"type":42,"tag":92,"props":1029,"children":1030},{},[1031,1033,1039,1041,1047],{"type":48,"value":1032},"Add a bucket policy denying requests where ",{"type":42,"tag":101,"props":1034,"children":1036},{"className":1035},[],[1037],{"type":48,"value":1038},"aws:SecureTransport",{"type":48,"value":1040}," is ",{"type":42,"tag":101,"props":1042,"children":1044},{"className":1043},[],[1045],{"type":48,"value":1046},"false",{"type":48,"value":1048}," (enforce TLS)",{"type":42,"tag":92,"props":1050,"children":1051},{},[1052],{"type":48,"value":1053},"Restrict bucket access to authorized personnel only — reports contain sensitive infrastructure details (plan config, execution timeline, resource states, alarm history)",{"type":42,"tag":92,"props":1055,"children":1056},{},[1057],{"type":48,"value":1058},"Enable S3 bucket versioning and MFA Delete for tamper protection",{"type":42,"tag":92,"props":1060,"children":1061},{},[1062],{"type":48,"value":1063},"Ensure the bucket is not publicly accessible",{"type":42,"tag":392,"props":1065,"children":1067},{"id":1066},"custom-action-lambda-security",[1068],{"type":48,"value":1069},"Custom Action Lambda Security",{"type":42,"tag":88,"props":1071,"children":1072},{},[1073,1078,1083],{"type":42,"tag":92,"props":1074,"children":1075},{},[1076],{"type":48,"value":1077},"Apply least-privilege execution roles to Custom Action Lambda functions",{"type":42,"tag":92,"props":1079,"children":1080},{},[1081],{"type":48,"value":1082},"Validate inputs within Lambda functions",{"type":42,"tag":92,"props":1084,"children":1085},{},[1086],{"type":48,"value":1087},"Do not embed secrets in Lambda environment variables — use Secrets Manager or Parameter Store",{"type":42,"tag":392,"props":1089,"children":1091},{"id":1090},"notification-event-targets",[1092],{"type":48,"value":1093},"Notification & Event Targets",{"type":42,"tag":88,"props":1095,"children":1096},{},[1097,1102],{"type":42,"tag":92,"props":1098,"children":1099},{},[1100],{"type":48,"value":1101},"Restrict EventBridge rule targets (SNS topics, Lambda functions, etc.) that receive plan-evaluation warnings and execution events to authorized recipients only",{"type":42,"tag":92,"props":1103,"children":1104},{},[1105],{"type":48,"value":1106},"Lock down SNS topic subscription policies and Lambda resource policies so sensitive infrastructure details (plan configuration, resource ARNs, execution state) are not exposed to unauthorized parties",{"type":42,"tag":392,"props":1108,"children":1110},{"id":1109},"logging-and-monitoring",[1111],{"type":48,"value":1112},"Logging and Monitoring",{"type":42,"tag":88,"props":1114,"children":1115},{},[1116,1121,1126,1131],{"type":42,"tag":92,"props":1117,"children":1118},{},[1119],{"type":48,"value":1120},"Enable AWS CloudTrail for auditing all ARC Region switch API calls",{"type":42,"tag":92,"props":1122,"children":1123},{},[1124],{"type":48,"value":1125},"Configure CloudWatch alarms for unexpected or unauthorized plan executions",{"type":42,"tag":92,"props":1127,"children":1128},{},[1129],{"type":48,"value":1130},"Enable S3 access logging on the execution reports bucket",{"type":42,"tag":92,"props":1132,"children":1133},{},[1134,1136],{"type":48,"value":1135},"See ",{"type":42,"tag":317,"props":1137,"children":1140},{"href":1138,"rel":1139},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fr53recovery\u002Flatest\u002Fdg\u002Flogging-and-monitoring-rs.html",[321],[1141],{"type":48,"value":1142},"Logging and monitoring for Region switch",{"type":42,"tag":51,"props":1144,"children":1146},{"id":1145},"positioning",[1147],{"type":48,"value":1148},"Positioning",{"type":42,"tag":58,"props":1150,"children":1151},{},[1152,1154,1162],{"type":48,"value":1153},"Customer-facing framing, the Region switch vs Routing Controls comparison, analyst talking\npoints, and per-audience conversation guidance are maintained in\n",{"type":42,"tag":64,"props":1155,"children":1156},{},[1157],{"type":42,"tag":317,"props":1158,"children":1160},{"href":1159},"references\u002Fpositioning.md",[1161],{"type":48,"value":1148},{"type":48,"value":1163},". Load that reference for any customer-positioning,\ncompetitive-comparison, or analyst-briefing question. Key rules that always apply:",{"type":42,"tag":88,"props":1165,"children":1166},{},[1167,1172],{"type":42,"tag":92,"props":1168,"children":1169},{},[1170],{"type":48,"value":1171},"Use \"Region switch\" (plan-based orchestration) framing; do NOT present legacy \"routing controls\"\n\u002F \"ARC clusters\" language as the Region switch (plan-based) approach.",{"type":42,"tag":92,"props":1173,"children":1174},{},[1175,1177,1182,1184,1189],{"type":48,"value":1176},"Always mention ",{"type":42,"tag":64,"props":1178,"children":1179},{},[1180],{"type":48,"value":1181},"cross-account",{"type":48,"value":1183}," support and ",{"type":42,"tag":64,"props":1185,"children":1186},{},[1187],{"type":48,"value":1188},"data-plane-per-Region",{"type":48,"value":1190}," isolation for enterprise customers.",{"type":42,"tag":51,"props":1192,"children":1194},{"id":1193},"documentation-links",[1195],{"type":48,"value":1196},"Documentation Links",{"type":42,"tag":58,"props":1198,"children":1199},{},[1200,1202,1210],{"type":48,"value":1201},"The curated documentation index and the \"when to link which doc\" guidance live in\n",{"type":42,"tag":64,"props":1203,"children":1204},{},[1205],{"type":42,"tag":317,"props":1206,"children":1208},{"href":1207},"references\u002Fdoc-links.md",[1209],{"type":48,"value":1196},{"type":48,"value":1211},". Load that reference to attach the right AWS\ndoc to an answer (overview, components & concepts, execution blocks, API\u002FCLI, security & IAM,\nlogging & monitoring, quotas, Terraform provider).",{"type":42,"tag":51,"props":1213,"children":1215},{"id":1214},"troubleshooting",[1216],{"type":48,"value":1217},"Troubleshooting",{"type":42,"tag":392,"props":1219,"children":1221},{"id":1220},"customer-confuses-triggers-with-health-alarms",[1222],{"type":48,"value":1223},"Customer confuses triggers with health alarms",{"type":42,"tag":58,"props":1225,"children":1226},{},[1227,1229,1234,1236,1241],{"type":48,"value":1228},"Triggers are CloudWatch alarms that ",{"type":42,"tag":64,"props":1230,"children":1231},{},[1232],{"type":48,"value":1233},"start",{"type":48,"value":1235}," plan execution. Application health alarms ",{"type":42,"tag":64,"props":1237,"children":1238},{},[1239],{"type":48,"value":1240},"measure",{"type":48,"value":1242}," when recovery is complete. They serve different purposes and are configured separately.",{"type":42,"tag":392,"props":1244,"children":1246},{"id":1245},"customer-assumes-region-switch-handles-data-sync",[1247],{"type":48,"value":1248},"Customer assumes Region switch handles data sync",{"type":42,"tag":58,"props":1250,"children":1251},{},[1252],{"type":48,"value":1253},"Clarify: Region switch orchestrates failover of existing replicas (e.g., Aurora Global DB promotion). The customer must set up multi-Region data replication independently.",{"type":42,"tag":392,"props":1255,"children":1257},{"id":1256},"cross-account-execution-fails",[1258],{"type":48,"value":1259},"Cross-account execution fails",{"type":42,"tag":58,"props":1261,"children":1262},{},[1263,1265,1270,1271,1276,1277,1282],{"type":48,"value":1264},"Usually missing IAM permissions. Verify: cross-account trust policy includes condition keys (",{"type":42,"tag":101,"props":1266,"children":1268},{"className":1267},[],[1269],{"type":48,"value":874},{"type":48,"value":876},{"type":42,"tag":101,"props":1272,"children":1274},{"className":1273},[],[1275],{"type":48,"value":882},{"type":48,"value":876},{"type":42,"tag":101,"props":1278,"children":1280},{"className":1279},[],[1281],{"type":48,"value":889},{"type":48,"value":1283},"), target IAM role ARN is correct, and permissions are scoped to the specific resources in the execution blocks.",{"type":42,"tag":392,"props":1285,"children":1287},{"id":1286},"plan-evaluation-warnings",[1288],{"type":48,"value":1289},"Plan evaluation warnings",{"type":42,"tag":58,"props":1291,"children":1292},{},[1293],{"type":48,"value":1294},"Warnings indicate IAM, resource, or capacity issues. Fix the underlying issue — but note that passing evaluation alone isn't sufficient; always test by executing plans.",{"type":42,"tag":392,"props":1296,"children":1298},{"id":1297},"wrong-regional-endpoint-used",[1299],{"type":48,"value":1300},"Wrong Regional endpoint used",{"type":42,"tag":58,"props":1302,"children":1303},{},[1304,1306,1311,1313,1318],{"type":48,"value":1305},"When deactivating a Region, ",{"type":42,"tag":101,"props":1307,"children":1309},{"className":1308},[],[1310],{"type":48,"value":313},{"type":48,"value":1312}," MUST be called from the healthy Region. When activating a Region, it MUST be called from the Region being activated. Using the wrong endpoint will fail or produce unexpected behavior. See ",{"type":42,"tag":317,"props":1314,"children":1316},{"href":319,"rel":1315},[321],[1317],{"type":48,"value":324},{"type":48,"value":186},{"items":1320,"total":1424},[1321,1338,1353,1368,1383,1393,1408],{"slug":1322,"name":1322,"fn":1323,"description":1324,"org":1325,"tags":1326,"stars":24,"repoUrl":25,"updatedAt":1337},"agents-build","add capabilities to existing agent projects","Use when adding capabilities to an existing agent project — memory, app integration, VPC, multi-agent, migration, model changes, browser, code interpreter, or resource removal. Triggers on: \"add memory\", \"remember across sessions\", \"call agent from app\", \"invoke agent from code\", \"auth to call agent\", \"streaming responses\", \"VPC\", \"VPC connectivity\", \"VPC error\", \"can't reach from VPC\", \"multi-agent\", \"A2A\", \"A2A auth\", \"orchestrator not delegating\", \"specialist not called\", \"migrate Bedrock Agent\", \"after import\", \"migration issue\", \"framework for migration\", \"change model\", \"browser tool\", \"code interpreter\", \"delete agent\", \"tear down\", \"agentcore remove\", \"cross-account memory\", \"resource-based policy on memory\", \"pay for x402 content\", \"402 Payment Required\", \"microtransactions\", \"paid API or tool\". Not for connecting to external APIs via Gateway — use agents-connect. Not for scaffolding a new project — use agents-get-started. Not for CLI\u002Fdev server errors — use agents-debug. Strands vs LangGraph in a migration context routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1327,1330,1333,1334],{"name":1328,"slug":1329,"type":15},"Agents","agents",{"name":1331,"slug":1332,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":1335,"slug":1336,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":1339,"name":1339,"fn":1340,"description":1341,"org":1342,"tags":1343,"stars":24,"repoUrl":25,"updatedAt":1352},"agents-connect","connect agents to external services","Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: \"connect to API\", \"add gateway\", \"connect to MCP server\", \"Lambda tools\", \"OpenAPI\", \"gateway target\", \"Cedar policy\", \"restrict tools\", \"policy engine\", \"gateway auth error\", \"store API key\", \"outbound credential\", \"env var API key\", \"API key None after deploy\", \"credential not available after deploy\", \"should this be a gateway target\", \"give my agent tools\", \"add tools to agent\". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1344,1345,1348,1351],{"name":1328,"slug":1329,"type":15},{"name":1346,"slug":1347,"type":15},"API Development","api-development",{"name":1349,"slug":1350,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":1354,"name":1354,"fn":1355,"description":1356,"org":1357,"tags":1358,"stars":24,"repoUrl":25,"updatedAt":1367},"agents-debug","debug agent and environment issues","Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: \"agent not working\", \"wrong answer\", \"agent error\", \"tool call failing\", \"debug agent\", \"check logs\", \"read traces\", \"broken\", \"500 error\", \"424 error\", \"model access denied\", \"command not found\", \"stuck in DELETING\", \"maxVms exceeded\", \"cold start diagnosis\", \"cold start slow\", \"agentcore create error\", \"create failed\", \"exit code 7\", \"connection refused local dev\". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1359,1360,1361,1364],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1362,"slug":1363,"type":15},"Debugging","debugging",{"name":1365,"slug":1366,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":1369,"name":1369,"fn":1370,"description":1371,"org":1372,"tags":1373,"stars":24,"repoUrl":25,"updatedAt":1382},"agents-deploy","deploy AI agents to AWS","Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK\u002FIAM\u002Fquota error diagnosis, version management, rollback, and canary deployments. Triggers on: \"deploy my agent\", \"agentcore deploy\", \"deploy failed\", \"CDK error\", \"rollback\", \"canary deploy\", \"pin version\", \"redeploy\", \"deploy stuck\". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1374,1375,1376,1379],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1377,"slug":1378,"type":15},"CI\u002FCD","ci-cd",{"name":1380,"slug":1381,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":1384,"name":1384,"fn":1385,"description":1386,"org":1387,"tags":1388,"stars":24,"repoUrl":25,"updatedAt":1392},"agents-get-started","scaffold and deploy new agent projects","Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: \"build an agent\", \"create an agent\", \"get started\", \"new project\", \"agentcore create\", \"which framework\", \"Strands vs LangGraph\", \"hello world agent\", \"first agent\", \"create MCP server\", \"host MCP server\", \"agentcore dev\", \"dev server\", \"what port\", \"local development\". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1389,1390,1391],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1380,"slug":1381,"type":15},"2026-07-12T08:42:51.963247",{"slug":1394,"name":1394,"fn":1395,"description":1396,"org":1397,"tags":1398,"stars":24,"repoUrl":25,"updatedAt":1407},"agents-harden","harden agents for production","Use when preparing your agent for production — IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: \"production checklist\", \"harden agent\", \"production ready\", \"secure agent\", \"inbound auth\", \"going live\", \"cold start optimization\", \"session lifecycle\", \"StopRuntimeSession\", \"quota\", \"throttling\", \"maxVms\", \"rate limit\", \"security audit of outbound API calls\", \"gateway target audit for production\", \"restrict who can call\", \"lock down endpoint\", \"only our app can call\". Not for Cedar tool-restriction policies — use agents-connect. Not for quality measurement — use agents-optimize. Not for outbound credential storage or API key wiring — use agents-connect. Not for A2A agent-to-agent auth — use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1399,1400,1401,1404],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1402,"slug":1403,"type":15},"Best Practices","best-practices",{"name":1405,"slug":1406,"type":15},"Security","security","2026-07-16T06:00:42.174705",{"slug":1409,"name":1409,"fn":1410,"description":1411,"org":1412,"tags":1413,"stars":24,"repoUrl":25,"updatedAt":1423},"agents-optimize","optimize agent quality and performance","Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI\u002FCD quality gates, observability, or cost optimization. Triggers on: \"evaluate my agent\", \"add evaluator\", \"measure quality\", \"quality gate\", \"run evals\", \"agent too slow\", \"why is it slow\", \"reduce latency\", \"set up observability\", \"CloudWatch dashboard\", \"how much does my agent cost\", \"cost optimization\", \"logs not showing up\", \"logs missing\", \"spans not found\", \"eval failing\", \"eval error\", \"dev traces\", \"local traces\", \"agentcore dev traces\", \"traces to CloudWatch\". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1414,1415,1416,1419,1420],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1417,"slug":1418,"type":15},"Evals","evals",{"name":1365,"slug":1366,"type":15},{"name":1421,"slug":1422,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",114,{"items":1426,"total":1543},[1427,1434,1441,1448,1455,1461,1468,1476,1493,1506,1518,1533],{"slug":1322,"name":1322,"fn":1323,"description":1324,"org":1428,"tags":1429,"stars":24,"repoUrl":25,"updatedAt":1337},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1430,1431,1432,1433],{"name":1328,"slug":1329,"type":15},{"name":1331,"slug":1332,"type":15},{"name":23,"slug":8,"type":15},{"name":1335,"slug":1336,"type":15},{"slug":1339,"name":1339,"fn":1340,"description":1341,"org":1435,"tags":1436,"stars":24,"repoUrl":25,"updatedAt":1352},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1437,1438,1439,1440],{"name":1328,"slug":1329,"type":15},{"name":1346,"slug":1347,"type":15},{"name":1349,"slug":1350,"type":15},{"name":23,"slug":8,"type":15},{"slug":1354,"name":1354,"fn":1355,"description":1356,"org":1442,"tags":1443,"stars":24,"repoUrl":25,"updatedAt":1367},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1444,1445,1446,1447],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1362,"slug":1363,"type":15},{"name":1365,"slug":1366,"type":15},{"slug":1369,"name":1369,"fn":1370,"description":1371,"org":1449,"tags":1450,"stars":24,"repoUrl":25,"updatedAt":1382},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1451,1452,1453,1454],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1377,"slug":1378,"type":15},{"name":1380,"slug":1381,"type":15},{"slug":1384,"name":1384,"fn":1385,"description":1386,"org":1456,"tags":1457,"stars":24,"repoUrl":25,"updatedAt":1392},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1458,1459,1460],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1380,"slug":1381,"type":15},{"slug":1394,"name":1394,"fn":1395,"description":1396,"org":1462,"tags":1463,"stars":24,"repoUrl":25,"updatedAt":1407},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1464,1465,1466,1467],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1402,"slug":1403,"type":15},{"name":1405,"slug":1406,"type":15},{"slug":1409,"name":1409,"fn":1410,"description":1411,"org":1469,"tags":1470,"stars":24,"repoUrl":25,"updatedAt":1423},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1471,1472,1473,1474,1475],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1417,"slug":1418,"type":15},{"name":1365,"slug":1366,"type":15},{"name":1421,"slug":1422,"type":15},{"slug":1477,"name":1477,"fn":1478,"description":1479,"org":1480,"tags":1481,"stars":24,"repoUrl":25,"updatedAt":1492},"amazon-aurora-mysql","manage Amazon Aurora MySQL clusters","Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1482,1483,1486,1489],{"name":23,"slug":8,"type":15},{"name":1484,"slug":1485,"type":15},"Database","database",{"name":1487,"slug":1488,"type":15},"MySQL","mysql",{"name":1490,"slug":1491,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":1494,"name":1494,"fn":1495,"description":1496,"org":1497,"tags":1498,"stars":24,"repoUrl":25,"updatedAt":1505},"amazon-aurora-postgresql","configure Amazon Aurora PostgreSQL clusters","Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1499,1500,1501,1504],{"name":23,"slug":8,"type":15},{"name":1484,"slug":1485,"type":15},{"name":1502,"slug":1503,"type":15},"PostgreSQL","postgresql",{"name":1490,"slug":1491,"type":15},"2026-07-16T06:00:34.789624",{"slug":1507,"name":1507,"fn":1508,"description":1509,"org":1510,"tags":1511,"stars":24,"repoUrl":25,"updatedAt":1517},"amazon-bedrock","build generative AI apps with Amazon Bedrock","Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore. Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating\u002Fporting\u002Fconverting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). ALSO USE for prompt caching setup and debugging, quota health checks and throttling diagnosis, cost attribution and tracking, migrating between Claude model generations (4.5 to 4.6 to 4.7), chunking strategies, API selection (Converse vs InvokeModel), guardrail capabilities, and model selection. Also covers AgentCore Payments setup (x402, microtransactions, Payment Manager, Connector, Instrument, Coinbase CDP, Stripe Privy, 402 Payment Required, pay for content, paid endpoint, agent payments). NOT for custom model training, Rekognition, or Comprehend.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1512,1513,1514],{"name":1328,"slug":1329,"type":15},{"name":23,"slug":8,"type":15},{"name":1515,"slug":1516,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":1519,"name":1519,"fn":1520,"description":1521,"org":1522,"tags":1523,"stars":24,"repoUrl":25,"updatedAt":1532},"amazon-documentdb","manage Amazon DocumentDB clusters","Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS\u002FVPC\u002Fdriver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0), Well-Architected reviews (41-check wa_review.py), cost estimation, and security hardening. Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS — DocumentDB is AWS's MongoDB-compatible managed database. Triggers: JSON document store, document database, MongoDB on AWS, Nested fields, Lambda cannot connect, TLS handshake, VPC port 27017, IAM auth, Secrets Manager, encryption at rest, $graphLookup, flexible schema, COLLSCAN, compound index, DMS migration, CDC cutover, $vectorSearch, RAG, Global Clusters, DR replication, cost sizing, audit, health check, production-readiness.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1524,1525,1526,1529],{"name":23,"slug":8,"type":15},{"name":1484,"slug":1485,"type":15},{"name":1527,"slug":1528,"type":15},"MongoDB","mongodb",{"name":1530,"slug":1531,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":1534,"name":1534,"fn":1535,"description":1536,"org":1537,"tags":1538,"stars":24,"repoUrl":25,"updatedAt":1542},"amazon-dynamodb","design and debug DynamoDB data layers","Designs, reviews, and debugs DynamoDB data layers from design axioms — enumerates access patterns, chooses partition\u002Fsort keys and GSIs, decides single-table vs. multi-table, configures Streams, Global Tables, TTL, and zero-ETL integrations to OpenSearch\u002FRedshift\u002FSageMaker Lakehouse, and produces a defensible data-layer design with a monthly cost estimate and optional live validation. Applies whenever a user is designing, reviewing, or refactoring anything backed by DynamoDB — schemas, access patterns, GSIs, single- vs. multi-table choices, Streams consumers, transactional outboxes, Global Tables, zero-ETL pipelines — even when they don't say \"axioms\" or \"design review.\" Also applies when debugging hot partitions, throttling, unbounded Scans, LWW conflicts, or surprise bills on DynamoDB workloads.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1539,1540,1541],{"name":23,"slug":8,"type":15},{"name":1484,"slug":1485,"type":15},{"name":1530,"slug":1531,"type":15},"2026-07-16T06:00:37.690386",115]