[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A2TRAKVPCB24YKBYSD13RM":3,"skill-same:01M7A2TRAKVPCB24YKBYSD13RM":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7A2TRAKVPCB24YKBYSD13RM","account-factory-deployer",null,"Deploys AWS Control Tower Account Factory accounts with production defaults: account creation via Service Catalog product (provision-product), Organizational Unit placement, SSO assignment via permission sets, Guardrail inheritance (SCP, Detective, Config), landing zone baseline conformance, email and account name uniqueness, alternate contacts, compliance status verification, account customization via custom product (CloudFormation StackSets), vending new accounts, terminating accounts, and updating account baselines. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating AWS accounts via Control Tower, vending accounts to teams, assigning SSO permission sets, verifying Guardrail. Triggers: create aws account control tower, account factory provision, vending new account, control tower account enrollment, sso permission set assignment, guardrail scp inheritance, account factory service catalog, control tower landing zone baseline, terminate aws account, custom account baseline.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: account-factory-deployer\ndescription: 'Deploys AWS Control Tower Account Factory accounts with production defaults: account creation via Service Catalog product (provision-product), Organizational Unit placement, SSO assignment via permission sets, Guardrail inheritance (SCP, Detective, Config), landing zone baseline conformance, email and account name uniqueness, alternate contacts, compliance status verification, account customization via custom product (CloudFormation StackSets), vending new accounts, terminating accounts, and updating account baselines. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating AWS accounts via Control Tower, vending accounts to teams, assigning SSO permission sets, verifying Guardrail. Triggers: create aws account control tower, account factory provision, vending new account, control tower account enrollment, sso permission set assignment, guardrail scp inheritance, account factory service catalog, control tower landing zone baseline, terminate aws account, custom account baseline.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with servicecatalog, controltower, organizations, and sso-admin access. Works with Terraform aws_controltower_account \u002F aws_organizations_ account \u002F aws_ssoadmin_permission_set resources and CloudFormation AWS::ServiceCatalog::CloudFormationProvisionedProduct templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Governance\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, control-tower, account-factory, cloudops, deploy, governance, provisioning, landing-zone, scp, guardrails, sso, organizations\n  dependencies: aws-orchestrator\n  keywords: aws, control tower, account factory, service catalog, cloudops, deploy, provisioning, landing zone, scp, guardrails, sso, permission set, organizations, stacksets, baseline, account vending, compliance, alternate contacts\n  when_to_use: Invoke when the user wants to create AWS accounts via Control Tower Account Factory, vend accounts to teams, place accounts in Organizational Units, assign SSO permission sets, verify Guardrail (SCP\u002FDetective\u002FConfig) inheritance, customize account baselines via CloudFormation StackSets, update account baselines, or terminate accounts. Do NOT invoke for AWS Organizations account creation outside Control Tower (use organizations-account-deployer), Control Tower landing zone setup\u002Fupgrade (use controltower-control- auditor), or SCP authoring (use organizations-scp-deployer).\n---\n\n# AWS Control Tower Account Factory Deployer\n\nAn AWS CloudOps agent skill that deploys AWS accounts via Control Tower\nAccount Factory with correct defaults. The skill walks the operator\nthrough Service Catalog product provisioning, OU placement, SSO\npermission set assignment, Guardrail inheritance verification, landing\nzone baseline conformance, email uniqueness, alternate contacts, account\ncustomization via StackSets, and account lifecycle management (vending,\nupdating, terminating), captures governance decisions, explains why each\ndefault matters, and emits a READY_TO_DEPLOY checklist with copy-\npasteable verification commands.\n\n## Activation keywords\n\ncreate AWS account Control Tower, account factory provision, vending\nnew account, Control Tower account enrollment, SSO permission set\nassignment, Guardrail SCP inheritance, Account Factory Service Catalog,\nControl Tower landing zone baseline, terminate AWS account, custom\naccount baseline.\n\n## STRICT output contract\n\nWhen this skill is invoked with an Account Factory provisioning request\n(create\u002Fvend an account, assign permission sets, verify Guardrails,\ncustomize baselines, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `ACCOUNT_FACTORY:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Account Factory via Service Catalog | Core vending mechanism |\n| Step 2 — Organizational Unit placement | OU topology |\n| Step 3 — SSO permission set assignment | Access control |\n| Step 4 — Guardrail inheritance (SCP, Detective, Config) | Compliance |\n| Step 5 — Landing zone baseline conformance | Baseline enforcement |\n| Step 6 — Email and account name uniqueness | Prerequisite check |\n| Step 7 — Alternate contacts | Operational metadata |\n| Step 8 — Account customization (custom product\u002FStackSets) | Baseline customization |\n| Step 9 — Account lifecycle (vending, updating, terminating) | Lifecycle management |\n| Step 10 — Compliance status verification | Post-provision audit |\n| Step 11 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fguardrails-and-baseline.md | Guardrail + baseline detail |\n| references\u002Fsso-and-lifecycle.md | SSO + lifecycle detail |\n| references\u002Fadvanced-patterns.md | Dependency graph + recent features |\n| references\u002Ferror-handling.md | Provisioning failure remedies |\n| references\u002Fdiagnostic-commands.md | Verification CLI detail |\n\n## Mindset\n\n**One-line takeaway:** Control Tower Account Factory vends AWS accounts\nthrough a Service Catalog product. Each account is placed in an\nOrganizational Unit, inherits Guardrails (SCP, Detective, Config) from\nthe OU and landing zone, gets SSO access via permission sets, and\nreceives a baseline (CloudFormation StackSets for logging, security,\nand operational standards). The Service Catalog product is the ONLY\nsupported way to create accounts that Control Tower manages — accounts\ncreated directly via Organizations `CreateAccount` are NOT enrolled in\nControl Tower and do NOT inherit Guardrails or baselines.\n\nThree misconceptions in full (raw Organizations ≠ Account Factory; Guardrails apply only to registered OUs; SSO assignment is a three-way binding): [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## Configuration dependency graph (novel heuristic)\n\nAccount Factory configurations are NOT independent. The landing zone\nmust exist before OUs can be registered. OUs must be registered before\naccounts can be enrolled. The Service Catalog product must be available\nbefore provisioning. SSO permission sets must exist before assignment.\nUse this graph to sequence provisioning.\n\nFull dependency table (landing zone → registered OU → SC product → account → SSO → guardrails → baseline → custom product → alternate contacts) plus cross-dependency gotchas: [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: landing zone baseline propagation\n\nBaseline propagation walkthrough (StackSet fan-out via AWSControlTowerExecutionRole, per-account baseline resources, incomplete-baseline failure mode): [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Expert heuristic: SCP inheritance from parent OU\n\nSCP hierarchy walkthrough (effective-SCP intersection, OU-move consequences) and the preventive\u002Fdetective\u002Fproactive Guardrail types: [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Expert heuristic: SSO permission set auto-assignment\n\nGroup-based auto-assignment flow and the O(groups × OUs) scaling model: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Control Tower landing zone enabled | Account Factory requires an active landing zone | `aws controltower list-landing-zones` |\n| Target OU registered with Control Tower | Only registered OUs get Guardrails and baselines | `aws controltower list-controls --control-source-ou \u003Cou-id>` |\n| Service Catalog product available | Account vending uses the Account Factory SC product | `aws servicecatalog search-products --filters FullTextSearch=Control` |\n| Unique account email | Duplicate emails fail provisioning | Check email pattern against existing accounts |\n| Unique account name | Duplicate names cause confusion in billing and console | `aws organizations list-accounts --query 'Accounts[*].Name'` |\n| Identity Center enabled | SSO assignment requires Identity Center | `aws sso-admin list-instances` |\n| Permission sets defined | Assignment requires existing permission sets | `aws sso-admin list-permission-sets --instance-arn \u003Carn>` |\n| Management account access | Account Factory runs from the management account | `aws sts get-caller-identity` (must be management account) |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Account Factory via Service Catalog\n\nAccount Factory vends accounts through a Service Catalog product. The\nproduct is auto-created by Control Tower during landing zone setup.\n\n**Provision a new account:**\n\n```bash\n# Get the Account Factory product ID\nPRODUCT_ID=$(aws servicecatalog search-products \\\n  --filters FullTextSearch=\"AWS Control Tower Account Factory Factory\" \\\n  --query 'ProductViewSummaries[0].ProductId' --output text)\n\n# Get the provisioning artifact ID (the \"version\" of the product)\nARTIFACT_ID=$(aws servicecatalog describe-product \\\n  --id \"$PRODUCT_ID\" \\\n  --query 'ProvisioningArtifacts[0].Id' --output text)\n\n# Provision the account\naws servicecatalog provision-product \\\n  --product-id \"$PRODUCT_ID\" \\\n  --provisioning-artifact-id \"$ARTIFACT_ID\" \\\n  --provisioned-product-name \"data-platform-prod\" \\\n  --provisioning-parameters '[\n    {\"Key\":\"AccountEmail\",\"Value\":\"aws+data-platform@company.com\"},\n    {\"Key\":\"AccountName\",\"Value\":\"data-platform-prod\"},\n    {\"Key\":\"ManagedOrganizationalUnit\",\"Value\":\"Custom (DataPlatform)\"},\n    {\"Key\":\"SSOUserEmail\",\"Value\":\"platform-lead@company.com\"},\n    {\"Key\":\"SSOUserFirstName\",\"Value\":\"Platform\"},\n    {\"Key\":\"SSOUserLastName\",\"Value\":\"Team\"}\n  ]'\n```\n\n**Provisioning parameters (required):**\n\n| Parameter | Description | Constraints |\n|---|---|---|\n| AccountEmail | Root email for the account | Globally unique; not used by any other AWS account |\n| AccountName | Display name | Unique within the org |\n| ManagedOrganizationalUnit | Target OU (name or SelectWithExist) | Must be a registered OU |\n| SSOUserEmail | Initial SSO admin email | Must be unique in Identity Center |\n| SSOUserFirstName | Initial SSO admin first name | Non-empty |\n| SSOUserLastName | Initial SSO admin last name | Non-empty |\n\n**Provisioning is asynchronous** — typically 5-30 minutes. Poll the\nprovisioned product status:\n\n```bash\naws servicecatalog describe-provisioned-product \\\n  --name \"data-platform-prod\" \\\n  --query 'ProvisionedProductDetail.Status' --output text\n# Wait for status: AVAILABLE\n```\n\n## Step 2 — Organizational Unit placement\n\nThe target OU determines Guardrail inheritance and baseline StackSet\ndeployment. The OU must be registered with Control Tower.\n\n**Registered vs. unregistered OUs:**\n\n| OU type | Guardrails | Baseline | SSO auto-provision |\n|---|---|---|---|\n| Registered with Control Tower | Full SCP inheritance | StackSets auto-deploy | Yes |\n| Unregistered (raw org OU) | No Guardrails | No baseline | No |\n\n**List registered OUs:**\n\n```bash\n# List all registered OUs in the landing zone\naws controltower list-enabled-controls \\\n  --control-source-ou \u003Croot-ou-id> \\\n  --query 'EnabledControls[*].ControlIdentifier' --output table\n```\n\n**Place the account in the correct OU:**\n\nThe OU is specified via the `ManagedOrganizationalUnit` parameter in\nthe Service Catalog provisioning call. The format is the OU name as\nshown in Control Tower (e.g., \"Custom (DataPlatform)\") or the OU's\nSelectWithExist path.\n\n**Moving an account between OUs** (after creation):\n\n```bash\naws organizations move-account \\\n  --account-id \"123456789012\" \\\n  --source-parent-id \"ou-aaa-source111\" \\\n  --destination-parent-id \"ou-bbb-dest222\"\n```\n\n**Critical:** moving an account to a different OU immediately changes\nits inherited SCPs. Moving from a strict OU to a permissive OU can\nexpose the account to previously-blocked actions.\n\n## Step 3 — SSO permission set assignment\n\nSSO (Identity Center) provides federated access to accounts via\npermission sets. Assignment is a three-way binding: principal (user or\ngroup) + permission set + account.\n\nCreate\u002Fattach\u002Fassign\u002Fprovision CLI sequence and the provisioning-is-separate-from-assignment rule: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 4 — Guardrail inheritance (SCP, Detective, Config)\n\nGuardrails are inherited from the OU level. An account in a registered\nOU automatically gets:\n\n| Guardrail type | Implementation | Example |\n|---|---|---|\n| Preventive | SCP in Organizations | Deny leaving org, deny disabling CloudTrail |\n| Detective | Config rule + Security Hub control | Detect publicly readable S3 bucket |\n| Proactive | Config rule | Detect non-compliant resource creation |\n\nSCP and Config-rule verification CLI: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 5 — Landing zone baseline conformance\n\nControl Tower deploys a baseline (set of StackSets) to every enrolled\naccount. The baseline includes:\n\n| Baseline StackSet | Purpose | Target |\n|---|---|---|\n| AWSControlTowerLogging | CloudTrail trail to logging account | All enrolled accounts |\n| AWSControlTowerSecurity | Security Hub, Config rules | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CLOUDTRAIL | CloudTrail baseline | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CONFIG | Config recorder baseline | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CLOUDWATCH | CloudWatch alarms baseline | All enrolled accounts |\n\nStackSet instance-status check and failure triage: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 6 — Email and account name uniqueness\n\n**Email uniqueness:** the root email for each AWS account must be\nglobally unique across ALL AWS accounts (including accounts in other\norgs and closed accounts). AWS rejects provisioning with a duplicate\nemail.\n\nEmail alias pattern, examples, and the uniqueness-check CLI: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 7 — Alternate contacts\n\nAlternate contacts provide operational metadata for billing, security,\nand operational notifications. They are set per-account via the Account\nManagement API.\n\nput-alternate-contact CLI for BILLING, SECURITY, and OPERATIONS contacts: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n**Critical:** alternate contacts are NOT inherited from the OU or org\nlevel. They must be set per-account. Automate this in the account\ncustomization pipeline (Step 8).\n\n## Step 8 — Account customization (custom product\u002FStackSets)\n\nBeyond the default baseline, accounts can be customized via custom\nService Catalog products that deploy additional CloudFormation\nStackSets.\n\n**Custom product pattern:**\n\n```text\nCustom account customization flow:\n  1. Create a CloudFormation template with account-specific resources\n     (VPC, KMS keys, IAM roles, CloudWatch dashboards, etc.)\n  2. Publish as a Service Catalog product in the Account Factory portfolio\n  3. When vending an account, provision BOTH the standard Account Factory\n     product AND the custom product\n  4. Control Tower's StackSets deploy the custom resources alongside the\n     baseline\n```\n\nCustom StackSet create CLI and the customization-template flow: [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Step 9 — Account lifecycle (vending, updating, terminating)\n\nBaseline update, terminate-provisioned-product, and the SUSPENDED-then-closed-after-90-days lifecycle: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 10 — Compliance status verification\n\nAfter provisioning, verify the account's compliance status:\n\nOU placement, SCP, Config, Security Hub, and SSO verification CLI: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 11 — Recent features\n\n2023-2026 features — Account Factory Customization, group-based auto-assignment, email validation API, Landing Zone 3.0+, API termination, StackSet alternate contacts: [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER create accounts via raw Organizations `CreateAccount` when\n   Control Tower is in use.** Organizations-created accounts are NOT\n   enrolled in Control Tower. They miss Guardrails, baselines, and SSO.\n   Always use the Account Factory Service Catalog product for managed\n   accounts.\n\n2. **NEVER place accounts in unregistered OUs.** Only registered OUs\n   get Guardrails (SCP, Detective, Config). An account in an\n   unregistered OU is a compliance gap. Always verify the OU is\n   registered with Control Tower before vending.\n\n3. **NEVER use duplicate root emails.** The root email must be globally\n   unique. Duplicate emails cause provisioning failures. Use a\n   consistent alias pattern (e.g., `aws+\u003Cou>-\u003Cname>@company.com`).\n\n4. **NEVER assume SCPs persist after moving accounts between OUs.**\n   SCPs are inherited from the OU. Moving an account to a different OU\n   immediately changes its effective SCPs. Always verify SCPs after any\n   OU move.\n\n5. **NEVER skip baseline StackSet verification.** Control Tower deploys\n   baselines automatically, but StackSets can fail silently. An\n   account with a failed StackSet has no CloudTrail, Config, or\n   Security Hub — a critical compliance gap. Always verify StackSet\n   deployment status.\n\n6. **NEVER assign SSO permission sets without provisioning.** Creating\n   a permission set and assigning it to a principal does NOT take\n   effect until the permission set is provisioned to the account.\n   Always call `provision-permission-set` after assignment.\n\n7. **NEVER forget alternate contacts.** They are not inherited from\n   the OU or org level. Without billing\u002Fsecurity\u002Foperations contacts,\n   AWS support and billing notifications go to the root email only.\n   Always set all three alternate contacts per account.\n\n8. **NEVER assume Account Factory termination deletes the AWS account.**\n   Terminating the Service Catalog product dis-enrolls the account\n   from Control Tower but does NOT close the AWS account. The account\n   remains in SUSPENDED state for 90 days before permanent closure.\n   Close the account separately if immediate removal is needed.\n\n9. **NEVER use individual user SSO assignments at scale.** Assign\n   permission sets to GROUPS, not individual users. Group-based\n   assignment scales to O(groups x OUs) instead of O(users x accounts).\n   Add users to groups; groups inherit permission sets.\n\n10. **NEVER skip landing zone version checks.** Outdated landing zone\n    versions silently lack newer Guardrails and features. Always check\n    the landing zone version and upgrade before vending accounts that\n    require the latest Guardrails.\n\n## Output format\n\n```text\nACCOUNT_FACTORY: \u003Caccount-name> (\u003Caccount-id>) in OU \u003Cou-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Account email: \u003Cemail> — UNIQUE (globally)\n  [✓|✗] Account name: \u003Cname> — UNIQUE (within org)\n  [✓|✗] Target OU: \u003Cou-name> (\u003Cou-id>) — REGISTERED with Control Tower\n  [✓|✗] Service Catalog product: \u003Cproduct-id> — AVAILABLE\n  [✓|✗] Account provisioned: \u003Caccount-id> — ACTIVE\n  [✓|✗] Guardrails (SCP): \u003Ccount> preventive controls inherited from OU\n  [✓|✗] Guardrails (Detective): Config rules deployed in account\n  [✓|✗] Guardrails (Config): baseline StackSets — \u003Call\u002Ffailed list>\n  [✓|✗] Baseline StackSets: AWSControlTowerLogging — DEPLOYED, AWSControlTowerSecurity — DEPLOYED\n  [✓|✗] SSO: Identity Center instance \u003Cinstance-arn>\n  [✓|✗] Permission sets: \u003Clist> assigned to \u003Cgroup> for this account\n  [✓|✗] SSO provisioning: permission set provisioned — SUCCEEDED\n  [✓|✗] Alternate contacts: BILLING ✓, SECURITY ✓, OPERATIONS ✓\n  [✓|✗] Custom baseline: \u003Cstackset-name> — DEPLOYED\n  [✓|✗] Compliance status: \u003Ccompliant | non-compliant (gaps listed)>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws organizations describe-account --account-id \u003Caccount-id>\n  aws organizations list-policies-for-target --target-id \u003Caccount-id> --filter SERVICE_CONTROL_POLICY\n  aws cloudformation list-stack-instances --stack-set-name AWSControlTowerLogging\n  aws sso-admin list-account-assignments --instance-arn \u003Cinstance-arn> --account-id \u003Caccount-id>\n```\n\n### Worked example — data platform account with SSO and Guardrails\n\n```text\nACCOUNT_FACTORY: data-platform-prod (123456789012) in OU DataPlatform (ou-bbb-ccc)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Account email: aws+prod-data-platform@company.com — UNIQUE\n  [✓] Account name: data-platform-prod — UNIQUE\n  [✓] Target OU: Custom (DataPlatform) (ou-bbb-ccc) — REGISTERED\n  [✓] Service Catalog product: prod-aaa111 — AVAILABLE\n  [✓] Account provisioned: 123456789012 — ACTIVE\n  [✓] Guardrails (SCP): 8 preventive controls inherited from OU\n  [✓] Guardrails (Detective): 12 Config rules deployed\n  [✓] Guardrails (Config): baseline StackSets — all DEPLOYED\n  [✓] Baseline StackSets: AWSControlTowerLogging — DEPLOYED, AWSControlTowerSecurity — DEPLOYED\n  [✓] SSO: Identity Center instance arn:aws:sso:::instance\u002Fssoins-12345\n  [✓] Permission sets: DataEngineerAccess assigned to DataPlatformTeam group\n  [✓] SSO provisioning: DataEngineerAccess provisioned — SUCCEEDED\n  [✓] Alternate contacts: BILLING ✓, SECURITY ✓, OPERATIONS ✓\n  [✓] Custom baseline: CustomBaseline-VPC — DEPLOYED\n  [✓] Compliance status: compliant\n  [✓] Tags: Environment=production, OU=DataPlatform, Owner=PlatformTeam\nVERIFICATION_COMMANDS:\n  aws organizations describe-account --account-id 123456789012\n  aws organizations list-policies-for-target --target-id 123456789012 --filter SERVICE_CONTROL_POLICY\n  aws cloudformation list-stack-instances --stack-set-name AWSControlTowerLogging\n  aws sso-admin list-account-assignments --instance-arn arn:aws:sso:::instance\u002Fssoins-12345 --account-id 123456789012\n```\n\n## Error handling\n\nStuck provisioning, failed baseline StackSet, unprovisioned permission set, missing Guardrails, unset alternate contacts: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Guardrails and baseline](references\u002Fguardrails-and-baseline.md) — guardrail types, OU registration, baseline StackSets, SCP-inheritance and propagation heuristics, custom StackSets\n- [SSO and lifecycle](references\u002Fsso-and-lifecycle.md) — permission sets, group assignment, vending\u002Fupdating\u002Fterminating, email management\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — provisioning misconceptions, configuration dependency graph, recent features\n- [Error handling](references\u002Ferror-handling.md) — provisioning, StackSet, SSO, and Guardrail failure remedies\n- [Diagnostic commands](references\u002Fdiagnostic-commands.md) — guardrail, baseline, alternate-contact, and compliance verification CLI\n\n## Domain\n\nAWS CloudOps \u002F AWS Control Tower Account Factory Governance & Account\nLifecycle Management.\n\n## AWS documentation\n\n- **Control Tower User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002F\n- **Account Factory** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Faccount-factory.html\n- **Guardrails** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Fguardrails.html\n- **Landing zone** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Flanding-zone.html\n- **SCP inheritance** — https:\u002F\u002Fdocs.aws.amazon.com\u002Forganizations\u002Flatest\u002Fuserguide\u002Forgs_manage_policies_scps.html\n- **Identity Center** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsinglesignon\u002Flatest\u002Fuserguide\u002F\n- **Permission sets** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsinglesignon\u002Flatest\u002Fuserguide\u002Fpermissionsetsconcept.html\n- **Service Catalog Account Factory** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Faccount-factory.html\n- **Alternate contacts** — https:\u002F\u002Fdocs.aws.amazon.com\u002Faccounts\u002Flatest\u002Freference\u002Fmanage-acct-update\u002Falternate-contacts.html\n- **CloudFormation StackSets** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSCloudFormation\u002Flatest\u002FUserGuide\u002Fwhat-is-cfnstacksets.html\n","# AWS Control Tower Account Factory Deployer\n\nAn AWS CloudOps agent skill that deploys AWS accounts via Control Tower\nAccount Factory with correct defaults. The skill walks the operator\nthrough Service Catalog product provisioning, OU placement, SSO\npermission set assignment, Guardrail inheritance verification, landing\nzone baseline conformance, email uniqueness, alternate contacts, account\ncustomization via StackSets, and account lifecycle management (vending,\nupdating, terminating), captures governance decisions, explains why each\ndefault matters, and emits a READY_TO_DEPLOY checklist with copy-\npasteable verification commands.\n\n## Activation keywords\n\ncreate AWS account Control Tower, account factory provision, vending\nnew account, Control Tower account enrollment, SSO permission set\nassignment, Guardrail SCP inheritance, Account Factory Service Catalog,\nControl Tower landing zone baseline, terminate AWS account, custom\naccount baseline.\n\n## STRICT output contract\n\nWhen this skill is invoked with an Account Factory provisioning request\n(create\u002Fvend an account, assign permission sets, verify Guardrails,\ncustomize baselines, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `ACCOUNT_FACTORY:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and\ndownstream provisioning pipelines rely on; deviating from the literal\nlabels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Account Factory via Service Catalog | Core vending mechanism |\n| Step 2 — Organizational Unit placement | OU topology |\n| Step 3 — SSO permission set assignment | Access control |\n| Step 4 — Guardrail inheritance (SCP, Detective, Config) | Compliance |\n| Step 5 — Landing zone baseline conformance | Baseline enforcement |\n| Step 6 — Email and account name uniqueness | Prerequisite check |\n| Step 7 — Alternate contacts | Operational metadata |\n| Step 8 — Account customization (custom product\u002FStackSets) | Baseline customization |\n| Step 9 — Account lifecycle (vending, updating, terminating) | Lifecycle management |\n| Step 10 — Compliance status verification | Post-provision audit |\n| Step 11 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fguardrails-and-baseline.md | Guardrail + baseline detail |\n| references\u002Fsso-and-lifecycle.md | SSO + lifecycle detail |\n| references\u002Fadvanced-patterns.md | Dependency graph + recent features |\n| references\u002Ferror-handling.md | Provisioning failure remedies |\n| references\u002Fdiagnostic-commands.md | Verification CLI detail |\n\n## Mindset\n\n**One-line takeaway:** Control Tower Account Factory vends AWS accounts\nthrough a Service Catalog product. Each account is placed in an\nOrganizational Unit, inherits Guardrails (SCP, Detective, Config) from\nthe OU and landing zone, gets SSO access via permission sets, and\nreceives a baseline (CloudFormation StackSets for logging, security,\nand operational standards). The Service Catalog product is the ONLY\nsupported way to create accounts that Control Tower manages — accounts\ncreated directly via Organizations `CreateAccount` are NOT enrolled in\nControl Tower and do NOT inherit Guardrails or baselines.\n\nThree misconceptions in full (raw Organizations ≠ Account Factory; Guardrails apply only to registered OUs; SSO assignment is a three-way binding): [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## Configuration dependency graph (novel heuristic)\n\nAccount Factory configurations are NOT independent. The landing zone\nmust exist before OUs can be registered. OUs must be registered before\naccounts can be enrolled. The Service Catalog product must be available\nbefore provisioning. SSO permission sets must exist before assignment.\nUse this graph to sequence provisioning.\n\nFull dependency table (landing zone → registered OU → SC product → account → SSO → guardrails → baseline → custom product → alternate contacts) plus cross-dependency gotchas: [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: landing zone baseline propagation\n\nBaseline propagation walkthrough (StackSet fan-out via AWSControlTowerExecutionRole, per-account baseline resources, incomplete-baseline failure mode): [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Expert heuristic: SCP inheritance from parent OU\n\nSCP hierarchy walkthrough (effective-SCP intersection, OU-move consequences) and the preventive\u002Fdetective\u002Fproactive Guardrail types: [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Expert heuristic: SSO permission set auto-assignment\n\nGroup-based auto-assignment flow and the O(groups × OUs) scaling model: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Control Tower landing zone enabled | Account Factory requires an active landing zone | `aws controltower list-landing-zones` |\n| Target OU registered with Control Tower | Only registered OUs get Guardrails and baselines | `aws controltower list-controls --control-source-ou \u003Cou-id>` |\n| Service Catalog product available | Account vending uses the Account Factory SC product | `aws servicecatalog search-products --filters FullTextSearch=Control` |\n| Unique account email | Duplicate emails fail provisioning | Check email pattern against existing accounts |\n| Unique account name | Duplicate names cause confusion in billing and console | `aws organizations list-accounts --query 'Accounts[*].Name'` |\n| Identity Center enabled | SSO assignment requires Identity Center | `aws sso-admin list-instances` |\n| Permission sets defined | Assignment requires existing permission sets | `aws sso-admin list-permission-sets --instance-arn \u003Carn>` |\n| Management account access | Account Factory runs from the management account | `aws sts get-caller-identity` (must be management account) |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Account Factory via Service Catalog\n\nAccount Factory vends accounts through a Service Catalog product. The\nproduct is auto-created by Control Tower during landing zone setup.\n\n**Provision a new account:**\n\n```bash\n# Get the Account Factory product ID\nPRODUCT_ID=$(aws servicecatalog search-products \\\n  --filters FullTextSearch=\"AWS Control Tower Account Factory Factory\" \\\n  --query 'ProductViewSummaries[0].ProductId' --output text)\n\n# Get the provisioning artifact ID (the \"version\" of the product)\nARTIFACT_ID=$(aws servicecatalog describe-product \\\n  --id \"$PRODUCT_ID\" \\\n  --query 'ProvisioningArtifacts[0].Id' --output text)\n\n# Provision the account\naws servicecatalog provision-product \\\n  --product-id \"$PRODUCT_ID\" \\\n  --provisioning-artifact-id \"$ARTIFACT_ID\" \\\n  --provisioned-product-name \"data-platform-prod\" \\\n  --provisioning-parameters '[\n    {\"Key\":\"AccountEmail\",\"Value\":\"aws+data-platform@company.com\"},\n    {\"Key\":\"AccountName\",\"Value\":\"data-platform-prod\"},\n    {\"Key\":\"ManagedOrganizationalUnit\",\"Value\":\"Custom (DataPlatform)\"},\n    {\"Key\":\"SSOUserEmail\",\"Value\":\"platform-lead@company.com\"},\n    {\"Key\":\"SSOUserFirstName\",\"Value\":\"Platform\"},\n    {\"Key\":\"SSOUserLastName\",\"Value\":\"Team\"}\n  ]'\n```\n\n**Provisioning parameters (required):**\n\n| Parameter | Description | Constraints |\n|---|---|---|\n| AccountEmail | Root email for the account | Globally unique; not used by any other AWS account |\n| AccountName | Display name | Unique within the org |\n| ManagedOrganizationalUnit | Target OU (name or SelectWithExist) | Must be a registered OU |\n| SSOUserEmail | Initial SSO admin email | Must be unique in Identity Center |\n| SSOUserFirstName | Initial SSO admin first name | Non-empty |\n| SSOUserLastName | Initial SSO admin last name | Non-empty |\n\n**Provisioning is asynchronous** — typically 5-30 minutes. Poll the\nprovisioned product status:\n\n```bash\naws servicecatalog describe-provisioned-product \\\n  --name \"data-platform-prod\" \\\n  --query 'ProvisionedProductDetail.Status' --output text\n# Wait for status: AVAILABLE\n```\n\n## Step 2 — Organizational Unit placement\n\nThe target OU determines Guardrail inheritance and baseline StackSet\ndeployment. The OU must be registered with Control Tower.\n\n**Registered vs. unregistered OUs:**\n\n| OU type | Guardrails | Baseline | SSO auto-provision |\n|---|---|---|---|\n| Registered with Control Tower | Full SCP inheritance | StackSets auto-deploy | Yes |\n| Unregistered (raw org OU) | No Guardrails | No baseline | No |\n\n**List registered OUs:**\n\n```bash\n# List all registered OUs in the landing zone\naws controltower list-enabled-controls \\\n  --control-source-ou \u003Croot-ou-id> \\\n  --query 'EnabledControls[*].ControlIdentifier' --output table\n```\n\n**Place the account in the correct OU:**\n\nThe OU is specified via the `ManagedOrganizationalUnit` parameter in\nthe Service Catalog provisioning call. The format is the OU name as\nshown in Control Tower (e.g., \"Custom (DataPlatform)\") or the OU's\nSelectWithExist path.\n\n**Moving an account between OUs** (after creation):\n\n```bash\naws organizations move-account \\\n  --account-id \"123456789012\" \\\n  --source-parent-id \"ou-aaa-source111\" \\\n  --destination-parent-id \"ou-bbb-dest222\"\n```\n\n**Critical:** moving an account to a different OU immediately changes\nits inherited SCPs. Moving from a strict OU to a permissive OU can\nexpose the account to previously-blocked actions.\n\n## Step 3 — SSO permission set assignment\n\nSSO (Identity Center) provides federated access to accounts via\npermission sets. Assignment is a three-way binding: principal (user or\ngroup) + permission set + account.\n\nCreate\u002Fattach\u002Fassign\u002Fprovision CLI sequence and the provisioning-is-separate-from-assignment rule: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 4 — Guardrail inheritance (SCP, Detective, Config)\n\nGuardrails are inherited from the OU level. An account in a registered\nOU automatically gets:\n\n| Guardrail type | Implementation | Example |\n|---|---|---|\n| Preventive | SCP in Organizations | Deny leaving org, deny disabling CloudTrail |\n| Detective | Config rule + Security Hub control | Detect publicly readable S3 bucket |\n| Proactive | Config rule | Detect non-compliant resource creation |\n\nSCP and Config-rule verification CLI: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 5 — Landing zone baseline conformance\n\nControl Tower deploys a baseline (set of StackSets) to every enrolled\naccount. The baseline includes:\n\n| Baseline StackSet | Purpose | Target |\n|---|---|---|\n| AWSControlTowerLogging | CloudTrail trail to logging account | All enrolled accounts |\n| AWSControlTowerSecurity | Security Hub, Config rules | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CLOUDTRAIL | CloudTrail baseline | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CONFIG | Config recorder baseline | All enrolled accounts |\n| AWSControlTowerBP-BASELINE-CLOUDWATCH | CloudWatch alarms baseline | All enrolled accounts |\n\nStackSet instance-status check and failure triage: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 6 — Email and account name uniqueness\n\n**Email uniqueness:** the root email for each AWS account must be\nglobally unique across ALL AWS accounts (including accounts in other\norgs and closed accounts). AWS rejects provisioning with a duplicate\nemail.\n\nEmail alias pattern, examples, and the uniqueness-check CLI: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 7 — Alternate contacts\n\nAlternate contacts provide operational metadata for billing, security,\nand operational notifications. They are set per-account via the Account\nManagement API.\n\nput-alternate-contact CLI for BILLING, SECURITY, and OPERATIONS contacts: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n**Critical:** alternate contacts are NOT inherited from the OU or org\nlevel. They must be set per-account. Automate this in the account\ncustomization pipeline (Step 8).\n\n## Step 8 — Account customization (custom product\u002FStackSets)\n\nBeyond the default baseline, accounts can be customized via custom\nService Catalog products that deploy additional CloudFormation\nStackSets.\n\n**Custom product pattern:**\n\n```text\nCustom account customization flow:\n  1. Create a CloudFormation template with account-specific resources\n     (VPC, KMS keys, IAM roles, CloudWatch dashboards, etc.)\n  2. Publish as a Service Catalog product in the Account Factory portfolio\n  3. When vending an account, provision BOTH the standard Account Factory\n     product AND the custom product\n  4. Control Tower's StackSets deploy the custom resources alongside the\n     baseline\n```\n\nCustom StackSet create CLI and the customization-template flow: [Guardrails and baseline](references\u002Fguardrails-and-baseline.md).\n\n## Step 9 — Account lifecycle (vending, updating, terminating)\n\nBaseline update, terminate-provisioned-product, and the SUSPENDED-then-closed-after-90-days lifecycle: [SSO and lifecycle](references\u002Fsso-and-lifecycle.md).\n\n## Step 10 — Compliance status verification\n\nAfter provisioning, verify the account's compliance status:\n\nOU placement, SCP, Config, Security Hub, and SSO verification CLI: [Diagnostic commands](references\u002Fdiagnostic-commands.md).\n\n## Step 11 — Recent features\n\n2023-2026 features — Account Factory Customization, group-based auto-assignment, email validation API, Landing Zone 3.0+, API termination, StackSet alternate contacts: [Advanced patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER create accounts via raw Organizations `CreateAccount` when\n   Control Tower is in use.** Organizations-created accounts are NOT\n   enrolled in Control Tower. They miss Guardrails, baselines, and SSO.\n   Always use the Account Factory Service Catalog product for managed\n   accounts.\n\n2. **NEVER place accounts in unregistered OUs.** Only registered OUs\n   get Guardrails (SCP, Detective, Config). An account in an\n   unregistered OU is a compliance gap. Always verify the OU is\n   registered with Control Tower before vending.\n\n3. **NEVER use duplicate root emails.** The root email must be globally\n   unique. Duplicate emails cause provisioning failures. Use a\n   consistent alias pattern (e.g., `aws+\u003Cou>-\u003Cname>@company.com`).\n\n4. **NEVER assume SCPs persist after moving accounts between OUs.**\n   SCPs are inherited from the OU. Moving an account to a different OU\n   immediately changes its effective SCPs. Always verify SCPs after any\n   OU move.\n\n5. **NEVER skip baseline StackSet verification.** Control Tower deploys\n   baselines automatically, but StackSets can fail silently. An\n   account with a failed StackSet has no CloudTrail, Config, or\n   Security Hub — a critical compliance gap. Always verify StackSet\n   deployment status.\n\n6. **NEVER assign SSO permission sets without provisioning.** Creating\n   a permission set and assigning it to a principal does NOT take\n   effect until the permission set is provisioned to the account.\n   Always call `provision-permission-set` after assignment.\n\n7. **NEVER forget alternate contacts.** They are not inherited from\n   the OU or org level. Without billing\u002Fsecurity\u002Foperations contacts,\n   AWS support and billing notifications go to the root email only.\n   Always set all three alternate contacts per account.\n\n8. **NEVER assume Account Factory termination deletes the AWS account.**\n   Terminating the Service Catalog product dis-enrolls the account\n   from Control Tower but does NOT close the AWS account. The account\n   remains in SUSPENDED state for 90 days before permanent closure.\n   Close the account separately if immediate removal is needed.\n\n9. **NEVER use individual user SSO assignments at scale.** Assign\n   permission sets to GROUPS, not individual users. Group-based\n   assignment scales to O(groups x OUs) instead of O(users x accounts).\n   Add users to groups; groups inherit permission sets.\n\n10. **NEVER skip landing zone version checks.** Outdated landing zone\n    versions silently lack newer Guardrails and features. Always check\n    the landing zone version and upgrade before vending accounts that\n    require the latest Guardrails.\n\n## Output format\n\n```text\nACCOUNT_FACTORY: \u003Caccount-name> (\u003Caccount-id>) in OU \u003Cou-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Account email: \u003Cemail> — UNIQUE (globally)\n  [✓|✗] Account name: \u003Cname> — UNIQUE (within org)\n  [✓|✗] Target OU: \u003Cou-name> (\u003Cou-id>) — REGISTERED with Control Tower\n  [✓|✗] Service Catalog product: \u003Cproduct-id> — AVAILABLE\n  [✓|✗] Account provisioned: \u003Caccount-id> — ACTIVE\n  [✓|✗] Guardrails (SCP): \u003Ccount> preventive controls inherited from OU\n  [✓|✗] Guardrails (Detective): Config rules deployed in account\n  [✓|✗] Guardrails (Config): baseline StackSets — \u003Call\u002Ffailed list>\n  [✓|✗] Baseline StackSets: AWSControlTowerLogging — DEPLOYED, AWSControlTowerSecurity — DEPLOYED\n  [✓|✗] SSO: Identity Center instance \u003Cinstance-arn>\n  [✓|✗] Permission sets: \u003Clist> assigned to \u003Cgroup> for this account\n  [✓|✗] SSO provisioning: permission set provisioned — SUCCEEDED\n  [✓|✗] Alternate contacts: BILLING ✓, SECURITY ✓, OPERATIONS ✓\n  [✓|✗] Custom baseline: \u003Cstackset-name> — DEPLOYED\n  [✓|✗] Compliance status: \u003Ccompliant | non-compliant (gaps listed)>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws organizations describe-account --account-id \u003Caccount-id>\n  aws organizations list-policies-for-target --target-id \u003Caccount-id> --filter SERVICE_CONTROL_POLICY\n  aws cloudformation list-stack-instances --stack-set-name AWSControlTowerLogging\n  aws sso-admin list-account-assignments --instance-arn \u003Cinstance-arn> --account-id \u003Caccount-id>\n```\n\n### Worked example — data platform account with SSO and Guardrails\n\n```text\nACCOUNT_FACTORY: data-platform-prod (123456789012) in OU DataPlatform (ou-bbb-ccc)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Account email: aws+prod-data-platform@company.com — UNIQUE\n  [✓] Account name: data-platform-prod — UNIQUE\n  [✓] Target OU: Custom (DataPlatform) (ou-bbb-ccc) — REGISTERED\n  [✓] Service Catalog product: prod-aaa111 — AVAILABLE\n  [✓] Account provisioned: 123456789012 — ACTIVE\n  [✓] Guardrails (SCP): 8 preventive controls inherited from OU\n  [✓] Guardrails (Detective): 12 Config rules deployed\n  [✓] Guardrails (Config): baseline StackSets — all DEPLOYED\n  [✓] Baseline StackSets: AWSControlTowerLogging — DEPLOYED, AWSControlTowerSecurity — DEPLOYED\n  [✓] SSO: Identity Center instance arn:aws:sso:::instance\u002Fssoins-12345\n  [✓] Permission sets: DataEngineerAccess assigned to DataPlatformTeam group\n  [✓] SSO provisioning: DataEngineerAccess provisioned — SUCCEEDED\n  [✓] Alternate contacts: BILLING ✓, SECURITY ✓, OPERATIONS ✓\n  [✓] Custom baseline: CustomBaseline-VPC — DEPLOYED\n  [✓] Compliance status: compliant\n  [✓] Tags: Environment=production, OU=DataPlatform, Owner=PlatformTeam\nVERIFICATION_COMMANDS:\n  aws organizations describe-account --account-id 123456789012\n  aws organizations list-policies-for-target --target-id 123456789012 --filter SERVICE_CONTROL_POLICY\n  aws cloudformation list-stack-instances --stack-set-name AWSControlTowerLogging\n  aws sso-admin list-account-assignments --instance-arn arn:aws:sso:::instance\u002Fssoins-12345 --account-id 123456789012\n```\n\n## Error handling\n\nStuck provisioning, failed baseline StackSet, unprovisioned permission set, missing Guardrails, unset alternate contacts: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Guardrails and baseline](references\u002Fguardrails-and-baseline.md) — guardrail types, OU registration, baseline StackSets, SCP-inheritance and propagation heuristics, custom StackSets\n- [SSO and lifecycle](references\u002Fsso-and-lifecycle.md) — permission sets, group assignment, vending\u002Fupdating\u002Fterminating, email management\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — provisioning misconceptions, configuration dependency graph, recent features\n- [Error handling](references\u002Ferror-handling.md) — provisioning, StackSet, SSO, and Guardrail failure remedies\n- [Diagnostic commands](references\u002Fdiagnostic-commands.md) — guardrail, baseline, alternate-contact, and compliance verification CLI\n\n## Domain\n\nAWS CloudOps \u002F AWS Control Tower Account Factory Governance & Account\nLifecycle Management.\n\n## AWS documentation\n\n- **Control Tower User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002F\n- **Account Factory** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Faccount-factory.html\n- **Guardrails** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Fguardrails.html\n- **Landing zone** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Flanding-zone.html\n- **SCP inheritance** — https:\u002F\u002Fdocs.aws.amazon.com\u002Forganizations\u002Flatest\u002Fuserguide\u002Forgs_manage_policies_scps.html\n- **Identity Center** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsinglesignon\u002Flatest\u002Fuserguide\u002F\n- **Permission sets** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsinglesignon\u002Flatest\u002Fuserguide\u002Fpermissionsetsconcept.html\n- **Service Catalog Account Factory** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcontroltower\u002Flatest\u002Fuserguide\u002Faccount-factory.html\n- **Alternate contacts** — https:\u002F\u002Fdocs.aws.amazon.com\u002Faccounts\u002Flatest\u002Freference\u002Fmanage-acct-update\u002Falternate-contacts.html\n- **CloudFormation StackSets** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSCloudFormation\u002Flatest\u002FUserGuide\u002Fwhat-is-cfnstacksets.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, control-tower, account-factory, cloudops, deploy, governance, provisioning, landing-zone, scp, guardrails, sso, organizations","1","Jacky Chan — AWS Community Builder","aws-cloudops","Governance","0.1.0","aws, control tower, account factory, service catalog, cloudops, deploy, provisioning, landing zone, scp, guardrails, sso, permission set, organizations, stacksets, baseline, account vending, compliance, alternate contacts","deploy","high","false","capability","Invoke when the user wants to create AWS accounts via Control Tower Account Factory, vend accounts to teams, place accounts in Organizational Units, assign SSO permission sets, verify Guardrail (SCP\u002FDetective\u002FConfig) inheritance, customize account baselines via CloudFormation StackSets, update account baselines, or terminate accounts. Do NOT invoke for AWS Organizations account creation outside Control Tower (use organizations-account-deployer), Control Tower landing zone setup\u002Fupgrade (use controltower-control- auditor), or SCP authoring (use organizations-scp-deployer).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with servicecatalog, controltower, organizations, and sso-admin access. Works with Terraform aws_controltower_account \u002F aws_organizations_ account \u002F aws_ssoadmin_permission_set resources and CloudFormation AWS::ServiceCatalog::CloudFormationProvisionedProduct templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Faccount-factory-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill account-factory-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill account-factory-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill account-factory-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5612,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Faccount-termination.md",503,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fbaselines\u002Faccount-termination.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fcustom-baseline-stacksets.md",765,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fbaselines\u002Fcustom-baseline-stacksets.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fgroup-sso-auto-assignment.md",711,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fbaselines\u002Fgroup-sso-auto-assignment.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fstandard-account-vending.md",689,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fbaselines\u002Fstandard-account-vending.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Funregistered-ou-prerequisite.md",826,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fbaselines\u002Funregistered-ou-prerequisite.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1784,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9227,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Faccount-termination.md",453,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fprompts\u002Faccount-termination.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fcustom-baseline-stacksets.md",571,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fprompts\u002Fcustom-baseline-stacksets.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fgroup-sso-auto-assignment.md",518,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fprompts\u002Fgroup-sso-auto-assignment.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fstandard-account-vending.md",623,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fprompts\u002Fstandard-account-vending.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Funregistered-ou-prerequisite.md",435,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fevals\u002Fprompts\u002Funregistered-ou-prerequisite.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",8471,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",7523,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fdiagnostic-commands.md",3236,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1569,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fguardrails-and-baseline.md",13809,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Freferences\u002Fguardrails-and-baseline.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fsso-and-lifecycle.md",18122,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Freferences\u002Fsso-and-lifecycle.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4440,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Faccount-factory-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]