[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACVD8RPRW7CMFZWXNZPRX4":3,"skill-same:01M7ACVD8RPRW7CMFZWXNZPRX4":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},"01M7ACVD8RPRW7CMFZWXNZPRX4","ssm-association-operator",null,"Operates AWS Systems Manager (SSM) State Manager associations with production defaults: association creation (document name, targets, schedule), association status (Success\u002FFailed\u002FPending), compliance reporting, association versioning, output location (S3 bucket with KMS-encrypted SSE), rate control (max-concurrency and max-errors as integer counts, NOT percentages), target via resource tags (dynamic — new instances auto-included) vs instance IDs (static), association automation (apply on cron\u002Frate schedule), association remediation on non-compliance, multi-document association, document-specific parameters, SSM document lifecycle (create\u002Fupdate\u002Fdefault version), and CloudWatch metrics for association execution. Emits an OPERATION_COMPLETED. Triggers: create ssm association, ssm state manager, ssm association schedule, ssm association rate control, ssm association targets, ssm association output s3, ssm association compliance, ssm association version, ssm document parameters, ssm association remediation.","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\u002Fssm-association-operator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ssm-association-operator\ndescription: 'Operates AWS Systems Manager (SSM) State Manager associations with production defaults: association creation (document name, targets, schedule), association status (Success\u002FFailed\u002FPending), compliance reporting, association versioning, output location (S3 bucket with KMS-encrypted SSE), rate control (max-concurrency and max-errors as integer counts, NOT percentages), target via resource tags (dynamic — new instances auto-included) vs instance IDs (static), association automation (apply on cron\u002Frate schedule), association remediation on non-compliance, multi-document association, document-specific parameters, SSM document lifecycle (create\u002Fupdate\u002Fdefault version), and CloudWatch metrics for association execution. Emits an OPERATION_COMPLETED. Triggers: create ssm association, ssm state manager, ssm association schedule, ssm association rate control, ssm association targets, ssm association output s3, ssm association compliance, ssm association version, ssm document parameters, ssm association remediation.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ssm access (and iam access for role\u002Fpolicy creation, s3 access for output bucket validation). Works with Terraform aws_ssm_association \u002F aws_ssm_document resources and CloudFormation AWS::SSM::Association \u002F AWS::SSM::Document templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: medium\n  requires_llm: 'true'\n  phase: '2'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Management\n  task_type: operate\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: OPERATION_COMPLETED | REVIEW_REQUIRED\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, systems-manager, ssm, state-manager, association, cloudops, operate, compliance, rate-control, ssm-document\n  dependencies: aws-orchestrator\n  keywords: aws, systems manager, ssm, state manager, association, create association, association schedule, association targets, rate control, max-concurrency, max-errors, compliance, association version, output location, ssm document, document lifecycle, remediation, tag targets, cloudops, operate\n  when_to_use: Invoke when the user wants to create or operate an SSM State Manager association — apply a document (AWS-managed or custom) to targets on a schedule, target instances by tag (dynamic) or instance IDs (static), configure rate control (max-concurrency and max-errors as integer counts), route execution output to an S3 bucket, view association status and compliance, version an association, set up remediation when an association drifts to non-compliant, or run multi-document associations. Do NOT invoke for ad-hoc one-off command runs (use ssm-run-command skills), patch baseline creation (use ssm-patch-baseline-deployer), or session manager troubleshooting (use ssm-session-troubleshooter).\n---\n\n# SSM Association Operator\n\nAn AWS CloudOps agent skill that operates AWS Systems Manager (SSM)\nState Manager associations with correct defaults. The skill walks the\noperator through the document\u002Ftarget\u002Fschedule model, tag-vs-instanceID\ntargeting, integer rate control, S3 output with KMS-encrypted SSE,\ncompliance reporting, association versioning, and remediation on\nnon-compliance, captures the configuration, explains why each default\nmatters, and emits an OPERATION_COMPLETED checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate SSM association, SSM State Manager, SSM association schedule,\nSSM association rate control, SSM association targets, SSM association\noutput S3, SSM association compliance, SSM association version, SSM\ndocument parameters, SSM association remediation.\n\n## STRICT output contract\n\nWhen this skill is invoked with an SSM-association-operation request\n(create an association, target instances by tag, schedule a document\nrun, configure rate control, route output to S3, set up remediation,\nversion an association, or report compliance status), the agent MUST\nrespond with the OPERATION_COMPLETED checklist defined in the \"Output\nformat\" section using the literal all-caps labels `SSM_ASSOCIATION:`,\n`VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface\nthe checklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream operations pipelines rely on; deviating from the\nliteral labels breaks automation silently.\n\nIf any prerequisite is missing or the configuration shows a material\ngap (S3 output bucket without KMS, percentage-string rate control,\nschedule without apply-at-creation, etc.), the verdict is\n`REVIEW_REQUIRED` with a specific gap citation in the checklist (marked\n`[!]`), and `OPERATION_COMPLETED` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before operating |\n| Step 1 — Document\u002Ftarget\u002Fschedule model | Core association model |\n| Step 2 — Targets: tag vs instance IDs | Targeting decision |\n| Step 3 — Rate control (integer counts, NOT percentages) | Concurrency + error threshold |\n| Step 4 — Schedule (cron\u002Frate, apply-at-creation) | When associations run |\n| Step 5 — Output location (S3 + KMS-encrypted SSE) | Execution artifacts |\n| Step 6 — Association status and compliance | Success\u002FFailed\u002FPending + compliance |\n| Step 7 — Association versioning | Update + default version |\n| Step 8 — Remediation on non-compliance | Auto-remediation wiring |\n| Step 9 — Multi-document associations | Documents chaining |\n| Step 10 — SSM document lifecycle | Create\u002Fupdate\u002Fdefault version |\n| Step 11 — CloudWatch metrics | Observability |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frate-control-and-targets.md | Rate control + targeting detail |\n| references\u002Foutput-and-compliance.md | S3 output + compliance detail |\n\n## Mindset\n\n**One-line takeaway:** An SSM State Manager association applies a\ndocument (AWS-managed or custom) to a set of targets on a schedule.\nTargets specified by tag are DYNAMIC — new instances matching the tag\nare picked up automatically on the next run. Targets specified by\ninstance ID are STATIC — new instances are NOT picked up until the\nassociation is updated. Rate control uses `max-concurrency` and\n`max-errors` as INTEGER COUNTS (e.g., `10` or `1`), NOT percentages.\n\nThree misconceptions dominate SSM association misoperation:\n\n- **\"Rate control accepts percentages as the canonical form.\"** It\n  does, but the integer count form is preferred for deterministic\n  behavior across fleets of varying size. A `10%` value on a\n  3-instance fleet rounds unpredictably; `max-concurrency: 1` is\n  unambiguous. The skill always emits the integer form and flags\n  percentage strings as REVIEW_REQUIRED.\n\n- **\"Tag-based targets behave the same as instance-ID targets.\"** They\n  do not. Tag targets are dynamic: any instance that gains the tag\n  (e.g., newly launched by Auto Scaling) is automatically picked up at\n  the next association run. Instance-ID targets are static: the\n  association only ever touches the IDs explicitly listed. For\n  autoscaling fleets, ALWAYS use tag targets.\n\n- **\"The S3 output bucket just needs to exist.\"** It needs SSE enabled,\n  and for production that means a customer-managed KMS key. SSM does\n  not enforce SSE, but execution artifacts (stdout\u002Fstderr\u002Fscripts) can\n  contain secrets; shipping them to an unencrypted bucket is a finding.\n  The skill flags a missing KMS key as REVIEW_REQUIRED.\n\n## Configuration dependency graph\n\nSSM association configurations are NOT independent. The document must\nexist before the association is created. The instance profile must\nallow SSM before targets can run anything. Output S3 bucket policy\nmust allow the SSM service principal to write before output is\ndelivered. Use this graph to sequence operations.\n\n| Configuration | Hard dependencies | Silent failure | Enables downstream |\n|---|---|---|---|\n| SSM document | document name exists in account or AWS-managed catalog | custom docs need a default version set before reference | the document body |\n| Instance profile | target EC2 instances have AmazonSSMManagedInstanceCore | instances without the role show PingStatus: Inactive and are silently skipped | SSM agent reachability |\n| Association (create) | document name; targets; schedule | does NOT run at creation unless `--apply-at-creation` is set | the association itself |\n| Rate control | integer counts for max-concurrency and max-errors | percentage strings work but are size-dependent and ambiguous | safe rollout pace |\n| Output S3 bucket | bucket exists; SSM service principal has s3:PutObject | without KMS key, output is unencrypted at rest; SSM silently drops output if bucket policy missing | execution artifacts |\n| Schedule | cron or rate expression | `rate(30 minutes)` and `cron(0 30 * * * *)` are NOT interchangeable | automated runs |\n| Compliance | association has executed at least once | non-compliant status only computed AFTER first run; before that = Pending | drift detection |\n| Remediation | association exists; document supports idempotent apply | remediation re-applies document on non-compliance; non-idempotent docs cause side effects | auto-remediation |\n\n**The integer-rate-control row is the one a baseline model misses.**\nMany baseline answers emit `max-concurrency: \"10%\"` because the API\ntechnically accepts percentage strings. The skill normalizes to\ninteger counts because that is the deterministic, fleet-size-\nindependent form. The S3-output-needs-KMS row is the second commonly\nmissed configuration.\n\n## Expert heuristic: integer rate control vs percentage strings\n\n→ Moved to [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — integer-vs-percentage decision model and worst-case blast radius.\n\n## Expert heuristic: tag targets vs instance-ID targets\n\n→ Moved to [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — tag-target vs instance-ID decision model.\n\n## Expert heuristic: S3 output bucket encryption\n\n→ Moved to [references\u002Foutput-and-compliance.md](references\u002Foutput-and-compliance.md) — S3 output bucket encryption requirements and silent-finding risk.\n\n## Prerequisites (verify before operating)\n\nBefore emitting association commands, verify these prerequisites. If\nany are missing, the verdict is **REVIEW_REQUIRED**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| SSM document exists | Association references a document name | `aws ssm describe-document --name \u003Cname>` |\n| Default document version set | Custom documents need a default version | `aws ssm describe-document --name \u003Cname> --query 'Document.DefaultVersion'` |\n| Target instances managed by SSM | Targets must have PingStatus: Online | `aws ssm describe-instance-information --filters Key=Tag:Environment,Values=[production]` |\n| Output S3 bucket exists | Output location must be writable | `aws s3api head-bucket --bucket \u003Cbucket>` |\n| KMS key for output bucket | SSE-KMS required for production | `aws s3api get-bucket-encryption --bucket \u003Cbucket>` |\n| Schedule expression valid | Cron needs seconds field; rate needs units | Validate `cron(...)` or `rate(...)` syntax |\n\n## Step 1 — Document\u002Ftarget\u002Fschedule model\n\nAn SSM State Manager association binds three things: a document, a set\nof targets, and a schedule.\n\n| Component | What it specifies | API field |\n|---|---|---|\n| Document | What to run (AWS-managed or custom) | `--name AWS-ApplyPatchBaseline` |\n| Targets | Which instances to run on | `--targets Key=tag:Environment,Values=production` |\n| Schedule | When to run | `--schedule-expression \"rate(30 minutes)\"` |\n| Parameters | Document-specific inputs | `--parameters Operation=Install` |\n\n**AWS-managed documents** include `AWS-ApplyPatchBaseline`,\n`AWS-GatherSoftwareInventory`, `AWS-UpdateSSMAgent`,\n`AWS-ConfigureCloudWatchOnEC2Instances`. **Custom documents** are\nuser-authored YAML\u002FJSON defining a sequence of steps; they need a\ndefault version set before they can be referenced.\n\n## Step 2 — Targets: tag vs instance IDs\n\n| Target type | Dynamic? | Use case | Example |\n|---|---|---|---|\n| Tag | Yes — new tagged instances auto-included | Auto Scaling fleets | `Key=tag:Environment,Values=production` |\n| Instance IDs | No — only listed IDs targeted | Pet servers, one-off | `Key=InstanceIds,Values=i-aaa111,i-bbb222` |\n| Resource group | Yes — membership rules | Complex grouping | `Key=ResourceGroups,Values=\u003Crg-arn>` |\n\nFor any fleet with churn, ALWAYS use tag targets.\n\n## Step 3 — Rate control (integer counts, NOT percentages)\n\n```bash\naws ssm create-association \\\n  --name \"AWS-ApplyPatchBaseline\" \\\n  --targets \"Key=tag:Environment,Values=production\" \\\n  --schedule-expression \"rate(30 minutes)\" \\\n  --max-concurrency 10 \\\n  --max-errors 3 \\\n  --parameters \"Operation=Install\" \\\n  --output-location '{\"S3Location\":{\"OutputS3BucketName\":\"my-ssm-output\",\"OutputS3KeyPrefix\":\"ssm-output\u002F\",\"OutputS3Region\":\"us-east-1\"}}' \\\n  --apply-at-creation \\\n  --region us-east-1\n```\n\n**Critical:** the integer form `10` is unambiguous across fleet sizes.\nThe percentage form `\"10%\"` rounds unpredictably in small fleets. The\nskill normalizes to integers and flags percentage strings as\nREVIEW_REQUIRED.\n\n## Step 4 — Schedule (cron\u002Frate, apply-at-creation)\n\n| Expression | Format | Example | Notes |\n|---|---|---|---|\n| `rate` | `rate(\u003Cvalue> \u003Cunits>)` | `rate(30 minutes)` | Min: 1 minute; no seconds |\n| `cron` | `cron(\u003Csec> \u003Cmin> \u003Chr> \u003Cdom> \u003Cmon> \u003Cdow> \u003Cyear>)` | `cron(0 30 2 ? * * *)` | 6 required fields + optional year; AWS cron (NOT Unix) |\n\n**Critical: AWS cron is NOT Unix cron.** AWS cron has 6 fields (with\noptional 7th year), starting with SECONDS. Unix cron has 5 fields\nstarting with minutes. The skill always uses AWS cron syntax.\n\n**Apply-at-creation:** by default, an association does NOT run when\ncreated. It waits for the next scheduled tick. For first-run\nvalidation, set `--apply-at-creation`. The skill always sets it.\n\n## Step 5 — Output location (S3 + KMS-encrypted SSE)\n\n```bash\naws ssm create-association \\\n  --name \"AWS-ApplyPatchBaseline\" \\\n  --targets \"Key=tag:Environment,Values=production\" \\\n  --schedule-expression \"rate(30 minutes)\" \\\n  --output-location '{\n    \"S3Location\": {\n      \"OutputS3BucketName\": \"my-ssm-output\",\n      \"OutputS3KeyPrefix\": \"ssm-output\u002F\",\n      \"OutputS3Region\": \"us-east-1\"\n    }\n  }' \\\n  --region us-east-1\n```\n\n**Verify the bucket has KMS-encrypted SSE:**\n\n```bash\naws s3api get-bucket-encryption --bucket my-ssm-output --region us-east-1\n# Expected: ServerSideEncryptionConfiguration with SSE-KMS + KMSMasterKeyID\n```\n\n**Critical:** SSM does NOT enforce SSE on the output bucket. An\nunencrypted bucket is a silent finding. The skill flags any output\nbucket without a customer-managed KMS key as REVIEW_REQUIRED. The S3\nbucket policy must allow the SSM service principal to `s3:PutObject`,\nand the KMS key policy must allow SSM to `kms:GenerateDataKey`.\n\n## Step 6 — Association status and compliance\n\n| Status | Meaning | Action |\n|---|---|---|\n| `Success` | All targeted instances ran successfully | None |\n| `Failed` | One or more instances errored; rate control may have stopped the run | Inspect per-instance output in S3 |\n| `Pending` | Association created but not yet executed | Wait, or trigger with `--apply-at-creation` |\n| `TimedOut` | Document execution exceeded timeout | Increase timeout or fix document |\n\n```bash\n# Association status + execution history\naws ssm describe-association --association-id \"\u003Cid>\" --region us-east-1\naws ssm describe-association-executions --association-id \"\u003Cid>\" --region us-east-1\n\n# Compliance reporting\naws ssm list-compliance-items --filters \"Key=ComplianceType,Values=Association\" --region us-east-1\naws ssm list-resource-compliance-summaries --filters \"Key=ComplianceType,Values=Association\" --region us-east-1\n```\n\n## Step 7 — Association versioning\n\nEach association update creates a new version (1, 2, 3, ...).\n\n```bash\naws ssm update-association \\\n  --association-id \"\u003Cid>\" \\\n  --schedule-expression \"rate(15 minutes)\" \\\n  --region us-east-1\n\naws ssm list-association-versions --association-id \"\u003Cid>\" --region us-east-1\n```\n\n**Critical:** there is no built-in rollback command. To revert, read\nthe desired version's parameters from `list-association-versions` and\nre-apply them via `update-association`.\n\n## Step 8 — Remediation on non-compliance\n\nWhen an association drifts to non-compliant, SSM can auto-remediate by\nre-applying the document.\n\n```text\nNON_COMPLIANT detected\n  → EventBridge rule pattern:\n      source: [aws.ssm]\n      detail-type: [Configuration Compliance State Change]\n      detail.status: [NON_COMPLIANT]\n  → Target: SSM Automation or Lambda → StartAssociationsOnce\n  → SSM re-applies the document → compliance flips back\n```\n\n**Manual re-run:**\n\n```bash\naws ssm start-associations-once --association-ids \"\u003Cid>\" --region us-east-1\n```\n\n**Critical:** remediation only works if the document is IDEMPOTENT. A\nnon-idempotent document (e.g., one that appends to a file) will cause\nside effects on re-run. Always verify idempotency before wiring\nremediation.\n\n## Step 9 — Multi-document associations\n\nA single association applies ONE document. To apply multiple documents\nto the same targets, create SEPARATE associations, OR build a single\ncustom step-document that runs multiple steps in sequence:\n\n```yaml\nschemaVersion: '2.2'\nname: Custom-ProvisionAndConfigure\nmainSteps:\n  - action: aws:runShellScript\n    name: installPackage\n    inputs:\n      runCommand:\n        - yum install -y httpd\n  - action: aws:runShellScript\n    name: configureService\n    inputs:\n      runCommand:\n        - systemctl enable httpd\n        - systemctl start httpd\n```\n\nUse a step-document when the steps have ordering dependencies. Use\nseparate associations when the documents are independent.\n\n## Step 10 — SSM document lifecycle\n\n```bash\n# Create\naws ssm create-document --content file:\u002F\u002Fdoc.yaml --name \"Custom-Harden\" \\\n  --document-type Command --document-format YAML --region us-east-1\n\n# Update (creates new version)\naws ssm update-document --content file:\u002F\u002Fdoc-v2.yaml --name \"Custom-Harden\" \\\n  --document-version \"1\" --region us-east-1\n\n# Set default version (associations use the default version)\naws ssm update-document-default-version --name \"Custom-Harden\" \\\n  --document-version \"2\" --region us-east-1\n```\n\n**Critical:** an association referencing a custom document always uses\nthe document's DEFAULT VERSION. To pin an association to a specific\nversion, reference it explicitly: `Custom-HardenBaseline:2`.\n\n## Step 11 — CloudWatch metrics\n\nSSM emits metrics in the `AWS\u002FSSM` namespace.\n\n| Metric | Description |\n|---|---|\n| `AssociationSuccess` | Count of successful executions |\n| `AssociationFailed` | Count of failed executions — alarm on spikes |\n| `AssociationTimeout` | Count of timed-out executions |\n| `AssociationCompliance` | 1=compliant, 0=non-compliant |\n\n## Step 12 — Recent features\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026).\n\n## NEVER do these things\n\n1. **NEVER use percentage strings for rate control.**\n   `max-concurrency: \"10%\"` behaves differently across fleet sizes.\n   Use integer counts (`max-concurrency: 10`, `max-errors: 3`).\n\n2. **NEVER use instance-ID targets for autoscaling fleets.** Instance\n   IDs are static; new instances are NOT picked up. Use tag targets.\n\n3. **NEVER configure an output S3 bucket without customer-managed\n   KMS-encrypted SSE.** SSM does not enforce SSE; an unencrypted\n   bucket is a silent finding.\n\n4. **NEVER create an association without `--apply-at-creation` for the\n   first run.** Otherwise it waits for the next scheduled tick.\n\n5. **NEVER use Unix cron syntax.** AWS cron has 6 fields starting with\n   SECONDS. `cron(0 30 2 ? * * *)` is AWS cron for 02:30 daily.\n\n6. **NEVER wire remediation for a non-idempotent document.**\n   Remediation re-applies the document; non-idempotent documents cause\n   side effects on re-run.\n\n7. **NEVER assume compliance status is computed before the first run.**\n   A newly created association shows \"Pending\" until it executes at\n   least once.\n\n8. **NEVER update a custom document without setting a default\n   version.** Associations reference the default version.\n\n9. **NEVER assume the S3 output bucket policy is correct without\n   testing.** SSM silently drops output if the bucket policy does not\n   allow the SSM service principal to `s3:PutObject`.\n\n10. **NEVER assume the association will run immediately after\n    creation.** By default, the first run happens at the next\n    scheduled execution.\n\n## Output format\n\n```text\nSSM_ASSOCIATION: \u003Cassociation-name> (\u003Cassociation-id>)\nVERDICT: OPERATION_COMPLETED | REVIEW_REQUIRED\nCHECKLIST:\n  [✓|!] Document: \u003Cdocument-name> (version \u003Cv|default>)\n  [✓|!] Targets: \u003Ctag-key>=\u003Cvalues> (dynamic) | InstanceIds=\u003Cids> (static)\n  [✓|!] Schedule: \u003Ccron|rate expression>\n  [✓|!] Apply-at-creation: ENABLED | DISABLED\n  [✓|!] Rate control: max-concurrency=\u003CN>, max-errors=\u003CN> (integer form)\n  [✓|!] Output S3: s3:\u002F\u002F\u003Cbucket>\u002F\u003Cprefix> (SSE-KMS) | UNENCRYPTED [!]\n  [✓|!] Parameters: \u003Ckey=value list>\n  [✓|!] Compliance: COMPLIANT | NON_COMPLIANT | PENDING (first run)\n  [✓|!] Status: Success | Failed | Pending\n  [✓|!] Association version: \u003Cv>\n  [✓|!] CloudWatch alarm: \u003Calarm-name or \"none\">\n  [✓|!] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ssm describe-association --association-id \u003Cassociation-id> --region \u003Cregion>\n  aws ssm describe-association-executions --association-id \u003Cassociation-id> --region \u003Cregion>\n  aws ssm list-compliance-items --filters Key=ComplianceType,Values=Association --region \u003Cregion>\n  aws s3api get-bucket-encryption --bucket \u003Coutput-bucket> --region \u003Cregion>\n```\n\n### Worked example — tag-targeted scheduled association with integer rate control and KMS-encrypted S3 output\n\n```text\nSSM_ASSOCIATION: PatchProductionFleet (a-1a2b3c4d5e6f7g8h9)\nVERDICT: OPERATION_COMPLETED\nCHECKLIST:\n  [✓] Document: AWS-ApplyPatchBaseline (default version)\n  [✓] Targets: tag:Environment=production (dynamic)\n  [✓] Schedule: rate(30 minutes)\n  [✓] Apply-at-creation: ENABLED\n  [✓] Rate control: max-concurrency=10, max-errors=3 (integer form)\n  [✓] Output S3: s3:\u002F\u002Fmy-ssm-output\u002Fssm-output\u002F (SSE-KMS, key arn:aws:kms:us-east-1:123456789012:key\u002Fabc123)\n  [✓] Parameters: Operation=Install, SnapshotId=latest\n  [✓] Compliance: COMPLIANT\n  [✓] Status: Success\n  [✓] Association version: 3\n  [✓] CloudWatch alarm: ssm-patch-failures-prod\n  [✓] Tags: Environment=production, Owner=cloudops\nVERIFICATION_COMMANDS:\n  aws ssm describe-association --association-id a-1a2b3c4d5e6f7g8h9 --region us-east-1\n  aws ssm describe-association-executions --association-id a-1a2b3c4d5e6f7g8h9 --region us-east-1\n  aws ssm list-compliance-items --filters Key=ComplianceType,Values=Association --region us-east-1\n  aws s3api get-bucket-encryption --bucket my-ssm-output --region us-east-1\n```\n\n## Error handling\n\n→ Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — six failure modes: zero targets, stuck Pending, output not delivered, Failed status, NON_COMPLIANT, rate-control stop.\n\n## References (load on demand)\n\n- [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — pre-existing; extended with the integer-rate-control and tag-vs-instance-ID expert heuristics moved from SKILL.md.\n- [references\u002Foutput-and-compliance.md](references\u002Foutput-and-compliance.md) — pre-existing; extended with the S3 output bucket encryption expert heuristic moved from SKILL.md.\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026): association-level KMS, target-locations, calendar schedules, EventBridge triggers, compliance dashboard.\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — error-handling deep dive: zero targets, Pending stall, S3 output drop, Failed runs, NON_COMPLIANT after success, rate-control stop.\n\n## Domain\n\nAWS CloudOps \u002F AWS Systems Manager (SSM) State Manager Association\nOperations & Compliance Management.\n\n## AWS documentation\n\n- **SSM State Manager** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsystems-manager-state.html\n- **Creating associations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-assoc.html\n- **Targeting instances** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-target.html\n- **Rate control** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-rate-control.html\n- **Cron schedules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Freference-cron-and-rate-expressions.html\n- **S3 output** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-rc-output.html\n- **Compliance** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-compliance.html\n- **Association versions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-association-versions.html\n- **SSM documents** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fdocuments.html\n- **CloudWatch metrics for SSM** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fmonitoring-cloudwatch-metrics.html\n","# SSM Association Operator\n\nAn AWS CloudOps agent skill that operates AWS Systems Manager (SSM)\nState Manager associations with correct defaults. The skill walks the\noperator through the document\u002Ftarget\u002Fschedule model, tag-vs-instanceID\ntargeting, integer rate control, S3 output with KMS-encrypted SSE,\ncompliance reporting, association versioning, and remediation on\nnon-compliance, captures the configuration, explains why each default\nmatters, and emits an OPERATION_COMPLETED checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate SSM association, SSM State Manager, SSM association schedule,\nSSM association rate control, SSM association targets, SSM association\noutput S3, SSM association compliance, SSM association version, SSM\ndocument parameters, SSM association remediation.\n\n## STRICT output contract\n\nWhen this skill is invoked with an SSM-association-operation request\n(create an association, target instances by tag, schedule a document\nrun, configure rate control, route output to S3, set up remediation,\nversion an association, or report compliance status), the agent MUST\nrespond with the OPERATION_COMPLETED checklist defined in the \"Output\nformat\" section using the literal all-caps labels `SSM_ASSOCIATION:`,\n`VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface\nthe checklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream operations pipelines rely on; deviating from the\nliteral labels breaks automation silently.\n\nIf any prerequisite is missing or the configuration shows a material\ngap (S3 output bucket without KMS, percentage-string rate control,\nschedule without apply-at-creation, etc.), the verdict is\n`REVIEW_REQUIRED` with a specific gap citation in the checklist (marked\n`[!]`), and `OPERATION_COMPLETED` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before operating |\n| Step 1 — Document\u002Ftarget\u002Fschedule model | Core association model |\n| Step 2 — Targets: tag vs instance IDs | Targeting decision |\n| Step 3 — Rate control (integer counts, NOT percentages) | Concurrency + error threshold |\n| Step 4 — Schedule (cron\u002Frate, apply-at-creation) | When associations run |\n| Step 5 — Output location (S3 + KMS-encrypted SSE) | Execution artifacts |\n| Step 6 — Association status and compliance | Success\u002FFailed\u002FPending + compliance |\n| Step 7 — Association versioning | Update + default version |\n| Step 8 — Remediation on non-compliance | Auto-remediation wiring |\n| Step 9 — Multi-document associations | Documents chaining |\n| Step 10 — SSM document lifecycle | Create\u002Fupdate\u002Fdefault version |\n| Step 11 — CloudWatch metrics | Observability |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frate-control-and-targets.md | Rate control + targeting detail |\n| references\u002Foutput-and-compliance.md | S3 output + compliance detail |\n\n## Mindset\n\n**One-line takeaway:** An SSM State Manager association applies a\ndocument (AWS-managed or custom) to a set of targets on a schedule.\nTargets specified by tag are DYNAMIC — new instances matching the tag\nare picked up automatically on the next run. Targets specified by\ninstance ID are STATIC — new instances are NOT picked up until the\nassociation is updated. Rate control uses `max-concurrency` and\n`max-errors` as INTEGER COUNTS (e.g., `10` or `1`), NOT percentages.\n\nThree misconceptions dominate SSM association misoperation:\n\n- **\"Rate control accepts percentages as the canonical form.\"** It\n  does, but the integer count form is preferred for deterministic\n  behavior across fleets of varying size. A `10%` value on a\n  3-instance fleet rounds unpredictably; `max-concurrency: 1` is\n  unambiguous. The skill always emits the integer form and flags\n  percentage strings as REVIEW_REQUIRED.\n\n- **\"Tag-based targets behave the same as instance-ID targets.\"** They\n  do not. Tag targets are dynamic: any instance that gains the tag\n  (e.g., newly launched by Auto Scaling) is automatically picked up at\n  the next association run. Instance-ID targets are static: the\n  association only ever touches the IDs explicitly listed. For\n  autoscaling fleets, ALWAYS use tag targets.\n\n- **\"The S3 output bucket just needs to exist.\"** It needs SSE enabled,\n  and for production that means a customer-managed KMS key. SSM does\n  not enforce SSE, but execution artifacts (stdout\u002Fstderr\u002Fscripts) can\n  contain secrets; shipping them to an unencrypted bucket is a finding.\n  The skill flags a missing KMS key as REVIEW_REQUIRED.\n\n## Configuration dependency graph\n\nSSM association configurations are NOT independent. The document must\nexist before the association is created. The instance profile must\nallow SSM before targets can run anything. Output S3 bucket policy\nmust allow the SSM service principal to write before output is\ndelivered. Use this graph to sequence operations.\n\n| Configuration | Hard dependencies | Silent failure | Enables downstream |\n|---|---|---|---|\n| SSM document | document name exists in account or AWS-managed catalog | custom docs need a default version set before reference | the document body |\n| Instance profile | target EC2 instances have AmazonSSMManagedInstanceCore | instances without the role show PingStatus: Inactive and are silently skipped | SSM agent reachability |\n| Association (create) | document name; targets; schedule | does NOT run at creation unless `--apply-at-creation` is set | the association itself |\n| Rate control | integer counts for max-concurrency and max-errors | percentage strings work but are size-dependent and ambiguous | safe rollout pace |\n| Output S3 bucket | bucket exists; SSM service principal has s3:PutObject | without KMS key, output is unencrypted at rest; SSM silently drops output if bucket policy missing | execution artifacts |\n| Schedule | cron or rate expression | `rate(30 minutes)` and `cron(0 30 * * * *)` are NOT interchangeable | automated runs |\n| Compliance | association has executed at least once | non-compliant status only computed AFTER first run; before that = Pending | drift detection |\n| Remediation | association exists; document supports idempotent apply | remediation re-applies document on non-compliance; non-idempotent docs cause side effects | auto-remediation |\n\n**The integer-rate-control row is the one a baseline model misses.**\nMany baseline answers emit `max-concurrency: \"10%\"` because the API\ntechnically accepts percentage strings. The skill normalizes to\ninteger counts because that is the deterministic, fleet-size-\nindependent form. The S3-output-needs-KMS row is the second commonly\nmissed configuration.\n\n## Expert heuristic: integer rate control vs percentage strings\n\n→ Moved to [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — integer-vs-percentage decision model and worst-case blast radius.\n\n## Expert heuristic: tag targets vs instance-ID targets\n\n→ Moved to [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — tag-target vs instance-ID decision model.\n\n## Expert heuristic: S3 output bucket encryption\n\n→ Moved to [references\u002Foutput-and-compliance.md](references\u002Foutput-and-compliance.md) — S3 output bucket encryption requirements and silent-finding risk.\n\n## Prerequisites (verify before operating)\n\nBefore emitting association commands, verify these prerequisites. If\nany are missing, the verdict is **REVIEW_REQUIRED**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| SSM document exists | Association references a document name | `aws ssm describe-document --name \u003Cname>` |\n| Default document version set | Custom documents need a default version | `aws ssm describe-document --name \u003Cname> --query 'Document.DefaultVersion'` |\n| Target instances managed by SSM | Targets must have PingStatus: Online | `aws ssm describe-instance-information --filters Key=Tag:Environment,Values=[production]` |\n| Output S3 bucket exists | Output location must be writable | `aws s3api head-bucket --bucket \u003Cbucket>` |\n| KMS key for output bucket | SSE-KMS required for production | `aws s3api get-bucket-encryption --bucket \u003Cbucket>` |\n| Schedule expression valid | Cron needs seconds field; rate needs units | Validate `cron(...)` or `rate(...)` syntax |\n\n## Step 1 — Document\u002Ftarget\u002Fschedule model\n\nAn SSM State Manager association binds three things: a document, a set\nof targets, and a schedule.\n\n| Component | What it specifies | API field |\n|---|---|---|\n| Document | What to run (AWS-managed or custom) | `--name AWS-ApplyPatchBaseline` |\n| Targets | Which instances to run on | `--targets Key=tag:Environment,Values=production` |\n| Schedule | When to run | `--schedule-expression \"rate(30 minutes)\"` |\n| Parameters | Document-specific inputs | `--parameters Operation=Install` |\n\n**AWS-managed documents** include `AWS-ApplyPatchBaseline`,\n`AWS-GatherSoftwareInventory`, `AWS-UpdateSSMAgent`,\n`AWS-ConfigureCloudWatchOnEC2Instances`. **Custom documents** are\nuser-authored YAML\u002FJSON defining a sequence of steps; they need a\ndefault version set before they can be referenced.\n\n## Step 2 — Targets: tag vs instance IDs\n\n| Target type | Dynamic? | Use case | Example |\n|---|---|---|---|\n| Tag | Yes — new tagged instances auto-included | Auto Scaling fleets | `Key=tag:Environment,Values=production` |\n| Instance IDs | No — only listed IDs targeted | Pet servers, one-off | `Key=InstanceIds,Values=i-aaa111,i-bbb222` |\n| Resource group | Yes — membership rules | Complex grouping | `Key=ResourceGroups,Values=\u003Crg-arn>` |\n\nFor any fleet with churn, ALWAYS use tag targets.\n\n## Step 3 — Rate control (integer counts, NOT percentages)\n\n```bash\naws ssm create-association \\\n  --name \"AWS-ApplyPatchBaseline\" \\\n  --targets \"Key=tag:Environment,Values=production\" \\\n  --schedule-expression \"rate(30 minutes)\" \\\n  --max-concurrency 10 \\\n  --max-errors 3 \\\n  --parameters \"Operation=Install\" \\\n  --output-location '{\"S3Location\":{\"OutputS3BucketName\":\"my-ssm-output\",\"OutputS3KeyPrefix\":\"ssm-output\u002F\",\"OutputS3Region\":\"us-east-1\"}}' \\\n  --apply-at-creation \\\n  --region us-east-1\n```\n\n**Critical:** the integer form `10` is unambiguous across fleet sizes.\nThe percentage form `\"10%\"` rounds unpredictably in small fleets. The\nskill normalizes to integers and flags percentage strings as\nREVIEW_REQUIRED.\n\n## Step 4 — Schedule (cron\u002Frate, apply-at-creation)\n\n| Expression | Format | Example | Notes |\n|---|---|---|---|\n| `rate` | `rate(\u003Cvalue> \u003Cunits>)` | `rate(30 minutes)` | Min: 1 minute; no seconds |\n| `cron` | `cron(\u003Csec> \u003Cmin> \u003Chr> \u003Cdom> \u003Cmon> \u003Cdow> \u003Cyear>)` | `cron(0 30 2 ? * * *)` | 6 required fields + optional year; AWS cron (NOT Unix) |\n\n**Critical: AWS cron is NOT Unix cron.** AWS cron has 6 fields (with\noptional 7th year), starting with SECONDS. Unix cron has 5 fields\nstarting with minutes. The skill always uses AWS cron syntax.\n\n**Apply-at-creation:** by default, an association does NOT run when\ncreated. It waits for the next scheduled tick. For first-run\nvalidation, set `--apply-at-creation`. The skill always sets it.\n\n## Step 5 — Output location (S3 + KMS-encrypted SSE)\n\n```bash\naws ssm create-association \\\n  --name \"AWS-ApplyPatchBaseline\" \\\n  --targets \"Key=tag:Environment,Values=production\" \\\n  --schedule-expression \"rate(30 minutes)\" \\\n  --output-location '{\n    \"S3Location\": {\n      \"OutputS3BucketName\": \"my-ssm-output\",\n      \"OutputS3KeyPrefix\": \"ssm-output\u002F\",\n      \"OutputS3Region\": \"us-east-1\"\n    }\n  }' \\\n  --region us-east-1\n```\n\n**Verify the bucket has KMS-encrypted SSE:**\n\n```bash\naws s3api get-bucket-encryption --bucket my-ssm-output --region us-east-1\n# Expected: ServerSideEncryptionConfiguration with SSE-KMS + KMSMasterKeyID\n```\n\n**Critical:** SSM does NOT enforce SSE on the output bucket. An\nunencrypted bucket is a silent finding. The skill flags any output\nbucket without a customer-managed KMS key as REVIEW_REQUIRED. The S3\nbucket policy must allow the SSM service principal to `s3:PutObject`,\nand the KMS key policy must allow SSM to `kms:GenerateDataKey`.\n\n## Step 6 — Association status and compliance\n\n| Status | Meaning | Action |\n|---|---|---|\n| `Success` | All targeted instances ran successfully | None |\n| `Failed` | One or more instances errored; rate control may have stopped the run | Inspect per-instance output in S3 |\n| `Pending` | Association created but not yet executed | Wait, or trigger with `--apply-at-creation` |\n| `TimedOut` | Document execution exceeded timeout | Increase timeout or fix document |\n\n```bash\n# Association status + execution history\naws ssm describe-association --association-id \"\u003Cid>\" --region us-east-1\naws ssm describe-association-executions --association-id \"\u003Cid>\" --region us-east-1\n\n# Compliance reporting\naws ssm list-compliance-items --filters \"Key=ComplianceType,Values=Association\" --region us-east-1\naws ssm list-resource-compliance-summaries --filters \"Key=ComplianceType,Values=Association\" --region us-east-1\n```\n\n## Step 7 — Association versioning\n\nEach association update creates a new version (1, 2, 3, ...).\n\n```bash\naws ssm update-association \\\n  --association-id \"\u003Cid>\" \\\n  --schedule-expression \"rate(15 minutes)\" \\\n  --region us-east-1\n\naws ssm list-association-versions --association-id \"\u003Cid>\" --region us-east-1\n```\n\n**Critical:** there is no built-in rollback command. To revert, read\nthe desired version's parameters from `list-association-versions` and\nre-apply them via `update-association`.\n\n## Step 8 — Remediation on non-compliance\n\nWhen an association drifts to non-compliant, SSM can auto-remediate by\nre-applying the document.\n\n```text\nNON_COMPLIANT detected\n  → EventBridge rule pattern:\n      source: [aws.ssm]\n      detail-type: [Configuration Compliance State Change]\n      detail.status: [NON_COMPLIANT]\n  → Target: SSM Automation or Lambda → StartAssociationsOnce\n  → SSM re-applies the document → compliance flips back\n```\n\n**Manual re-run:**\n\n```bash\naws ssm start-associations-once --association-ids \"\u003Cid>\" --region us-east-1\n```\n\n**Critical:** remediation only works if the document is IDEMPOTENT. A\nnon-idempotent document (e.g., one that appends to a file) will cause\nside effects on re-run. Always verify idempotency before wiring\nremediation.\n\n## Step 9 — Multi-document associations\n\nA single association applies ONE document. To apply multiple documents\nto the same targets, create SEPARATE associations, OR build a single\ncustom step-document that runs multiple steps in sequence:\n\n```yaml\nschemaVersion: '2.2'\nname: Custom-ProvisionAndConfigure\nmainSteps:\n  - action: aws:runShellScript\n    name: installPackage\n    inputs:\n      runCommand:\n        - yum install -y httpd\n  - action: aws:runShellScript\n    name: configureService\n    inputs:\n      runCommand:\n        - systemctl enable httpd\n        - systemctl start httpd\n```\n\nUse a step-document when the steps have ordering dependencies. Use\nseparate associations when the documents are independent.\n\n## Step 10 — SSM document lifecycle\n\n```bash\n# Create\naws ssm create-document --content file:\u002F\u002Fdoc.yaml --name \"Custom-Harden\" \\\n  --document-type Command --document-format YAML --region us-east-1\n\n# Update (creates new version)\naws ssm update-document --content file:\u002F\u002Fdoc-v2.yaml --name \"Custom-Harden\" \\\n  --document-version \"1\" --region us-east-1\n\n# Set default version (associations use the default version)\naws ssm update-document-default-version --name \"Custom-Harden\" \\\n  --document-version \"2\" --region us-east-1\n```\n\n**Critical:** an association referencing a custom document always uses\nthe document's DEFAULT VERSION. To pin an association to a specific\nversion, reference it explicitly: `Custom-HardenBaseline:2`.\n\n## Step 11 — CloudWatch metrics\n\nSSM emits metrics in the `AWS\u002FSSM` namespace.\n\n| Metric | Description |\n|---|---|\n| `AssociationSuccess` | Count of successful executions |\n| `AssociationFailed` | Count of failed executions — alarm on spikes |\n| `AssociationTimeout` | Count of timed-out executions |\n| `AssociationCompliance` | 1=compliant, 0=non-compliant |\n\n## Step 12 — Recent features\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026).\n\n## NEVER do these things\n\n1. **NEVER use percentage strings for rate control.**\n   `max-concurrency: \"10%\"` behaves differently across fleet sizes.\n   Use integer counts (`max-concurrency: 10`, `max-errors: 3`).\n\n2. **NEVER use instance-ID targets for autoscaling fleets.** Instance\n   IDs are static; new instances are NOT picked up. Use tag targets.\n\n3. **NEVER configure an output S3 bucket without customer-managed\n   KMS-encrypted SSE.** SSM does not enforce SSE; an unencrypted\n   bucket is a silent finding.\n\n4. **NEVER create an association without `--apply-at-creation` for the\n   first run.** Otherwise it waits for the next scheduled tick.\n\n5. **NEVER use Unix cron syntax.** AWS cron has 6 fields starting with\n   SECONDS. `cron(0 30 2 ? * * *)` is AWS cron for 02:30 daily.\n\n6. **NEVER wire remediation for a non-idempotent document.**\n   Remediation re-applies the document; non-idempotent documents cause\n   side effects on re-run.\n\n7. **NEVER assume compliance status is computed before the first run.**\n   A newly created association shows \"Pending\" until it executes at\n   least once.\n\n8. **NEVER update a custom document without setting a default\n   version.** Associations reference the default version.\n\n9. **NEVER assume the S3 output bucket policy is correct without\n   testing.** SSM silently drops output if the bucket policy does not\n   allow the SSM service principal to `s3:PutObject`.\n\n10. **NEVER assume the association will run immediately after\n    creation.** By default, the first run happens at the next\n    scheduled execution.\n\n## Output format\n\n```text\nSSM_ASSOCIATION: \u003Cassociation-name> (\u003Cassociation-id>)\nVERDICT: OPERATION_COMPLETED | REVIEW_REQUIRED\nCHECKLIST:\n  [✓|!] Document: \u003Cdocument-name> (version \u003Cv|default>)\n  [✓|!] Targets: \u003Ctag-key>=\u003Cvalues> (dynamic) | InstanceIds=\u003Cids> (static)\n  [✓|!] Schedule: \u003Ccron|rate expression>\n  [✓|!] Apply-at-creation: ENABLED | DISABLED\n  [✓|!] Rate control: max-concurrency=\u003CN>, max-errors=\u003CN> (integer form)\n  [✓|!] Output S3: s3:\u002F\u002F\u003Cbucket>\u002F\u003Cprefix> (SSE-KMS) | UNENCRYPTED [!]\n  [✓|!] Parameters: \u003Ckey=value list>\n  [✓|!] Compliance: COMPLIANT | NON_COMPLIANT | PENDING (first run)\n  [✓|!] Status: Success | Failed | Pending\n  [✓|!] Association version: \u003Cv>\n  [✓|!] CloudWatch alarm: \u003Calarm-name or \"none\">\n  [✓|!] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ssm describe-association --association-id \u003Cassociation-id> --region \u003Cregion>\n  aws ssm describe-association-executions --association-id \u003Cassociation-id> --region \u003Cregion>\n  aws ssm list-compliance-items --filters Key=ComplianceType,Values=Association --region \u003Cregion>\n  aws s3api get-bucket-encryption --bucket \u003Coutput-bucket> --region \u003Cregion>\n```\n\n### Worked example — tag-targeted scheduled association with integer rate control and KMS-encrypted S3 output\n\n```text\nSSM_ASSOCIATION: PatchProductionFleet (a-1a2b3c4d5e6f7g8h9)\nVERDICT: OPERATION_COMPLETED\nCHECKLIST:\n  [✓] Document: AWS-ApplyPatchBaseline (default version)\n  [✓] Targets: tag:Environment=production (dynamic)\n  [✓] Schedule: rate(30 minutes)\n  [✓] Apply-at-creation: ENABLED\n  [✓] Rate control: max-concurrency=10, max-errors=3 (integer form)\n  [✓] Output S3: s3:\u002F\u002Fmy-ssm-output\u002Fssm-output\u002F (SSE-KMS, key arn:aws:kms:us-east-1:123456789012:key\u002Fabc123)\n  [✓] Parameters: Operation=Install, SnapshotId=latest\n  [✓] Compliance: COMPLIANT\n  [✓] Status: Success\n  [✓] Association version: 3\n  [✓] CloudWatch alarm: ssm-patch-failures-prod\n  [✓] Tags: Environment=production, Owner=cloudops\nVERIFICATION_COMMANDS:\n  aws ssm describe-association --association-id a-1a2b3c4d5e6f7g8h9 --region us-east-1\n  aws ssm describe-association-executions --association-id a-1a2b3c4d5e6f7g8h9 --region us-east-1\n  aws ssm list-compliance-items --filters Key=ComplianceType,Values=Association --region us-east-1\n  aws s3api get-bucket-encryption --bucket my-ssm-output --region us-east-1\n```\n\n## Error handling\n\n→ Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — six failure modes: zero targets, stuck Pending, output not delivered, Failed status, NON_COMPLIANT, rate-control stop.\n\n## References (load on demand)\n\n- [references\u002Frate-control-and-targets.md](references\u002Frate-control-and-targets.md) — pre-existing; extended with the integer-rate-control and tag-vs-instance-ID expert heuristics moved from SKILL.md.\n- [references\u002Foutput-and-compliance.md](references\u002Foutput-and-compliance.md) — pre-existing; extended with the S3 output bucket encryption expert heuristic moved from SKILL.md.\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026): association-level KMS, target-locations, calendar schedules, EventBridge triggers, compliance dashboard.\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — error-handling deep dive: zero targets, Pending stall, S3 output drop, Failed runs, NON_COMPLIANT after success, rate-control stop.\n\n## Domain\n\nAWS CloudOps \u002F AWS Systems Manager (SSM) State Manager Association\nOperations & Compliance Management.\n\n## AWS documentation\n\n- **SSM State Manager** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsystems-manager-state.html\n- **Creating associations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-assoc.html\n- **Targeting instances** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-target.html\n- **Rate control** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-rate-control.html\n- **Cron schedules** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Freference-cron-and-rate-expressions.html\n- **S3 output** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-rc-output.html\n- **Compliance** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-compliance.html\n- **Association versions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsysman-state-association-versions.html\n- **SSM documents** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fdocuments.html\n- **CloudWatch metrics for SSM** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fmonitoring-cloudwatch-metrics.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, systems-manager, ssm, state-manager, association, cloudops, operate, compliance, rate-control, ssm-document","2","Jacky Chan — AWS Community Builder","aws-cloudops","Management","0.1.0","aws, systems manager, ssm, state manager, association, create association, association schedule, association targets, rate control, max-concurrency, max-errors, compliance, association version, output location, ssm document, document lifecycle, remediation, tag targets, cloudops, operate","operate","medium","false","capability","Invoke when the user wants to create or operate an SSM State Manager association — apply a document (AWS-managed or custom) to targets on a schedule, target instances by tag (dynamic) or instance IDs (static), configure rate control (max-concurrency and max-errors as integer counts), route execution output to an S3 bucket, view association status and compliance, version an association, set up remediation when an association drifts to non-compliant, or run multi-document associations. Do NOT invoke for ad-hoc one-off command runs (use ssm-run-command skills), patch baseline creation (use ssm-patch-baseline-deployer), or session manager troubleshooting (use ssm-session-troubleshooter).","aws-orchestrator","true","OPERATION_COMPLETED | REVIEW_REQUIRED","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ssm access (and iam access for role\u002Fpolicy creation, s3 access for output bucket validation). Works with Terraform aws_ssm_association \u002F aws_ssm_document resources and CloudFormation AWS::SSM::Association \u002F AWS::SSM::Document templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fssm-association-operator",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 ssm-association-operator",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill ssm-association-operator",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill ssm-association-operator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\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","参考文档",7288,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcompliance-remediation-association.md",722,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fbaselines\u002Fcompliance-remediation-association.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Finstance-id-target-association.md",740,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fbaselines\u002Finstance-id-target-association.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-s3-kms-key.md",883,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fbaselines\u002Fmissing-s3-kms-key.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fmulti-document-step-association.md",871,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fbaselines\u002Fmulti-document-step-association.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Ftag-target-scheduled-association.md",1022,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fbaselines\u002Ftag-target-scheduled-association.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1866,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",11059,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcompliance-remediation-association.md",775,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fprompts\u002Fcompliance-remediation-association.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Finstance-id-target-association.md",629,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fprompts\u002Finstance-id-target-association.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-s3-kms-key.md",580,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fprompts\u002Fmissing-s3-kms-key.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fmulti-document-step-association.md",811,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fprompts\u002Fmulti-document-step-association.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Ftag-target-scheduled-association.md",757,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fevals\u002Fprompts\u002Ftag-target-scheduled-association.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",8350,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",944,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ferror-handling.md",1309,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Freferences\u002Ferror-handling.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Foutput-and-compliance.md",13890,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Freferences\u002Foutput-and-compliance.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Frate-control-and-targets.md",13183,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\u002Freferences\u002Frate-control-and-targets.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"skill.usf.yaml",4568,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fssm-association-operator\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",[],[]]