[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4YVYGDGQ2S6F1R3K4641T":3,"skill-same:01M7A4YVYGDGQ2S6F1R3K4641T":142},{"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},"01M7A4YVYGDGQ2S6F1R3K4641T","cloudhsm-cluster-deployer",null,"Provisions AWS CloudHSM clusters with production defaults: cluster creation in a VPC with subnets across 2+ AZs for HA, HSM instance creation, one-time cluster activation (CSR signing, self-signed cert), crypto officer\u002Fuser management (mu, password policies), HSM backups (daily automatic + on-demand), cross-region backup copy, HA across AZs, PKCS#11\u002FJCE\u002FPCSC library integration, SSL\u002FTLS offload, FIPS 140-2 Level 3 compliance, network security group (sg-xxx), CN-to-cluster-ID mapping, and degradation recovery (create replacement, sync). Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a CloudHSM cluster, activating an HSM, managing crypto officers, configuring backups, or recovering from HSM degradation. Triggers: create cloudhsm cluster, activate cloudhsm, HSM instance, crypto officer, cloudhsm backup, cross-region backup, PKCS#11, JCE, FIPS 140-2 Level 3, CN-to-cluster-ID.","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\u002Fcloudhsm-cluster-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloudhsm-cluster-deployer\ndescription: 'Provisions AWS CloudHSM clusters with production defaults: cluster creation in a VPC with subnets across 2+ AZs for HA, HSM instance creation, one-time cluster activation (CSR signing, self-signed cert), crypto officer\u002Fuser management (mu, password policies), HSM backups (daily automatic + on-demand), cross-region backup copy, HA across AZs, PKCS#11\u002FJCE\u002FPCSC library integration, SSL\u002FTLS offload, FIPS 140-2 Level 3 compliance, network security group (sg-xxx), CN-to-cluster-ID mapping, and degradation recovery (create replacement, sync). Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a CloudHSM cluster, activating an HSM, managing crypto officers, configuring backups, or recovering from HSM degradation. Triggers: create cloudhsm cluster, activate cloudhsm, HSM instance, crypto officer, cloudhsm backup, cross-region backup, PKCS#11, JCE, FIPS 140-2 Level 3, CN-to-cluster-ID.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with cloudhsm, ec2, iam, sts access, plus the CloudHSM client (config -a) and key_mgmt_util \u002F cloudhsm_mgmt_util for crypto officer workflows. Works with Terraform aws_cloudhsm_v2_cluster \u002F aws_cloudhsm_v2_hsm resources and CloudFormation AWS::CloudHSM::Cluster \u002F AWS::CloudHSM::HSM 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: Security\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, cloudhsm, hsm, cloudops, deploy, security, provisioning, fips-140-2, pkcs11, jce, cluster-activation, hsm-backup\n  dependencies: aws-orchestrator\n  keywords: aws, cloudhsm, hsm, cloudops, deploy, provisioning, security, fips 140-2, pkcs#11, jce, crypto officer, cluster activation, hsm backup, cross-region backup, ha\n  when_to_use: Invoke when the user wants to create an AWS CloudHSM cluster, activate an HSM (CSR → self-signed cert), create HSM instances across 2+ AZs for HA, manage crypto officers and users, configure backups (daily + on-demand + cross-region copy), integrate PKCS#11\u002FJCE\u002FPCSC libraries, offload SSL\u002FTLS, or recover from HSM degradation. Do NOT invoke for AWS KMS (use kms-key-deployer), ACM (use acm-certificate-deployer), or AWS Signer (use signer-signing-profile-deployer).\n---\n\n# CloudHSM Cluster Deployer\n\nAn AWS CloudOps agent skill that provisions AWS CloudHSM clusters\nwith correct production defaults: cluster creation in a VPC with\nsubnets across 2+ AZs, HSM instance creation, one-time cluster\nactivation (CSR → self-signed cert), crypto officer\u002Fuser management,\nbackups, HA, PKCS#11\u002FJCE integration, FIPS 140-2 Level 3 posture,\nand degradation recovery. Captures every configuration decision and\nemits a READY_TO_DEPLOY checklist with verification commands.\n\n## Activation keywords\n\ncreate CloudHSM cluster, activate CloudHSM, HSM instance, crypto\nofficer, CloudHSM backup, cross-region backup, PKCS#11, JCE, FIPS\n140-2 Level 3, CN-to-cluster-ID, HSM degradation recovery.\n\n## STRICT output contract\n\nWhen this skill is invoked with a CloudHSM-provisioning request\n(create a cluster, activate an HSM, add an HSM instance, configure\nbackups, or recover from degradation), the agent MUST respond with\nthe READY_TO_DEPLOY checklist defined in \"Output format\" using the\nliteral all-caps labels `CLOUDHSM:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the checklist\n(marked `[✗]`), and `READY_TO_DEPLOY` MUST NOT also appear. The\nresponse uses these literal labels: `CLOUDHSM: \u003Ccluster-id>\n(\u003Csubnet-az-list>)`, then `VERDICT:`, then `CHECKLIST:` with status\nmarkers, then `VERIFICATION_COMMANDS:` with indented\n`aws cloudhsmv2 ...` and `aws ec2 ...` commands.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Cluster creation (VPC, 2+ AZ subnets) | Core topology |\n| Step 2 — HSM instance creation | Per-AZ HA |\n| Step 3 — Cluster activation (one-time CSR) | One-time gate |\n| Step 4 — Crypto officer\u002Fuser management | CO password + users |\n| Step 5 — HSM backups (daily + on-demand) | Backup posture |\n| Step 6 — Cross-region backup copy | DR posture |\n| Step 7 — HA across AZs | Availability |\n| Step 8 — PKCS#11\u002FJCE\u002FPCSC integration | Client libraries |\n| Step 9 — SSL\u002FTLS offload | Workload integration |\n| Step 10 — FIPS 140-2 Level 3 compliance | Compliance |\n| Step 11 — Network security group (sg-xxx) | Network isolation |\n| Step 12 — CN-to-cluster-ID mapping | Client discovery |\n| Step 13 — Degradation recovery | Replace + sync |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fcluster-activation-and-users.md | Activation + CO detail |\n| references\u002Fbackups-and-ha.md | Backups + HA + recovery detail |\n| references\u002Fadvanced-patterns.md | Heuristics + integration detail |\n| references\u002Ferror-handling.md | API errors + remedies |\n\n## Mindset\n\n**One-line takeaway:** An AWS CloudHSM cluster is a single-tenant\nHSM fleet inside your VPC, validated to FIPS 140-2 Level 3.\nCreation gives you a `cluster-id`; creating the FIRST HSM produces\na CSR that you sign once to issue the cluster's customer certificate\n— this activation is one-time and the resulting trust root is what\nevery subsequent HSM inherits. Production clusters need HSMs in\n≥2 AZs for HA, and the crypto officer (CO) password is NOT\nrecoverable — lose it (or lose quorum) and the cluster's key\nmaterial is unrecoverable.\n\nThree misconceptions dominate CloudHSM misdesign at provisioning\ntime:\n\n- **\"Create a cluster and you're done.\"** You're not. After\n  `create-cluster` you must (a) create at least one HSM instance\n  (`create-hsm`), (b) wait for the HSM to be `ACTIVE`, (c) sign the\n  CSR the HSM produces and upload the signed cert + your customerCA\n  certificate to activate the cluster. Until activated, no CO, no\n  users, no crypto operations.\n\n- **\"One HSM is enough for HA.\"** It isn't. A single HSM is a\n  single point of failure. AWS CloudHSM supports HA by adding HSM\n  instances in different AZs to the SAME cluster — they auto-sync\n  key material. Production needs ≥2 AZs.\n\n- **\"The CO password can be reset like a normal password.\"** It\n  cannot. CloudHSM crypto officer credentials are NOT recoverable.\n  Lose the CO password (or the CO user) and you lose access to the\n  key material. Maintain quorum and a secure offline record. No\n  \"forgot password\" flow exists.\n\n## Configuration dependency graph (novel heuristic)\n\nCloudHSM configurations are NOT independent. The cluster needs a\nVPC with subnets in 2+ AZs. The first HSM instance produces the\nCSR. Activation (CSR → self-signed cert) is a one-time gate that\nunlocks CO\u002Fuser management. Backups are taken per-cluster, copied\ncross-region for DR. HA requires ≥2 AZs. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Cluster | VPC + ≥2 subnet-AZs; `cloudhsm:CreateCluster` | cluster-id is fixed; subnet list cannot be expanded later | cluster-id for HSM creation |\n| HSM instance | cluster-id; AZ in subnet list; `cloudhsm:CreateHsm` | first HSM emits a CSR; HSM unreachable until activation | CSR for activation |\n| Cluster activation | first HSM `ACTIVE`; CSR signed by in-house CA | ONE-TIME — customer cert becomes trust root for every subsequent HSM | CO\u002Fuser mgmt; all crypto ops |\n| Crypto officer (CO) | cluster activated; CO logs in via `cloudhsm_mgmt_util` (mu) | CO password NOT recoverable; lose CO + quorum = lose key material | user creation, key mgmt, policy |\n| HSM user (CU) | cluster activated; CO creates users via `mu` or `key_mgmt_util` | users are cluster-scoped; same username\u002Fpassword on every HSM (sync) | key use via PKCS#11\u002FJCE clients |\n| Daily automatic backup | cluster activated; 5-min delta + daily snapshot | backups cluster-scoped; retention configurable; hold key material | point-in-time restore |\n| On-demand backup | cluster activated; via mu `createBackup` | snapshot at time T | pre-change safety net |\n| Cross-region backup copy | destination region enabled; `cloudhsm:CopyBackupToRegion` | copy is one-way; restores in destination create a new cluster | DR in second region |\n| HA across AZs | cluster activated; ≥2 HSM instances in different AZs | key material auto-syncs across HSMs; client lib load-balances | AZ failure tolerance |\n| PKCS#11\u002FJCE client | cluster activated; client configured with CN-to-cluster-ID | client uses customer CA cert to trust cluster; wrong mapping = failure | workload crypto operations |\n| Network security group | SG attached to CloudHSM ENIs; inbound from workload subnets | SG enforced at ENI; too-broad CIDR = attack surface | network isolation |\n| CN-to-cluster-ID mapping | registered via `configure -a \u003Cip>` or DNS CNAME | client uses CN to verify cluster identity; mismatch = TLS failure | client bootstrap |\n\n**The activation-is-one-time row is the one a baseline model\nmisses.** A naive answer treats activation as repeatable or skips\nit. In reality the customer certificate you upload after signing the\nCSR becomes the cluster's permanent trust root; every subsequent\nHSM inherits it. The CO-password-not-recoverable row is the second\nmost missed: operators assume an AWS-side reset path that does not\nexist.\n\n**Cross-dependency gotchas:**\n- Activation is one-time. After uploading the signed customer\n  certificate, you CANNOT re-activate under a different CA without\n  a new cluster (restoring from backup).\n- HA requires ≥2 AZs in the SAME cluster. Two clusters in two AZs\n  do NOT sync key material.\n- Cross-region backup copy creates a restorable backup in the\n  destination region; it does NOT create a running cluster. Restore\n  = `restore-backup` → new cluster-id in destination.\n- CloudHSM ENI security group must allow inbound from workload\n  subnets on HSM service ports (TCP 22 for SSH-less mu, TCP 17578\n  for management, TCP 2223 for client). Use narrowest possible\n  CIDR.\n\n## Prerequisites (verify before provisioning)\n\nBefore provisioning, verify these prerequisites. If any are missing,\nthe verdict is **PREREQUISITES_MISSING** and the specific gap must\nbe cited.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| VPC + ≥2 subnets in different AZs | HA requires ≥2 AZs in the same cluster | `aws ec2 describe-subnets --filters Name=vpc-id,Values=\u003Cvpc>` |\n| Security group for CloudHSM ENIs | Network isolation; workload subnets only | `aws ec2 describe-security-groups` |\n| `cloudhsm:CreateCluster`, `cloudhsm:CreateHsm` IAM | Required to create cluster + HSM | `aws iam simulate-principal-policy ...` |\n| Service-linked role (`AWSServiceRoleForCloudHSM`) | CloudHSM auto-creates; if deleted, recreate | `aws iam get-role --role-name AWSServiceRoleForCloudHSM` |\n| HSM type chosen (`hsm1.medium`) | Instance type for the HSM | Confirm capacity needs |\n| Backup retention policy decision | Daily snapshots; retention in days | Confirm policy intent |\n| Cross-region destination (if DR) | Destination region must be enabled | `aws cloudhsmv2 describe-regions-settings --region \u003Cdst>` |\n| Customer CA (for activation) | Bootstrap CA to sign the first CSR | Confirm in-house CA or self-sign |\n| CO password storage plan | CO password is not recoverable | Confirm secret store (Secrets Manager \u002F KMS vault) |\n| CloudHSM client installed (for activation) | CloudHSM client + key_mgmt_util + cloudhsm_mgmt_util | `cloudhsm-cli version` |\n\nIf any prerequisite is missing, output\n`VERDICT: PREREQUISITES_MISSING` and cite the specific gap.\n\n## Step 1 — Cluster creation (VPC, 2+ AZ subnets)\n\nThe cluster is a regional resource that holds HSM instances.\nSpecify the subnet list (one per AZ) and a security group.\n\n```bash\n# Create the cluster (subnet-az list fixes the HA topology)\nCLUSTER_ID=$(aws cloudhsmv2 create-cluster \\\n  --hsm-type hsm1.medium \\\n  --subnet-ids subnet-aaa11122 subnet-bbb22233 subnet-ccc33344 \\\n  --security-group-id sg-cloudhsm-prod \\\n  --query 'Cluster.ClusterId' --output text --region us-east-1)\n\n# Verify cluster state (CREATE_IN_PROGRESS → UNINITIALIZED)\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[*].{Id:ClusterId, State:State, Subnets:SubnetMapping, Type:HsmType}' \\\n  --output table --region us-east-1\n```\n\n**Constraint:** the subnet list CANNOT be expanded after cluster\ncreation. Plan the AZ topology up front. Adding a new AZ requires a\nnew cluster.\n\n## Step 2 — HSM instance creation\n\nCreate at least one HSM (per AZ) in the cluster. The first HSM\nemits the CSR for activation.\n\n```bash\n# Create HSMs — one per AZ for HA\naws cloudhsmv2 create-hsm --cluster-id \"$CLUSTER_ID\" --availability-zone us-east-1a \\\n  --ip-address 10.0.1.10 --region us-east-1\naws cloudhsmv2 create-hsm --cluster-id \"$CLUSTER_ID\" --availability-zone us-east-1b \\\n  --ip-address 10.0.2.10 --region us-east-1\n\n# Verify each HSM reaches ACTIVE\naws cloudhsmv2 describe-clusters --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].Hsms[*].{Id:HsmId, AZ:AvailabilityZone, State:State, ENI:EniIp}' \\\n  --output table --region us-east-1\n```\n\nEach HSM gets an ENI in the specified subnet. State transitions:\n`CREATE_IN_PROGRESS → ACTIVE`. Once the first HSM is `ACTIVE`, the\nCSR is available via `describe-clusters`.\n\n## Step 3 — Cluster activation (one-time CSR → self-signed cert)\n\nActivation is the one-time gate that unlocks CO\u002Fuser management.\n\n```bash\n# 1. Fetch the CSR from the first ACTIVE HSM\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].Certificates.ClusterCertificate' \\\n  --output text --region us-east-1 > cluster.csr\n\n# 2. Sign the CSR with your in-house CA (or self-sign for bootstrap)\nopenssl x509 -req -days 3650 -in cluster.csr \\\n  -CA customerCA.crt -CAkey customerCA.key -set_serial 01 \\\n  -out customerCertificate.crt\n\n# 3. Upload signed cert + CA cert to activate the cluster\naws cloudhsmv2 initialize-cluster \\\n  --cluster-id \"$CLUSTER_ID\" \\\n  --signed-cert fileb:\u002F\u002FcustomerCertificate.crt \\\n  --trust-anchor fileb:\u002F\u002FcustomerCA.crt --region us-east-1\n\n# 4. Verify state transitions to INITIALIZED → ACTIVE\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].{State:State, Cert:Certificates}' \\\n  --output table --region us-east-1\n```\n\n**Critical:** activation is ONE-TIME. After this, the customer\ncertificate is the trust root. To change CAs, restore from backup\ninto a new cluster.\n\n## Step 4 — Crypto officer\u002Fuser management\n\nFull procedure: [cluster-activation-and-users.md](references\u002Fcluster-activation-and-users.md). Log in via `cloudhsm_mgmt_util` (mu) over the ENI; create the first CO (`admin`) and CUs. The CO password is the crown-jewel secret — store in Secrets Manager (customer-managed KMS key) and keep >=2 COs for quorum.\n\n## Step 5 — HSM backups (daily + on-demand)\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). Automatic backups every ~5 minutes (delta) plus a daily snapshot; on-demand backups via the mu `createBackup` command. Backups are cluster-scoped; retention is configurable per cluster.\n\n## Step 6 — Cross-region backup copy\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). `copy-backup-to-region` for DR — the copy is one-way and restore in the destination creates a NEW cluster-id (cold DR, not a hot replica).\n\n## Step 7 — HA across AZs\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). 2 AZs tolerates 1 AZ failure (minimum production posture); 3 AZs tolerates 1 failure during a replace (recommended). Two separate clusters do NOT sync key material.\n\n## Step 8 — PKCS#11\u002FJCE\u002FPCSC library integration\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). The client uses the customer CA certificate (uploaded at activation) to trust the cluster — keep the bundle current on every client host.\n\n## Step 9 — SSL\u002FTLS offload\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). Generate the keypair inside the HSM; the web server holds only the certificate — the private key never leaves the HSM.\n\n## Step 10 — FIPS 140-2 Level 3 compliance\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). In-HSM operations only; CloudTrail control-plane + HSM data-plane audit trail; narrow SG inbound; CO quorum for destructive operations.\n\n## Step 11 — Network security group (sg-xxx)\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). Inbound TCP 2223 (client) from workload subnets only; TCP 17578 (management utility); TCP 22 (mu). Use the narrowest CIDR — never `0.0.0.0\u002F0`.\n\n## Step 12 — CN-to-cluster-ID mapping\n\nFull procedure: [cluster-activation-and-users.md](references\u002Fcluster-activation-and-users.md). Register the mapping via `configure -a \u003Ceni-ip>` or a DNS CNAME; a wrong mapping fails the client TLS handshake.\n\n## Step 13 — Degradation recovery (create replacement, sync)\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). Create the replacement HSM FIRST, wait for ACTIVE + sync, then delete the degraded HSM — never drop below 1 ACTIVE HSM.\n\n## NEVER do these things\n\n1. **NEVER deploy a production CloudHSM cluster with HSMs in only\n   one AZ.** Single-AZ is a single point of failure. Use ≥2 AZs.\n\n2. **NEVER skip cluster activation.** `create-cluster` +\n   `create-hsm` leaves the cluster UNINITIALIZED. Without activation\n   (CSR → signed cert upload), no CO, no users, no crypto.\n\n3. **NEVER treat activation as repeatable.** The customer certificate\n   is the cluster's permanent trust root. To change CAs, restore\n   from backup into a new cluster.\n\n4. **NEVER lose the CO password.** CloudHSM has NO password reset\n   flow. Lose CO + lose quorum = lose key material. Maintain ≥2 COs\n   and a secure offline record.\n\n5. **NEVER use two clusters as HA.** Two clusters do NOT sync key\n   material. HA is intra-cluster: ≥2 HSMs in different AZs in the\n   SAME cluster.\n\n6. **NEVER expand the subnet-AZ list after cluster creation.** The\n   subnet list is fixed at create-cluster time. Adding an AZ\n   requires a new cluster.\n\n7. **NEVER open CloudHSM ENI security group to `0.0.0.0\u002F0`.** Use\n   the narrowest workload-subnet CIDR.\n\n8. **NEVER export key material to workload memory if you need\n   FIPS 140-2 Level 3.** Use in-HSM operations via PKCS#11\u002FJCE.\n\n9. **NEVER assume cross-region backup copy creates a hot replica.**\n   Copy is one-way. Restore creates a NEW cluster-id; cold DR, not\n   a running failover target.\n\n10. **NEVER delete the degraded HSM before the replacement is\n    ACTIVE.** Dropping below 1 ACTIVE HSM loses HA. Create\n    replacement first; verify sync; then delete.\n\n11. **NEVER confuse CloudHSM with KMS.** CloudHSM is single-tenant\n    hardware, FIPS 140-2 Level 3, BYO client libraries, you manage\n    users\u002Fkeys. KMS is multi-tenant regional, FIPS 140-2 Level 2\n    (mostly), AWS manages the HSM backing.\n\n## Output format\n\n```text\nCLOUDHSM: \u003Ccluster-id> (\u003Caz-list>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Cluster ID: \u003Ccluster-id>\n  [✓|✗] VPC + subnets: \u003Cvpc-id> (subnet-AZ list)\n  [✓|✗] HSM type: hsm1.medium\n  [✓|✗] HSM instances: \u003Ccount> across \u003Cn> AZs (≥2 for HA)\n  [✓|✗] Cluster state: UNINITIALIZED → ACTIVE (after activation)\n  [✓|✗] Activation: CSR signed by \u003CCA>, customer cert uploaded (ONE-TIME)\n  [✓|✗] Customer CA: \u003Cca-name> (trust root for the cluster)\n  [✓|✗] Crypto officer (CO): ≥2 CO users created\n  [✓|✗] CO password: stored in Secrets Manager (KMS-encrypted)\n  [✓|✗] Crypto users (CU): \u003Ccu-list>\n  [✓|✗] Password policy: \u003Cpolicy-summary>\n  [✓|✗] Daily automatic backup: enabled (cluster-scoped)\n  [✓|✗] On-demand backup: pre-change snapshot available\n  [✓|✗] Cross-region backup copy: destination region \u003Cregion>\n  [✓|✗] HA: \u003Cn> AZs (tolerates 1 AZ failure)\n  [✓|✗] PKCS#11\u002FJCE client: configured with CN-to-cluster-ID mapping\n  [✓|✗] SSL\u002FTLS offload: \u003Cworkload-list>\n  [✓|✗] FIPS 140-2 Level 3: in-HSM operations, audit trail configured\n  [✓|✗] Security group: sg-cloudhsm-prod (narrow CIDR inbound)\n  [✓|✗] CN-to-cluster-ID mapping: configured (DNS CNAME or configure -a)\n  [✓|✗] Degradation recovery: documented (create replacement, sync, delete)\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws cloudhsmv2 describe-clusters --filters clusterIds=\u003Ccluster-id> --region \u003Cregion>\n  aws cloudhsmv2 describe-backups --filters clusterIds=\u003Ccluster-id> --region \u003Cregion>\n  aws ec2 describe-security-groups --group-ids \u003Csg-id> --region \u003Cregion>\n  aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=cloudhsm.amazonaws.com --region \u003Cregion>\n```\n\n### Worked example — 3-AZ CloudHSM cluster with activation and HA\n\n```text\nCLOUDHSM: cluster-abc123def (us-east-1a, us-east-1b, us-east-1c)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Cluster ID: cluster-abc123def\n  [✓] VPC + subnets: vpc-aaa11122 (subnet-aaa in 1a, subnet-bbb in 1b, subnet-ccc in 1c)\n  [✓] HSM type: hsm1.medium\n  [✓] HSM instances: 3 across 3 AZs (tolerates 1 AZ failure during replace)\n  [✓] Cluster state: ACTIVE\n  [✓] Activation: CSR signed by in-house customerCA, cert uploaded (ONE-TIME)\n  [✓] Customer CA: customerCA (trust root for cluster)\n  [✓] Crypto officer (CO): admin, officer2 (2 COs for quorum)\n  [✓] CO password: stored in Secrets Manager (KMS-encrypted)\n  [✓] Crypto users (CU): app-tls-user, app-code-sign-user\n  [✓] Password policy: min 14 chars, mixed, 90-day rotation\n  [✓] Daily automatic backup: enabled (5-min delta + daily snapshot)\n  [✓] On-demand backup: pre-change snapshot backup-aaa11122\n  [✓] Cross-region backup copy: us-west-2\n  [✓] HA: 3 AZs (tolerates 1 AZ failure during replace)\n  [✓] PKCS#11 client: configured (CN-to-cluster-ID via DNS CNAME)\n  [✓] SSL\u002FTLS offload: nginx using CloudHSM-held private key\n  [✓] FIPS 140-2 Level 3: in-HSM ops, CloudTrail + HSM logs\n  [✓] Security group: sg-cloudhsm-prod (10.0.10.0\u002F24 inbound on 2223)\n  [✓] CN-to-cluster-ID mapping: cloudhsm.internal.example.com → 10.0.1.10\n  [✓] Degradation recovery: documented (create replacement, sync, delete)\n  [✓] Tags: Environment=production, Workload=tls-offload, Owner=platform-team\nVERIFICATION_COMMANDS:\n  aws cloudhsmv2 describe-clusters --filters clusterIds=cluster-abc123def --region us-east-1\n  aws cloudhsmv2 describe-backups --filters clusterIds=cluster-abc123def --region us-east-1\n  aws ec2 describe-security-groups --group-ids sg-cloudhsm-prod --region us-east-1\n  aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=cloudhsm.amazonaws.com --region us-east-1\n```\n\n## References (load on demand)\n\n- [Cluster activation and users](references\u002Fcluster-activation-and-users.md) — one-time CSR activation flow, CO\u002FCU management via mu, password policies, quorum, CN-to-cluster-ID mapping (Steps 4 and 12 in detail)\n- [Backups and HA](references\u002Fbackups-and-ha.md) — backup model, cross-region copy, HA topology, degradation recovery, DR drill (Steps 5, 6, 7, and 13 in detail)\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — expert heuristics (one-time activation, >=2 AZs, CO password non-recoverability), PKCS#11\u002FJCE\u002FPCSC integration, SSL\u002FTLS offload, FIPS 140-2 Level 3 posture, security groups (Steps 8-11 in detail)\n- [Error handling](references\u002Ferror-handling.md) — API error codes and remedies\n- [End-to-end walkthrough](examples\u002FREADME.md) — full worked example from invocation to verification\n\n## Domain\n\nAWS CloudOps \u002F AWS CloudHSM Cluster Provisioning & HSM Lifecycle.\n\n## AWS documentation\n\n- **CloudHSM user guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fintroduction.html\n- **Create cluster** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fcreate-cluster.html\n- **Initialize cluster** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Finitialize-cluster.html\n- **HSM management** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fmanage-hsm.html\n- **Backups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fbackups.html\n- **Cross-region copy** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fbackup-copy.html\n- **PKCS#11 library** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fpkcs11-lib.html\n- **JCE provider** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fjava-lib.html\n- **FIPS 140-2 Level 3** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fcompliance.html\n- **CloudTrail events** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Flogging-using-cloudtrail.html\n","# CloudHSM Cluster Deployer\n\nAn AWS CloudOps agent skill that provisions AWS CloudHSM clusters\nwith correct production defaults: cluster creation in a VPC with\nsubnets across 2+ AZs, HSM instance creation, one-time cluster\nactivation (CSR → self-signed cert), crypto officer\u002Fuser management,\nbackups, HA, PKCS#11\u002FJCE integration, FIPS 140-2 Level 3 posture,\nand degradation recovery. Captures every configuration decision and\nemits a READY_TO_DEPLOY checklist with verification commands.\n\n## Activation keywords\n\ncreate CloudHSM cluster, activate CloudHSM, HSM instance, crypto\nofficer, CloudHSM backup, cross-region backup, PKCS#11, JCE, FIPS\n140-2 Level 3, CN-to-cluster-ID, HSM degradation recovery.\n\n## STRICT output contract\n\nWhen this skill is invoked with a CloudHSM-provisioning request\n(create a cluster, activate an HSM, add an HSM instance, configure\nbackups, or recover from degradation), the agent MUST respond with\nthe READY_TO_DEPLOY checklist defined in \"Output format\" using the\nliteral all-caps labels `CLOUDHSM:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the checklist\n(marked `[✗]`), and `READY_TO_DEPLOY` MUST NOT also appear. The\nresponse uses these literal labels: `CLOUDHSM: \u003Ccluster-id>\n(\u003Csubnet-az-list>)`, then `VERDICT:`, then `CHECKLIST:` with status\nmarkers, then `VERIFICATION_COMMANDS:` with indented\n`aws cloudhsmv2 ...` and `aws ec2 ...` commands.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Cluster creation (VPC, 2+ AZ subnets) | Core topology |\n| Step 2 — HSM instance creation | Per-AZ HA |\n| Step 3 — Cluster activation (one-time CSR) | One-time gate |\n| Step 4 — Crypto officer\u002Fuser management | CO password + users |\n| Step 5 — HSM backups (daily + on-demand) | Backup posture |\n| Step 6 — Cross-region backup copy | DR posture |\n| Step 7 — HA across AZs | Availability |\n| Step 8 — PKCS#11\u002FJCE\u002FPCSC integration | Client libraries |\n| Step 9 — SSL\u002FTLS offload | Workload integration |\n| Step 10 — FIPS 140-2 Level 3 compliance | Compliance |\n| Step 11 — Network security group (sg-xxx) | Network isolation |\n| Step 12 — CN-to-cluster-ID mapping | Client discovery |\n| Step 13 — Degradation recovery | Replace + sync |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fcluster-activation-and-users.md | Activation + CO detail |\n| references\u002Fbackups-and-ha.md | Backups + HA + recovery detail |\n| references\u002Fadvanced-patterns.md | Heuristics + integration detail |\n| references\u002Ferror-handling.md | API errors + remedies |\n\n## Mindset\n\n**One-line takeaway:** An AWS CloudHSM cluster is a single-tenant\nHSM fleet inside your VPC, validated to FIPS 140-2 Level 3.\nCreation gives you a `cluster-id`; creating the FIRST HSM produces\na CSR that you sign once to issue the cluster's customer certificate\n— this activation is one-time and the resulting trust root is what\nevery subsequent HSM inherits. Production clusters need HSMs in\n≥2 AZs for HA, and the crypto officer (CO) password is NOT\nrecoverable — lose it (or lose quorum) and the cluster's key\nmaterial is unrecoverable.\n\nThree misconceptions dominate CloudHSM misdesign at provisioning\ntime:\n\n- **\"Create a cluster and you're done.\"** You're not. After\n  `create-cluster` you must (a) create at least one HSM instance\n  (`create-hsm`), (b) wait for the HSM to be `ACTIVE`, (c) sign the\n  CSR the HSM produces and upload the signed cert + your customerCA\n  certificate to activate the cluster. Until activated, no CO, no\n  users, no crypto operations.\n\n- **\"One HSM is enough for HA.\"** It isn't. A single HSM is a\n  single point of failure. AWS CloudHSM supports HA by adding HSM\n  instances in different AZs to the SAME cluster — they auto-sync\n  key material. Production needs ≥2 AZs.\n\n- **\"The CO password can be reset like a normal password.\"** It\n  cannot. CloudHSM crypto officer credentials are NOT recoverable.\n  Lose the CO password (or the CO user) and you lose access to the\n  key material. Maintain quorum and a secure offline record. No\n  \"forgot password\" flow exists.\n\n## Configuration dependency graph (novel heuristic)\n\nCloudHSM configurations are NOT independent. The cluster needs a\nVPC with subnets in 2+ AZs. The first HSM instance produces the\nCSR. Activation (CSR → self-signed cert) is a one-time gate that\nunlocks CO\u002Fuser management. Backups are taken per-cluster, copied\ncross-region for DR. HA requires ≥2 AZs. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Cluster | VPC + ≥2 subnet-AZs; `cloudhsm:CreateCluster` | cluster-id is fixed; subnet list cannot be expanded later | cluster-id for HSM creation |\n| HSM instance | cluster-id; AZ in subnet list; `cloudhsm:CreateHsm` | first HSM emits a CSR; HSM unreachable until activation | CSR for activation |\n| Cluster activation | first HSM `ACTIVE`; CSR signed by in-house CA | ONE-TIME — customer cert becomes trust root for every subsequent HSM | CO\u002Fuser mgmt; all crypto ops |\n| Crypto officer (CO) | cluster activated; CO logs in via `cloudhsm_mgmt_util` (mu) | CO password NOT recoverable; lose CO + quorum = lose key material | user creation, key mgmt, policy |\n| HSM user (CU) | cluster activated; CO creates users via `mu` or `key_mgmt_util` | users are cluster-scoped; same username\u002Fpassword on every HSM (sync) | key use via PKCS#11\u002FJCE clients |\n| Daily automatic backup | cluster activated; 5-min delta + daily snapshot | backups cluster-scoped; retention configurable; hold key material | point-in-time restore |\n| On-demand backup | cluster activated; via mu `createBackup` | snapshot at time T | pre-change safety net |\n| Cross-region backup copy | destination region enabled; `cloudhsm:CopyBackupToRegion` | copy is one-way; restores in destination create a new cluster | DR in second region |\n| HA across AZs | cluster activated; ≥2 HSM instances in different AZs | key material auto-syncs across HSMs; client lib load-balances | AZ failure tolerance |\n| PKCS#11\u002FJCE client | cluster activated; client configured with CN-to-cluster-ID | client uses customer CA cert to trust cluster; wrong mapping = failure | workload crypto operations |\n| Network security group | SG attached to CloudHSM ENIs; inbound from workload subnets | SG enforced at ENI; too-broad CIDR = attack surface | network isolation |\n| CN-to-cluster-ID mapping | registered via `configure -a \u003Cip>` or DNS CNAME | client uses CN to verify cluster identity; mismatch = TLS failure | client bootstrap |\n\n**The activation-is-one-time row is the one a baseline model\nmisses.** A naive answer treats activation as repeatable or skips\nit. In reality the customer certificate you upload after signing the\nCSR becomes the cluster's permanent trust root; every subsequent\nHSM inherits it. The CO-password-not-recoverable row is the second\nmost missed: operators assume an AWS-side reset path that does not\nexist.\n\n**Cross-dependency gotchas:**\n- Activation is one-time. After uploading the signed customer\n  certificate, you CANNOT re-activate under a different CA without\n  a new cluster (restoring from backup).\n- HA requires ≥2 AZs in the SAME cluster. Two clusters in two AZs\n  do NOT sync key material.\n- Cross-region backup copy creates a restorable backup in the\n  destination region; it does NOT create a running cluster. Restore\n  = `restore-backup` → new cluster-id in destination.\n- CloudHSM ENI security group must allow inbound from workload\n  subnets on HSM service ports (TCP 22 for SSH-less mu, TCP 17578\n  for management, TCP 2223 for client). Use narrowest possible\n  CIDR.\n\n## Prerequisites (verify before provisioning)\n\nBefore provisioning, verify these prerequisites. If any are missing,\nthe verdict is **PREREQUISITES_MISSING** and the specific gap must\nbe cited.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| VPC + ≥2 subnets in different AZs | HA requires ≥2 AZs in the same cluster | `aws ec2 describe-subnets --filters Name=vpc-id,Values=\u003Cvpc>` |\n| Security group for CloudHSM ENIs | Network isolation; workload subnets only | `aws ec2 describe-security-groups` |\n| `cloudhsm:CreateCluster`, `cloudhsm:CreateHsm` IAM | Required to create cluster + HSM | `aws iam simulate-principal-policy ...` |\n| Service-linked role (`AWSServiceRoleForCloudHSM`) | CloudHSM auto-creates; if deleted, recreate | `aws iam get-role --role-name AWSServiceRoleForCloudHSM` |\n| HSM type chosen (`hsm1.medium`) | Instance type for the HSM | Confirm capacity needs |\n| Backup retention policy decision | Daily snapshots; retention in days | Confirm policy intent |\n| Cross-region destination (if DR) | Destination region must be enabled | `aws cloudhsmv2 describe-regions-settings --region \u003Cdst>` |\n| Customer CA (for activation) | Bootstrap CA to sign the first CSR | Confirm in-house CA or self-sign |\n| CO password storage plan | CO password is not recoverable | Confirm secret store (Secrets Manager \u002F KMS vault) |\n| CloudHSM client installed (for activation) | CloudHSM client + key_mgmt_util + cloudhsm_mgmt_util | `cloudhsm-cli version` |\n\nIf any prerequisite is missing, output\n`VERDICT: PREREQUISITES_MISSING` and cite the specific gap.\n\n## Step 1 — Cluster creation (VPC, 2+ AZ subnets)\n\nThe cluster is a regional resource that holds HSM instances.\nSpecify the subnet list (one per AZ) and a security group.\n\n```bash\n# Create the cluster (subnet-az list fixes the HA topology)\nCLUSTER_ID=$(aws cloudhsmv2 create-cluster \\\n  --hsm-type hsm1.medium \\\n  --subnet-ids subnet-aaa11122 subnet-bbb22233 subnet-ccc33344 \\\n  --security-group-id sg-cloudhsm-prod \\\n  --query 'Cluster.ClusterId' --output text --region us-east-1)\n\n# Verify cluster state (CREATE_IN_PROGRESS → UNINITIALIZED)\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[*].{Id:ClusterId, State:State, Subnets:SubnetMapping, Type:HsmType}' \\\n  --output table --region us-east-1\n```\n\n**Constraint:** the subnet list CANNOT be expanded after cluster\ncreation. Plan the AZ topology up front. Adding a new AZ requires a\nnew cluster.\n\n## Step 2 — HSM instance creation\n\nCreate at least one HSM (per AZ) in the cluster. The first HSM\nemits the CSR for activation.\n\n```bash\n# Create HSMs — one per AZ for HA\naws cloudhsmv2 create-hsm --cluster-id \"$CLUSTER_ID\" --availability-zone us-east-1a \\\n  --ip-address 10.0.1.10 --region us-east-1\naws cloudhsmv2 create-hsm --cluster-id \"$CLUSTER_ID\" --availability-zone us-east-1b \\\n  --ip-address 10.0.2.10 --region us-east-1\n\n# Verify each HSM reaches ACTIVE\naws cloudhsmv2 describe-clusters --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].Hsms[*].{Id:HsmId, AZ:AvailabilityZone, State:State, ENI:EniIp}' \\\n  --output table --region us-east-1\n```\n\nEach HSM gets an ENI in the specified subnet. State transitions:\n`CREATE_IN_PROGRESS → ACTIVE`. Once the first HSM is `ACTIVE`, the\nCSR is available via `describe-clusters`.\n\n## Step 3 — Cluster activation (one-time CSR → self-signed cert)\n\nActivation is the one-time gate that unlocks CO\u002Fuser management.\n\n```bash\n# 1. Fetch the CSR from the first ACTIVE HSM\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].Certificates.ClusterCertificate' \\\n  --output text --region us-east-1 > cluster.csr\n\n# 2. Sign the CSR with your in-house CA (or self-sign for bootstrap)\nopenssl x509 -req -days 3650 -in cluster.csr \\\n  -CA customerCA.crt -CAkey customerCA.key -set_serial 01 \\\n  -out customerCertificate.crt\n\n# 3. Upload signed cert + CA cert to activate the cluster\naws cloudhsmv2 initialize-cluster \\\n  --cluster-id \"$CLUSTER_ID\" \\\n  --signed-cert fileb:\u002F\u002FcustomerCertificate.crt \\\n  --trust-anchor fileb:\u002F\u002FcustomerCA.crt --region us-east-1\n\n# 4. Verify state transitions to INITIALIZED → ACTIVE\naws cloudhsmv2 describe-clusters \\\n  --filters clusterIds=$CLUSTER_ID \\\n  --query 'Clusters[0].{State:State, Cert:Certificates}' \\\n  --output table --region us-east-1\n```\n\n**Critical:** activation is ONE-TIME. After this, the customer\ncertificate is the trust root. To change CAs, restore from backup\ninto a new cluster.\n\n## Step 4 — Crypto officer\u002Fuser management\n\nFull procedure: [cluster-activation-and-users.md](references\u002Fcluster-activation-and-users.md). Log in via `cloudhsm_mgmt_util` (mu) over the ENI; create the first CO (`admin`) and CUs. The CO password is the crown-jewel secret — store in Secrets Manager (customer-managed KMS key) and keep >=2 COs for quorum.\n\n## Step 5 — HSM backups (daily + on-demand)\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). Automatic backups every ~5 minutes (delta) plus a daily snapshot; on-demand backups via the mu `createBackup` command. Backups are cluster-scoped; retention is configurable per cluster.\n\n## Step 6 — Cross-region backup copy\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). `copy-backup-to-region` for DR — the copy is one-way and restore in the destination creates a NEW cluster-id (cold DR, not a hot replica).\n\n## Step 7 — HA across AZs\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). 2 AZs tolerates 1 AZ failure (minimum production posture); 3 AZs tolerates 1 failure during a replace (recommended). Two separate clusters do NOT sync key material.\n\n## Step 8 — PKCS#11\u002FJCE\u002FPCSC library integration\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). The client uses the customer CA certificate (uploaded at activation) to trust the cluster — keep the bundle current on every client host.\n\n## Step 9 — SSL\u002FTLS offload\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). Generate the keypair inside the HSM; the web server holds only the certificate — the private key never leaves the HSM.\n\n## Step 10 — FIPS 140-2 Level 3 compliance\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). In-HSM operations only; CloudTrail control-plane + HSM data-plane audit trail; narrow SG inbound; CO quorum for destructive operations.\n\n## Step 11 — Network security group (sg-xxx)\n\nFull procedure: [advanced-patterns.md](references\u002Fadvanced-patterns.md). Inbound TCP 2223 (client) from workload subnets only; TCP 17578 (management utility); TCP 22 (mu). Use the narrowest CIDR — never `0.0.0.0\u002F0`.\n\n## Step 12 — CN-to-cluster-ID mapping\n\nFull procedure: [cluster-activation-and-users.md](references\u002Fcluster-activation-and-users.md). Register the mapping via `configure -a \u003Ceni-ip>` or a DNS CNAME; a wrong mapping fails the client TLS handshake.\n\n## Step 13 — Degradation recovery (create replacement, sync)\n\nFull procedure: [backups-and-ha.md](references\u002Fbackups-and-ha.md). Create the replacement HSM FIRST, wait for ACTIVE + sync, then delete the degraded HSM — never drop below 1 ACTIVE HSM.\n\n## NEVER do these things\n\n1. **NEVER deploy a production CloudHSM cluster with HSMs in only\n   one AZ.** Single-AZ is a single point of failure. Use ≥2 AZs.\n\n2. **NEVER skip cluster activation.** `create-cluster` +\n   `create-hsm` leaves the cluster UNINITIALIZED. Without activation\n   (CSR → signed cert upload), no CO, no users, no crypto.\n\n3. **NEVER treat activation as repeatable.** The customer certificate\n   is the cluster's permanent trust root. To change CAs, restore\n   from backup into a new cluster.\n\n4. **NEVER lose the CO password.** CloudHSM has NO password reset\n   flow. Lose CO + lose quorum = lose key material. Maintain ≥2 COs\n   and a secure offline record.\n\n5. **NEVER use two clusters as HA.** Two clusters do NOT sync key\n   material. HA is intra-cluster: ≥2 HSMs in different AZs in the\n   SAME cluster.\n\n6. **NEVER expand the subnet-AZ list after cluster creation.** The\n   subnet list is fixed at create-cluster time. Adding an AZ\n   requires a new cluster.\n\n7. **NEVER open CloudHSM ENI security group to `0.0.0.0\u002F0`.** Use\n   the narrowest workload-subnet CIDR.\n\n8. **NEVER export key material to workload memory if you need\n   FIPS 140-2 Level 3.** Use in-HSM operations via PKCS#11\u002FJCE.\n\n9. **NEVER assume cross-region backup copy creates a hot replica.**\n   Copy is one-way. Restore creates a NEW cluster-id; cold DR, not\n   a running failover target.\n\n10. **NEVER delete the degraded HSM before the replacement is\n    ACTIVE.** Dropping below 1 ACTIVE HSM loses HA. Create\n    replacement first; verify sync; then delete.\n\n11. **NEVER confuse CloudHSM with KMS.** CloudHSM is single-tenant\n    hardware, FIPS 140-2 Level 3, BYO client libraries, you manage\n    users\u002Fkeys. KMS is multi-tenant regional, FIPS 140-2 Level 2\n    (mostly), AWS manages the HSM backing.\n\n## Output format\n\n```text\nCLOUDHSM: \u003Ccluster-id> (\u003Caz-list>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Cluster ID: \u003Ccluster-id>\n  [✓|✗] VPC + subnets: \u003Cvpc-id> (subnet-AZ list)\n  [✓|✗] HSM type: hsm1.medium\n  [✓|✗] HSM instances: \u003Ccount> across \u003Cn> AZs (≥2 for HA)\n  [✓|✗] Cluster state: UNINITIALIZED → ACTIVE (after activation)\n  [✓|✗] Activation: CSR signed by \u003CCA>, customer cert uploaded (ONE-TIME)\n  [✓|✗] Customer CA: \u003Cca-name> (trust root for the cluster)\n  [✓|✗] Crypto officer (CO): ≥2 CO users created\n  [✓|✗] CO password: stored in Secrets Manager (KMS-encrypted)\n  [✓|✗] Crypto users (CU): \u003Ccu-list>\n  [✓|✗] Password policy: \u003Cpolicy-summary>\n  [✓|✗] Daily automatic backup: enabled (cluster-scoped)\n  [✓|✗] On-demand backup: pre-change snapshot available\n  [✓|✗] Cross-region backup copy: destination region \u003Cregion>\n  [✓|✗] HA: \u003Cn> AZs (tolerates 1 AZ failure)\n  [✓|✗] PKCS#11\u002FJCE client: configured with CN-to-cluster-ID mapping\n  [✓|✗] SSL\u002FTLS offload: \u003Cworkload-list>\n  [✓|✗] FIPS 140-2 Level 3: in-HSM operations, audit trail configured\n  [✓|✗] Security group: sg-cloudhsm-prod (narrow CIDR inbound)\n  [✓|✗] CN-to-cluster-ID mapping: configured (DNS CNAME or configure -a)\n  [✓|✗] Degradation recovery: documented (create replacement, sync, delete)\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws cloudhsmv2 describe-clusters --filters clusterIds=\u003Ccluster-id> --region \u003Cregion>\n  aws cloudhsmv2 describe-backups --filters clusterIds=\u003Ccluster-id> --region \u003Cregion>\n  aws ec2 describe-security-groups --group-ids \u003Csg-id> --region \u003Cregion>\n  aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=cloudhsm.amazonaws.com --region \u003Cregion>\n```\n\n### Worked example — 3-AZ CloudHSM cluster with activation and HA\n\n```text\nCLOUDHSM: cluster-abc123def (us-east-1a, us-east-1b, us-east-1c)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Cluster ID: cluster-abc123def\n  [✓] VPC + subnets: vpc-aaa11122 (subnet-aaa in 1a, subnet-bbb in 1b, subnet-ccc in 1c)\n  [✓] HSM type: hsm1.medium\n  [✓] HSM instances: 3 across 3 AZs (tolerates 1 AZ failure during replace)\n  [✓] Cluster state: ACTIVE\n  [✓] Activation: CSR signed by in-house customerCA, cert uploaded (ONE-TIME)\n  [✓] Customer CA: customerCA (trust root for cluster)\n  [✓] Crypto officer (CO): admin, officer2 (2 COs for quorum)\n  [✓] CO password: stored in Secrets Manager (KMS-encrypted)\n  [✓] Crypto users (CU): app-tls-user, app-code-sign-user\n  [✓] Password policy: min 14 chars, mixed, 90-day rotation\n  [✓] Daily automatic backup: enabled (5-min delta + daily snapshot)\n  [✓] On-demand backup: pre-change snapshot backup-aaa11122\n  [✓] Cross-region backup copy: us-west-2\n  [✓] HA: 3 AZs (tolerates 1 AZ failure during replace)\n  [✓] PKCS#11 client: configured (CN-to-cluster-ID via DNS CNAME)\n  [✓] SSL\u002FTLS offload: nginx using CloudHSM-held private key\n  [✓] FIPS 140-2 Level 3: in-HSM ops, CloudTrail + HSM logs\n  [✓] Security group: sg-cloudhsm-prod (10.0.10.0\u002F24 inbound on 2223)\n  [✓] CN-to-cluster-ID mapping: cloudhsm.internal.example.com → 10.0.1.10\n  [✓] Degradation recovery: documented (create replacement, sync, delete)\n  [✓] Tags: Environment=production, Workload=tls-offload, Owner=platform-team\nVERIFICATION_COMMANDS:\n  aws cloudhsmv2 describe-clusters --filters clusterIds=cluster-abc123def --region us-east-1\n  aws cloudhsmv2 describe-backups --filters clusterIds=cluster-abc123def --region us-east-1\n  aws ec2 describe-security-groups --group-ids sg-cloudhsm-prod --region us-east-1\n  aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=cloudhsm.amazonaws.com --region us-east-1\n```\n\n## References (load on demand)\n\n- [Cluster activation and users](references\u002Fcluster-activation-and-users.md) — one-time CSR activation flow, CO\u002FCU management via mu, password policies, quorum, CN-to-cluster-ID mapping (Steps 4 and 12 in detail)\n- [Backups and HA](references\u002Fbackups-and-ha.md) — backup model, cross-region copy, HA topology, degradation recovery, DR drill (Steps 5, 6, 7, and 13 in detail)\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — expert heuristics (one-time activation, >=2 AZs, CO password non-recoverability), PKCS#11\u002FJCE\u002FPCSC integration, SSL\u002FTLS offload, FIPS 140-2 Level 3 posture, security groups (Steps 8-11 in detail)\n- [Error handling](references\u002Ferror-handling.md) — API error codes and remedies\n- [End-to-end walkthrough](examples\u002FREADME.md) — full worked example from invocation to verification\n\n## Domain\n\nAWS CloudOps \u002F AWS CloudHSM Cluster Provisioning & HSM Lifecycle.\n\n## AWS documentation\n\n- **CloudHSM user guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fintroduction.html\n- **Create cluster** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fcreate-cluster.html\n- **Initialize cluster** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Finitialize-cluster.html\n- **HSM management** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fmanage-hsm.html\n- **Backups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fbackups.html\n- **Cross-region copy** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fbackup-copy.html\n- **PKCS#11 library** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fpkcs11-lib.html\n- **JCE provider** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fjava-lib.html\n- **FIPS 140-2 Level 3** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Fcompliance.html\n- **CloudTrail events** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcloudhsm\u002Flatest\u002Fuserguide\u002Flogging-using-cloudtrail.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, cloudhsm, hsm, cloudops, deploy, security, provisioning, fips-140-2, pkcs11, jce, cluster-activation, hsm-backup","1","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.1.0","aws, cloudhsm, hsm, cloudops, deploy, provisioning, security, fips 140-2, pkcs#11, jce, crypto officer, cluster activation, hsm backup, cross-region backup, ha","deploy","high","false","capability","Invoke when the user wants to create an AWS CloudHSM cluster, activate an HSM (CSR → self-signed cert), create HSM instances across 2+ AZs for HA, manage crypto officers and users, configure backups (daily + on-demand + cross-region copy), integrate PKCS#11\u002FJCE\u002FPCSC libraries, offload SSL\u002FTLS, or recover from HSM degradation. Do NOT invoke for AWS KMS (use kms-key-deployer), ACM (use acm-certificate-deployer), or AWS Signer (use signer-signing-profile-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 cloudhsm, ec2, iam, sts access, plus the CloudHSM client (config -a) and key_mgmt_util \u002F cloudhsm_mgmt_util for crypto officer workflows. Works with Terraform aws_cloudhsm_v2_cluster \u002F aws_cloudhsm_v2_hsm resources and CloudFormation AWS::CloudHSM::Cluster \u002F AWS::CloudHSM::HSM templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fcloudhsm-cluster-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 cloudhsm-cluster-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill cloudhsm-cluster-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill cloudhsm-cluster-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5651,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fco-password-and-quorum.md",545,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fbaselines\u002Fco-password-and-quorum.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fcross-region-backup-copy.md",481,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fbaselines\u002Fcross-region-backup-copy.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fhsm-degradation-recovery.md",513,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fbaselines\u002Fhsm-degradation-recovery.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fsingle-az-prerequisite-failure.md",430,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fbaselines\u002Fsingle-az-prerequisite-failure.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fthree-az-cluster-with-activation.md",592,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fbaselines\u002Fthree-az-cluster-with-activation.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1819,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",8907,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fco-password-and-quorum.md",561,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fprompts\u002Fco-password-and-quorum.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fcross-region-backup-copy.md",417,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fprompts\u002Fcross-region-backup-copy.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fhsm-degradation-recovery.md",438,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fprompts\u002Fhsm-degradation-recovery.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fsingle-az-prerequisite-failure.md",305,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fprompts\u002Fsingle-az-prerequisite-failure.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fthree-az-cluster-with-activation.md",748,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fevals\u002Fprompts\u002Fthree-az-cluster-with-activation.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7831,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",6136,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fbackups-and-ha.md",8630,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Freferences\u002Fbackups-and-ha.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fcluster-activation-and-users.md",7928,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Freferences\u002Fcluster-activation-and-users.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1433,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"skill.usf.yaml",4417,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcloudhsm-cluster-deployer\u002Fskill.usf.yaml",[143,150,157,164,171,178],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"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":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"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":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"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":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"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":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"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",[],[]]