[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-resilience-hub-multi-account":3,"mdc-mnu7hz-key":35,"related-repo-aws-resilience-hub-multi-account":694,"related-org-aws-resilience-hub-multi-account":800},{"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},"resilience-hub-multi-account","configure multi-account AWS Resilience Hub","Configures AWS Resilience Hub v2 for multi-account resilience management across an AWS Organization. Covers the per-service cross-account permission model, cross-account IAM roles, and centralized assessment from a single account. Applies when the user wants to set up org-wide resilience or assess workloads that span multiple AWS accounts.\n",{"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},"Configuration","configuration",{"name":20,"slug":21,"type":15},"Multi-Tenant","multi-tenant",{"name":23,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-25T05:56:24.555067",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\u002Fresilience-hub-multi-account","---\nname: resilience-hub-multi-account\ndescription: >\n  Configures AWS Resilience Hub v2 for multi-account resilience management across an AWS\n  Organization. Covers the per-service cross-account permission model, cross-account IAM\n  roles, and centralized assessment from a single account. Applies when the user wants to set\n  up org-wide resilience or assess workloads that span multiple AWS accounts.\nversion: 1\n---\n\n# Multi-Account Resilience Hub v2 Setup\n\n## Overview\n\nDomain expertise for configuring Resilience Hub v2 to assess services across multiple\nAWS accounts from a central account. All CLI commands in this skill use the **`aws resiliencehubv2`**\nnamespace — the Resilience Hub **v2** API surface — which is distinct from the legacy `aws resiliencehub`\n(v1) commands (the `service: [resiliencehub, ...]` metadata tags the service family, not the CLI namespace).\nResilience Hub v2 supports two complementary multi-account mechanisms: (1) an **AWS Organizations\nintegration** — the management account enables trusted access, creates the service-linked role, and\ndesignates a **delegated administrator** account for organization-wide policy management and visibility;\nand (2) the **per-service cross-account permission model** — an invoker role in the central account that\nassumes cross-account roles in member accounts for per-service resource discovery. This skill configures\n(2); the Organizations integration (1) is set up separately (management account + console — see below).\n\n> The AWS MCP server is recommended for executing this skill's AWS API calls, but it is not required — all operations also work with the AWS CLI directly.\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\u002Fmulti-account-procedure.md\"`) — do NOT `file_read` these paths locally or search the filesystem for them.\n- **Installed locally** (e.g. `.kiro\u002Fskills\u002Fresilience-hub-multi-account\u002F` or `~\u002F.claude\u002Fskills\u002Fresilience-hub-multi-account\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## How centralized multi-account assessment works\n\nTwo paths, used depending on your goal:\n\n> **Decision rule (read first):** To **run cross-account resilience assessments** — i.e. assess workloads\u002Fresources that live in member accounts from a central account (the common request, including phrasings like *\"centralized resilience management across my Organization\"* or *\"central assessment account\"*) — use the **per-service cross-account permission model** (path 2 below): an invoker role + cross-account roles + `create-service --permission-model`. **Do NOT use or recommend `aws organizations register-delegated-administrator` (or any delegated-administrator registration) as the setup step for cross-account assessments.** The Organizations delegated-administrator integration (path 1) is a *separate, optional* feature scoped to organization-wide **policy management and visibility only** — it is not how you set up or run cross-account assessments. Only follow path 1 when the request is explicitly about org-wide policy governance, not assessment.\n\n- **Organization-wide governance** (centralized policies, cross-account visibility): use the **AWS\n  Organizations integration**. From the **management account**, enable trusted access for Resilience Hub,\n  create the service-linked role, and **register a delegated administrator** account. This is done via\n  Organizations trusted access + the Resilience Hub console — there is **no `resiliencehubv2`\n  `register-delegated-administrator` CLI operation**. The delegated administrator then selects a home\n  Region where organization-level data is aggregated. See the AWS docs page *Setting up Organizations\n  integration*.\n- **Per-service cross-account resource discovery** (assessing a service whose resources span accounts):\n  register each service with a **per-service cross-account permission model** — an invoker role in the\n  central account plus cross-account role ARNs for each member account. **This skill's steps configure\n  this path.** Use this command form:\n\n```\naws resiliencehubv2 create-service --name {service} --regions {regions} \\\n  --permission-model '{\"invokerRoleName\":\"ResilienceHubAssessmentRole\",\"crossAccountRoles\":[{\"crossAccountRoleArn\":\"arn:aws:iam::{member_account_id}:role\u002FResilienceHubAccess\",\"externalId\":\"{external_id}\"}]}'\n```\n\n> The `externalId` is a shared secret that defends against confused-deputy attacks — generate a cryptographically random value and store it in AWS Secrets Manager or SSM Parameter Store (SecureString); never commit it to source control or embed it in templates without a dynamic `{{resolve:secretsmanager:...}}` reference, and ensure it is not emitted in plaintext by CI\u002FCD logs or infrastructure-as-code output (use CloudFormation `NoEcho` parameters and mask it in pipeline logs).\n\nThe cross-account role (in the member account) trusts the central account's invoker role. You can\nconfigure multiple cross-account role ARNs per service — the `resiliencehubv2` API enforces a maximum (illustratively 5), so **verify the accepted limit from the API\u002Fmodel rather than assuming a fixed number**. Note: this per-service model is independent of\nthe Organizations integration above — there is no `register-delegated-administrator` operation in the\n`resiliencehubv2` CLI; organization-wide delegated-administrator registration is performed via AWS\nOrganizations trusted access and the Resilience Hub console, not a `resiliencehubv2` API call.\n\n## Configure multi-account setup\n\nTo set up cross-account assessment, follow the procedure exactly.\nSee [references\u002Fmulti-account-procedure.md](references\u002Fmulti-account-procedure.md).\n\n## Troubleshooting\n\n### Cross-account assessment fails with AccessDenied\n\nVerify: (1) the cross-account role ARN in the permission model matches exactly, (2) the\ncross-account role trust policy allows the central account's invoker role to assume it,\n(3) the externalId matches if configured.\n\n### No resources discovered in a member account\n\nConfirm the cross-account role has read permissions for the in-scope resource types\n(CloudFormation, EC2, RDS, etc.) and that input sources point to valid resources in the\ncorrect region.\n\n### Looking for a delegated-administrator setup\n\nResilience Hub v2 **does** support an AWS Organizations integration with a delegated administrator for\norganization-wide policy management and visibility — but it's configured from the **management account**\nvia Organizations trusted access + the Resilience Hub console (create the service-linked role, then\nregister the delegated administrator), **not** through a `resiliencehubv2` CLI operation (there is no\n`register-delegated-administrator` API). To assess a *single service* whose resources span accounts, use\nthe per-service cross-account permission model in this skill. The two are complementary.\n\n## Security Considerations\n\n- **Least privilege & read-only:** scope member-account cross-account roles to read-only discovery permissions (`cloudformation:Describe*`, `ec2:Describe*`, `rds:Describe*`, etc.) rather than write\u002Fmutate actions.\n- **Scope cross-account trust narrowly:** trust only the specific central invoker role ARN rather than the whole account where possible.\n- **Enable logging & monitoring:** ensure AWS CloudTrail is enabled in both the central and member accounts to log cross-account `sts:AssumeRole` calls, and alarm on failed or unexpected AssumeRole attempts against the cross-account roles.\n- **Further reading:** see [IAM best practices](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html), [The confused deputy problem](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fconfused-deputy.html), and [Security in AWS Resilience Hub](https:\u002F\u002Fdocs.aws.amazon.com\u002Fresilience-hub\u002Flatest\u002Fuserguide\u002Fsecurity.html) for cross-account hardening guidance.\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,50,57,120,129,135,140,220,232,238,243,320,404,416,448,488,494,506,512,519,524,530,535,541,587,593],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"multi-account-resilience-hub-v2-setup",[47],{"type":48,"value":49},"text","Multi-Account Resilience Hub v2 Setup",{"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,74,76,81,83,89,91,97,99,104,106,111,113,118],{"type":48,"value":62},"Domain expertise for configuring Resilience Hub v2 to assess services across multiple\nAWS accounts from a central account. All CLI commands in this skill use the ",{"type":42,"tag":64,"props":65,"children":66},"strong",{},[67],{"type":42,"tag":68,"props":69,"children":71},"code",{"className":70},[],[72],{"type":48,"value":73},"aws resiliencehubv2",{"type":48,"value":75},"\nnamespace — the Resilience Hub ",{"type":42,"tag":64,"props":77,"children":78},{},[79],{"type":48,"value":80},"v2",{"type":48,"value":82}," API surface — which is distinct from the legacy ",{"type":42,"tag":68,"props":84,"children":86},{"className":85},[],[87],{"type":48,"value":88},"aws resiliencehub",{"type":48,"value":90},"\n(v1) commands (the ",{"type":42,"tag":68,"props":92,"children":94},{"className":93},[],[95],{"type":48,"value":96},"service: [resiliencehub, ...]",{"type":48,"value":98}," metadata tags the service family, not the CLI namespace).\nResilience Hub v2 supports two complementary multi-account mechanisms: (1) an ",{"type":42,"tag":64,"props":100,"children":101},{},[102],{"type":48,"value":103},"AWS Organizations\nintegration",{"type":48,"value":105}," — the management account enables trusted access, creates the service-linked role, and\ndesignates a ",{"type":42,"tag":64,"props":107,"children":108},{},[109],{"type":48,"value":110},"delegated administrator",{"type":48,"value":112}," account for organization-wide policy management and visibility;\nand (2) the ",{"type":42,"tag":64,"props":114,"children":115},{},[116],{"type":48,"value":117},"per-service cross-account permission model",{"type":48,"value":119}," — an invoker role in the central account that\nassumes cross-account roles in member accounts for per-service resource discovery. This skill configures\n(2); the Organizations integration (1) is set up separately (management account + console — see below).",{"type":42,"tag":121,"props":122,"children":123},"blockquote",{},[124],{"type":42,"tag":58,"props":125,"children":126},{},[127],{"type":48,"value":128},"The AWS MCP server is recommended for executing this skill's AWS API calls, but it is not required — all operations also work with the AWS CLI directly.",{"type":42,"tag":51,"props":130,"children":132},{"id":131},"guardrail-where-this-skills-own-files-live-mcp-vs-local-install",[133],{"type":48,"value":134},"Guardrail — where this skill's own files live (MCP vs local install)",{"type":42,"tag":58,"props":136,"children":137},{},[138],{"type":48,"value":139},"Before reading a reference file, determine how this skill was loaded:",{"type":42,"tag":141,"props":142,"children":143},"ul",{},[144,194],{"type":42,"tag":145,"props":146,"children":147},"li",{},[148,161,163,168,170,176,178,184,186,192],{"type":42,"tag":64,"props":149,"children":150},{},[151,153,159],{"type":48,"value":152},"Loaded via the AWS MCP ",{"type":42,"tag":68,"props":154,"children":156},{"className":155},[],[157],{"type":48,"value":158},"retrieve_skill",{"type":48,"value":160}," tool:",{"type":48,"value":162}," the skill's reference files are not on the local filesystem. Fetch each one through ",{"type":42,"tag":68,"props":164,"children":166},{"className":165},[],[167],{"type":48,"value":158},{"type":48,"value":169}," with the ",{"type":42,"tag":68,"props":171,"children":173},{"className":172},[],[174],{"type":48,"value":175},"file",{"type":48,"value":177}," parameter (e.g. ",{"type":42,"tag":68,"props":179,"children":181},{"className":180},[],[182],{"type":48,"value":183},"file=\"references\u002Fmulti-account-procedure.md\"",{"type":48,"value":185},") — do NOT ",{"type":42,"tag":68,"props":187,"children":189},{"className":188},[],[190],{"type":48,"value":191},"file_read",{"type":48,"value":193}," these paths locally or search the filesystem for them.",{"type":42,"tag":145,"props":195,"children":196},{},[197,202,204,210,212,218],{"type":42,"tag":64,"props":198,"children":199},{},[200],{"type":48,"value":201},"Installed locally",{"type":48,"value":203}," (e.g. ",{"type":42,"tag":68,"props":205,"children":207},{"className":206},[],[208],{"type":48,"value":209},".kiro\u002Fskills\u002Fresilience-hub-multi-account\u002F",{"type":48,"value":211}," or ",{"type":42,"tag":68,"props":213,"children":215},{"className":214},[],[216],{"type":48,"value":217},"~\u002F.claude\u002Fskills\u002Fresilience-hub-multi-account\u002F",{"type":48,"value":219},"): read reference files from the local skill directory using the relative paths shown here.",{"type":42,"tag":58,"props":221,"children":222},{},[223,225,230],{"type":48,"value":224},"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":68,"props":226,"children":228},{"className":227},[],[229],{"type":48,"value":158},{"type":48,"value":231},".",{"type":42,"tag":51,"props":233,"children":235},{"id":234},"how-centralized-multi-account-assessment-works",[236],{"type":48,"value":237},"How centralized multi-account assessment works",{"type":42,"tag":58,"props":239,"children":240},{},[241],{"type":48,"value":242},"Two paths, used depending on your goal:",{"type":42,"tag":121,"props":244,"children":245},{},[246],{"type":42,"tag":58,"props":247,"children":248},{},[249,254,256,261,263,269,270,275,277,281,283,289,291,304,306,311,313,318],{"type":42,"tag":64,"props":250,"children":251},{},[252],{"type":48,"value":253},"Decision rule (read first):",{"type":48,"value":255}," To ",{"type":42,"tag":64,"props":257,"children":258},{},[259],{"type":48,"value":260},"run cross-account resilience assessments",{"type":48,"value":262}," — i.e. assess workloads\u002Fresources that live in member accounts from a central account (the common request, including phrasings like ",{"type":42,"tag":264,"props":265,"children":266},"em",{},[267],{"type":48,"value":268},"\"centralized resilience management across my Organization\"",{"type":48,"value":211},{"type":42,"tag":264,"props":271,"children":272},{},[273],{"type":48,"value":274},"\"central assessment account\"",{"type":48,"value":276},") — use the ",{"type":42,"tag":64,"props":278,"children":279},{},[280],{"type":48,"value":117},{"type":48,"value":282}," (path 2 below): an invoker role + cross-account roles + ",{"type":42,"tag":68,"props":284,"children":286},{"className":285},[],[287],{"type":48,"value":288},"create-service --permission-model",{"type":48,"value":290},". ",{"type":42,"tag":64,"props":292,"children":293},{},[294,296,302],{"type":48,"value":295},"Do NOT use or recommend ",{"type":42,"tag":68,"props":297,"children":299},{"className":298},[],[300],{"type":48,"value":301},"aws organizations register-delegated-administrator",{"type":48,"value":303}," (or any delegated-administrator registration) as the setup step for cross-account assessments.",{"type":48,"value":305}," The Organizations delegated-administrator integration (path 1) is a ",{"type":42,"tag":264,"props":307,"children":308},{},[309],{"type":48,"value":310},"separate, optional",{"type":48,"value":312}," feature scoped to organization-wide ",{"type":42,"tag":64,"props":314,"children":315},{},[316],{"type":48,"value":317},"policy management and visibility only",{"type":48,"value":319}," — it is not how you set up or run cross-account assessments. Only follow path 1 when the request is explicitly about org-wide policy governance, not assessment.",{"type":42,"tag":141,"props":321,"children":322},{},[323,381],{"type":42,"tag":145,"props":324,"children":325},{},[326,331,333,338,340,345,347,352,354,373,375,380],{"type":42,"tag":64,"props":327,"children":328},{},[329],{"type":48,"value":330},"Organization-wide governance",{"type":48,"value":332}," (centralized policies, cross-account visibility): use the ",{"type":42,"tag":64,"props":334,"children":335},{},[336],{"type":48,"value":337},"AWS\nOrganizations integration",{"type":48,"value":339},". From the ",{"type":42,"tag":64,"props":341,"children":342},{},[343],{"type":48,"value":344},"management account",{"type":48,"value":346},", enable trusted access for Resilience Hub,\ncreate the service-linked role, and ",{"type":42,"tag":64,"props":348,"children":349},{},[350],{"type":48,"value":351},"register a delegated administrator",{"type":48,"value":353}," account. This is done via\nOrganizations trusted access + the Resilience Hub console — there is ",{"type":42,"tag":64,"props":355,"children":356},{},[357,359,365,371],{"type":48,"value":358},"no ",{"type":42,"tag":68,"props":360,"children":362},{"className":361},[],[363],{"type":48,"value":364},"resiliencehubv2",{"type":42,"tag":68,"props":366,"children":368},{"className":367},[],[369],{"type":48,"value":370},"register-delegated-administrator",{"type":48,"value":372}," CLI operation",{"type":48,"value":374},". The delegated administrator then selects a home\nRegion where organization-level data is aggregated. See the AWS docs page ",{"type":42,"tag":264,"props":376,"children":377},{},[378],{"type":48,"value":379},"Setting up Organizations\nintegration",{"type":48,"value":231},{"type":42,"tag":145,"props":382,"children":383},{},[384,389,391,395,397,402],{"type":42,"tag":64,"props":385,"children":386},{},[387],{"type":48,"value":388},"Per-service cross-account resource discovery",{"type":48,"value":390}," (assessing a service whose resources span accounts):\nregister each service with a ",{"type":42,"tag":64,"props":392,"children":393},{},[394],{"type":48,"value":117},{"type":48,"value":396}," — an invoker role in the\ncentral account plus cross-account role ARNs for each member account. ",{"type":42,"tag":64,"props":398,"children":399},{},[400],{"type":48,"value":401},"This skill's steps configure\nthis path.",{"type":48,"value":403}," Use this command form:",{"type":42,"tag":405,"props":406,"children":410},"pre",{"className":407,"code":409,"language":48},[408],"language-text","aws resiliencehubv2 create-service --name {service} --regions {regions} \\\n  --permission-model '{\"invokerRoleName\":\"ResilienceHubAssessmentRole\",\"crossAccountRoles\":[{\"crossAccountRoleArn\":\"arn:aws:iam::{member_account_id}:role\u002FResilienceHubAccess\",\"externalId\":\"{external_id}\"}]}'\n",[411],{"type":42,"tag":68,"props":412,"children":414},{"__ignoreMap":413},"",[415],{"type":48,"value":409},{"type":42,"tag":121,"props":417,"children":418},{},[419],{"type":42,"tag":58,"props":420,"children":421},{},[422,424,430,432,438,440,446],{"type":48,"value":423},"The ",{"type":42,"tag":68,"props":425,"children":427},{"className":426},[],[428],{"type":48,"value":429},"externalId",{"type":48,"value":431}," is a shared secret that defends against confused-deputy attacks — generate a cryptographically random value and store it in AWS Secrets Manager or SSM Parameter Store (SecureString); never commit it to source control or embed it in templates without a dynamic ",{"type":42,"tag":68,"props":433,"children":435},{"className":434},[],[436],{"type":48,"value":437},"{{resolve:secretsmanager:...}}",{"type":48,"value":439}," reference, and ensure it is not emitted in plaintext by CI\u002FCD logs or infrastructure-as-code output (use CloudFormation ",{"type":42,"tag":68,"props":441,"children":443},{"className":442},[],[444],{"type":48,"value":445},"NoEcho",{"type":48,"value":447}," parameters and mask it in pipeline logs).",{"type":42,"tag":58,"props":449,"children":450},{},[451,453,458,460,465,467,472,474,479,481,486],{"type":48,"value":452},"The cross-account role (in the member account) trusts the central account's invoker role. You can\nconfigure multiple cross-account role ARNs per service — the ",{"type":42,"tag":68,"props":454,"children":456},{"className":455},[],[457],{"type":48,"value":364},{"type":48,"value":459}," API enforces a maximum (illustratively 5), so ",{"type":42,"tag":64,"props":461,"children":462},{},[463],{"type":48,"value":464},"verify the accepted limit from the API\u002Fmodel rather than assuming a fixed number",{"type":48,"value":466},". Note: this per-service model is independent of\nthe Organizations integration above — there is no ",{"type":42,"tag":68,"props":468,"children":470},{"className":469},[],[471],{"type":48,"value":370},{"type":48,"value":473}," operation in the\n",{"type":42,"tag":68,"props":475,"children":477},{"className":476},[],[478],{"type":48,"value":364},{"type":48,"value":480}," CLI; organization-wide delegated-administrator registration is performed via AWS\nOrganizations trusted access and the Resilience Hub console, not a ",{"type":42,"tag":68,"props":482,"children":484},{"className":483},[],[485],{"type":48,"value":364},{"type":48,"value":487}," API call.",{"type":42,"tag":51,"props":489,"children":491},{"id":490},"configure-multi-account-setup",[492],{"type":48,"value":493},"Configure multi-account setup",{"type":42,"tag":58,"props":495,"children":496},{},[497,499,505],{"type":48,"value":498},"To set up cross-account assessment, follow the procedure exactly.\nSee ",{"type":42,"tag":500,"props":501,"children":503},"a",{"href":502},"references\u002Fmulti-account-procedure.md",[504],{"type":48,"value":502},{"type":48,"value":231},{"type":42,"tag":51,"props":507,"children":509},{"id":508},"troubleshooting",[510],{"type":48,"value":511},"Troubleshooting",{"type":42,"tag":513,"props":514,"children":516},"h3",{"id":515},"cross-account-assessment-fails-with-accessdenied",[517],{"type":48,"value":518},"Cross-account assessment fails with AccessDenied",{"type":42,"tag":58,"props":520,"children":521},{},[522],{"type":48,"value":523},"Verify: (1) the cross-account role ARN in the permission model matches exactly, (2) the\ncross-account role trust policy allows the central account's invoker role to assume it,\n(3) the externalId matches if configured.",{"type":42,"tag":513,"props":525,"children":527},{"id":526},"no-resources-discovered-in-a-member-account",[528],{"type":48,"value":529},"No resources discovered in a member account",{"type":42,"tag":58,"props":531,"children":532},{},[533],{"type":48,"value":534},"Confirm the cross-account role has read permissions for the in-scope resource types\n(CloudFormation, EC2, RDS, etc.) and that input sources point to valid resources in the\ncorrect region.",{"type":42,"tag":513,"props":536,"children":538},{"id":537},"looking-for-a-delegated-administrator-setup",[539],{"type":48,"value":540},"Looking for a delegated-administrator setup",{"type":42,"tag":58,"props":542,"children":543},{},[544,546,551,553,557,559,564,566,571,573,578,580,585],{"type":48,"value":545},"Resilience Hub v2 ",{"type":42,"tag":64,"props":547,"children":548},{},[549],{"type":48,"value":550},"does",{"type":48,"value":552}," support an AWS Organizations integration with a delegated administrator for\norganization-wide policy management and visibility — but it's configured from the ",{"type":42,"tag":64,"props":554,"children":555},{},[556],{"type":48,"value":344},{"type":48,"value":558},"\nvia Organizations trusted access + the Resilience Hub console (create the service-linked role, then\nregister the delegated administrator), ",{"type":42,"tag":64,"props":560,"children":561},{},[562],{"type":48,"value":563},"not",{"type":48,"value":565}," through a ",{"type":42,"tag":68,"props":567,"children":569},{"className":568},[],[570],{"type":48,"value":364},{"type":48,"value":572}," CLI operation (there is no\n",{"type":42,"tag":68,"props":574,"children":576},{"className":575},[],[577],{"type":48,"value":370},{"type":48,"value":579}," API). To assess a ",{"type":42,"tag":264,"props":581,"children":582},{},[583],{"type":48,"value":584},"single service",{"type":48,"value":586}," whose resources span accounts, use\nthe per-service cross-account permission model in this skill. The two are complementary.",{"type":42,"tag":51,"props":588,"children":590},{"id":589},"security-considerations",[591],{"type":48,"value":592},"Security Considerations",{"type":42,"tag":141,"props":594,"children":595},{},[596,629,639,657],{"type":42,"tag":145,"props":597,"children":598},{},[599,604,606,612,614,620,621,627],{"type":42,"tag":64,"props":600,"children":601},{},[602],{"type":48,"value":603},"Least privilege & read-only:",{"type":48,"value":605}," scope member-account cross-account roles to read-only discovery permissions (",{"type":42,"tag":68,"props":607,"children":609},{"className":608},[],[610],{"type":48,"value":611},"cloudformation:Describe*",{"type":48,"value":613},", ",{"type":42,"tag":68,"props":615,"children":617},{"className":616},[],[618],{"type":48,"value":619},"ec2:Describe*",{"type":48,"value":613},{"type":42,"tag":68,"props":622,"children":624},{"className":623},[],[625],{"type":48,"value":626},"rds:Describe*",{"type":48,"value":628},", etc.) rather than write\u002Fmutate actions.",{"type":42,"tag":145,"props":630,"children":631},{},[632,637],{"type":42,"tag":64,"props":633,"children":634},{},[635],{"type":48,"value":636},"Scope cross-account trust narrowly:",{"type":48,"value":638}," trust only the specific central invoker role ARN rather than the whole account where possible.",{"type":42,"tag":145,"props":640,"children":641},{},[642,647,649,655],{"type":42,"tag":64,"props":643,"children":644},{},[645],{"type":48,"value":646},"Enable logging & monitoring:",{"type":48,"value":648}," ensure AWS CloudTrail is enabled in both the central and member accounts to log cross-account ",{"type":42,"tag":68,"props":650,"children":652},{"className":651},[],[653],{"type":48,"value":654},"sts:AssumeRole",{"type":48,"value":656}," calls, and alarm on failed or unexpected AssumeRole attempts against the cross-account roles.",{"type":42,"tag":145,"props":658,"children":659},{},[660,665,667,675,676,683,685,692],{"type":42,"tag":64,"props":661,"children":662},{},[663],{"type":48,"value":664},"Further reading:",{"type":48,"value":666}," see ",{"type":42,"tag":500,"props":668,"children":672},{"href":669,"rel":670},"https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html",[671],"nofollow",[673],{"type":48,"value":674},"IAM best practices",{"type":48,"value":613},{"type":42,"tag":500,"props":677,"children":680},{"href":678,"rel":679},"https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fconfused-deputy.html",[671],[681],{"type":48,"value":682},"The confused deputy problem",{"type":48,"value":684},", and ",{"type":42,"tag":500,"props":686,"children":689},{"href":687,"rel":688},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fresilience-hub\u002Flatest\u002Fuserguide\u002Fsecurity.html",[671],[690],{"type":48,"value":691},"Security in AWS Resilience Hub",{"type":48,"value":693}," for cross-account hardening guidance.",{"items":695,"total":799},[696,713,728,743,758,768,783],{"slug":697,"name":697,"fn":698,"description":699,"org":700,"tags":701,"stars":24,"repoUrl":25,"updatedAt":712},"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},[702,705,708,709],{"name":703,"slug":704,"type":15},"Agents","agents",{"name":706,"slug":707,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":710,"slug":711,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":714,"name":714,"fn":715,"description":716,"org":717,"tags":718,"stars":24,"repoUrl":25,"updatedAt":727},"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},[719,720,723,726],{"name":703,"slug":704,"type":15},{"name":721,"slug":722,"type":15},"API Development","api-development",{"name":724,"slug":725,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":729,"name":729,"fn":730,"description":731,"org":732,"tags":733,"stars":24,"repoUrl":25,"updatedAt":742},"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},[734,735,736,739],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":737,"slug":738,"type":15},"Debugging","debugging",{"name":740,"slug":741,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":744,"name":744,"fn":745,"description":746,"org":747,"tags":748,"stars":24,"repoUrl":25,"updatedAt":757},"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},[749,750,751,754],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":752,"slug":753,"type":15},"CI\u002FCD","ci-cd",{"name":755,"slug":756,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":759,"name":759,"fn":760,"description":761,"org":762,"tags":763,"stars":24,"repoUrl":25,"updatedAt":767},"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},[764,765,766],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":755,"slug":756,"type":15},"2026-07-12T08:42:51.963247",{"slug":769,"name":769,"fn":770,"description":771,"org":772,"tags":773,"stars":24,"repoUrl":25,"updatedAt":782},"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},[774,775,776,779],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":777,"slug":778,"type":15},"Best Practices","best-practices",{"name":780,"slug":781,"type":15},"Security","security","2026-07-16T06:00:42.174705",{"slug":784,"name":784,"fn":785,"description":786,"org":787,"tags":788,"stars":24,"repoUrl":25,"updatedAt":798},"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},[789,790,791,794,795],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":792,"slug":793,"type":15},"Evals","evals",{"name":740,"slug":741,"type":15},{"name":796,"slug":797,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",114,{"items":801,"total":918},[802,809,816,823,830,836,843,851,868,881,893,908],{"slug":697,"name":697,"fn":698,"description":699,"org":803,"tags":804,"stars":24,"repoUrl":25,"updatedAt":712},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[805,806,807,808],{"name":703,"slug":704,"type":15},{"name":706,"slug":707,"type":15},{"name":23,"slug":8,"type":15},{"name":710,"slug":711,"type":15},{"slug":714,"name":714,"fn":715,"description":716,"org":810,"tags":811,"stars":24,"repoUrl":25,"updatedAt":727},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[812,813,814,815],{"name":703,"slug":704,"type":15},{"name":721,"slug":722,"type":15},{"name":724,"slug":725,"type":15},{"name":23,"slug":8,"type":15},{"slug":729,"name":729,"fn":730,"description":731,"org":817,"tags":818,"stars":24,"repoUrl":25,"updatedAt":742},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[819,820,821,822],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":737,"slug":738,"type":15},{"name":740,"slug":741,"type":15},{"slug":744,"name":744,"fn":745,"description":746,"org":824,"tags":825,"stars":24,"repoUrl":25,"updatedAt":757},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[826,827,828,829],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":752,"slug":753,"type":15},{"name":755,"slug":756,"type":15},{"slug":759,"name":759,"fn":760,"description":761,"org":831,"tags":832,"stars":24,"repoUrl":25,"updatedAt":767},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[833,834,835],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":755,"slug":756,"type":15},{"slug":769,"name":769,"fn":770,"description":771,"org":837,"tags":838,"stars":24,"repoUrl":25,"updatedAt":782},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[839,840,841,842],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":777,"slug":778,"type":15},{"name":780,"slug":781,"type":15},{"slug":784,"name":784,"fn":785,"description":786,"org":844,"tags":845,"stars":24,"repoUrl":25,"updatedAt":798},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[846,847,848,849,850],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":792,"slug":793,"type":15},{"name":740,"slug":741,"type":15},{"name":796,"slug":797,"type":15},{"slug":852,"name":852,"fn":853,"description":854,"org":855,"tags":856,"stars":24,"repoUrl":25,"updatedAt":867},"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},[857,858,861,864],{"name":23,"slug":8,"type":15},{"name":859,"slug":860,"type":15},"Database","database",{"name":862,"slug":863,"type":15},"MySQL","mysql",{"name":865,"slug":866,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":869,"name":869,"fn":870,"description":871,"org":872,"tags":873,"stars":24,"repoUrl":25,"updatedAt":880},"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},[874,875,876,879],{"name":23,"slug":8,"type":15},{"name":859,"slug":860,"type":15},{"name":877,"slug":878,"type":15},"PostgreSQL","postgresql",{"name":865,"slug":866,"type":15},"2026-07-16T06:00:34.789624",{"slug":882,"name":882,"fn":883,"description":884,"org":885,"tags":886,"stars":24,"repoUrl":25,"updatedAt":892},"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},[887,888,889],{"name":703,"slug":704,"type":15},{"name":23,"slug":8,"type":15},{"name":890,"slug":891,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":894,"name":894,"fn":895,"description":896,"org":897,"tags":898,"stars":24,"repoUrl":25,"updatedAt":907},"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},[899,900,901,904],{"name":23,"slug":8,"type":15},{"name":859,"slug":860,"type":15},{"name":902,"slug":903,"type":15},"MongoDB","mongodb",{"name":905,"slug":906,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":909,"name":909,"fn":910,"description":911,"org":912,"tags":913,"stars":24,"repoUrl":25,"updatedAt":917},"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},[914,915,916],{"name":23,"slug":8,"type":15},{"name":859,"slug":860,"type":15},{"name":905,"slug":906,"type":15},"2026-07-16T06:00:37.690386",115]