[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A96GY34SC4Z69TWH48STE3":3,"skill-same:01M7A96GY34SC4Z69TWH48STE3":151},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7A96GY34SC4Z69TWH48STE3","inspector2-coverage-operator",null,"Operates Amazon Inspector v2 coverage across an AWS Organization or single account — enables \u002F disables Inspector per account and region, manages EC2 coverage (SSM agent, deep inspection), ECR coverage (image scanning, rescan on push), Lambda coverage (code scanning, dependencies), surfaces coverage gaps (uncovered resources, SSM-missing instances, disabled regions), configures delegated admin for org-wide coverage, and operates the latest capabilities (Lambda code vulnerability scanning, SBOM export, EC2 deep inspection, ECR enhanced scan). Runs deterministic pre-checks (delegated admin, members, region activation, SSM online, ECR config, Lambda eligibility), emits the exact inspector2:Enable \u002F Disable \u002F UpdateOrganizationConfiguration CLI behind a CONFIRM gate, and verifies coverage post-apply. Emits a verdict (READY | BLOCKED | COMPLETED). Use when enabling Inspector, diagnosing coverage gaps, configuring delegated admin, exporting SBOMs, or rolling out Lambda code scanning.","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\u002Finspector2-coverage-operator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: inspector2-coverage-operator\ndescription: Operates Amazon Inspector v2 coverage across an AWS Organization or single account — enables \u002F disables Inspector per account and region, manages EC2 coverage (SSM agent, deep inspection), ECR coverage (image scanning, rescan on push), Lambda coverage (code scanning, dependencies), surfaces coverage gaps (uncovered resources, SSM-missing instances, disabled regions), configures delegated admin for org-wide coverage, and operates the latest capabilities (Lambda code vulnerability scanning, SBOM export, EC2 deep inspection, ECR enhanced scan). Runs deterministic pre-checks (delegated admin, members, region activation, SSM online, ECR config, Lambda eligibility), emits the exact inspector2:Enable \u002F Disable \u002F UpdateOrganizationConfiguration CLI behind a CONFIRM gate, and verifies coverage post-apply. Emits a verdict (READY | BLOCKED | COMPLETED). Use when enabling Inspector, diagnosing coverage gaps, configuring delegated admin, exporting SBOMs, or rolling out Lambda code scanning.\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline plan classification. Live-account operations use aws inspector2 enable, disable, update-organization-configuration, describe-organization-configuration, list-coverage, list-members, batch-get-member-ec2-deep-inspection-state, update-ec2-deep-inspection-configuration, list-usage-totals, batch-update-ec2-deep-inspection-state, list-filters, enable-delegated-admin-account...\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '4'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Security\n  task_type: operate\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY | BLOCKED | COMPLETED\n  when_to_use: Enabling Inspector v2 per account or region, configuring delegated admin for Organizations-wide coverage, diagnosing EC2 coverage gaps (SSM agent missing, deep inspection not enabled), ECR scanning coverage (rescan-on-push, enhanced scan), Lambda function code vulnerability scanning enablement, exporting SBOMs for audit, or verifying that 100% of in-scope resources are covered.\n  activation_triggers: enable Inspector, disable Inspector, Inspector v2 coverage, EC2 scanning coverage, ECR scanning coverage, Lambda scanning coverage, Lambda code vulnerability, Inspector delegated admin, Inspector member accounts, Inspector organization scan, Inspector coverage gap, SSM agent missing Inspector, deep inspection EC2, EC2 deep inspection, SBOM export, software bill of materials, Inspector enable region, batch update EC2 deep inspection\n  invocation_schema: 'Input: either (a) an Inspector operation intent (enable, disable, enable-delegated-admin, update-org-config, associate-member, update-ec2-deep-inspection, enable-lambda-code-scan, configure-ecr-rescan, export-sbom, diagnose-coverage) with target account\u002Fregion, resource scope, and scan types (EC2 \u002F ECR \u002F Lambda \u002F Member); OR (b) a live coverage report from `aws inspector2 list-coverage` for diagnosis. Output: deterministic OPERATION\u002FVERDICT\u002FPRE_CHECKS\u002FSTEPS\u002FPOST_VERIFY block per operation, where VERDICT is one of READY, BLOCKED, COMPLETED.'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: Amazon Inspector v2, Inspector, vulnerability scanning, EC2 scanning, ECR scanning, Lambda scanning, code vulnerability, SBOM export, software bill of materials, deep inspection, SSM agent, coverage gap, delegated admin, AWS Organizations, member account, network reachability, package vulnerability, container image scanning, Inspector delegated admin, Inspector coverage\n  tags: aws-inspector2, security, operate, vulnerability-scanning, ec2-coverage, ecr-coverage, lambda-coverage, delegated-admin, sbom-export, code-vulnerability, organizations, ssm-agent\n---\n\n# Inspector v2 Coverage Operator\n\n## What this skill does\n\nExecutes Amazon Inspector v2 coverage operations correctly and safely —\nenable\u002Fdisable Inspector per account and region, configure delegated\nadmin for Organizations, manage EC2 coverage (deep inspection, SSM\nagent enrollment), ECR coverage (rescan-on-push, enhanced scan\nfrequency), Lambda coverage (function code + dependency scanning),\nexport SBOMs, and diagnose coverage gaps. Runs deterministic\npre-checks before any state-changing CLI, emits the exact\n`inspector2:*` CLI sequence behind a CONFIRM gate, and verifies\ncoverage state after apply. Every operation surfaces the resource\ntype (EC2 \u002F ECR \u002F Lambda), the scan type, and the org-vs-standalone\nmode so the operator knows the scope.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **§ Quick reference** | Verdict thresholds + pre-check priority + coverage baselines | Before any operation |\n| **§ Mindset** | Org mode vs standalone, resource type matrix, SSM coupling | Understanding the coverage model |\n| **§ Pre-flight** | Delegated admin + member + region activation gate | Before executing any CLI |\n| **§ Process** | Per-operation planning: enable, delegated admin, member, EC2, ECR, Lambda, SBOM, diagnose | When choosing which operation |\n| **§ Common patterns** | Enable org-wide, EC2 deep inspection, ECR rescan, Lambda code scan, SBOM export | Boilerplate lookup |\n| **§ Output format** | Structured output template with VERDICT, COMMANDS, POST_VERIFY | Formatting the response |\n| **§ Anti-Patterns** | NEVER list — common mistakes | Review before risky operations |\n\n## Quick reference — verdict thresholds\n\n| Verdict | Trigger condition | Action |\n|---|---|---|\n| `BLOCKED` | One or more pre-checks failed (account not in Organizations, region not opt-in, delegated admin already set to another account, SSM agent offline, member not associated, ECR in a region Inspector disabled, Lambda layer without scan permission) | List failures, do NOT execute |\n| `READY` | All pre-checks passed; awaiting CONFIRM gate | Emit exact CLI sequence, wait for operator yes |\n| `COMPLETED` | Operation applied and post-verification passed (Inspector status ENABLED for the resource types in the target region, member ACTIVE, deep inspection activated, Lambda code scan enabled, SBOM export COMPLETED) | Emit describe output, coverage count, gap list |\n\n**Priority order for pre-checks (all must pass for READY):**\n\n1. **Delegated admin state** — `describe-organization-configuration`\n   returns whether the org is configured for auto-enable. If\n   `autoEnable` is `false`, individual member enable is required.\n2. **Account membership** — for `enable` on a member account, the\n   account must be in the Organizations root\u002FOU and associated\n   (`list-members` returns `relationshipStatus: ENABLED`).\n3. **Region opt-in** — the region must be Inspector-supported and\n   opt-in.\n4. **Resource-type scan eligibility** — EC2 requires SSM agent\n   (online within 30 min); ECR requires the repository in a\n   region where ECR scanning is enabled; Lambda requires a supported\n   runtime (Python, Node.js, Java, Docker).\n5. **Delegated admin uniqueness** — only one delegated admin per\n   org; `enable-delegated-admin-account` against a non-delegated\n   account BLOCKS.\n6. **Deep inspection state** —\n   `batch-get-member-ec2-deep-inspection-state` must show `ACTIVE`\n   for deep inspection to scan package inventory. The agent must\n   have the SSM association `AmazonInspector-ManageAWSAgent`.\n7. **ECR rescan-on-push** — without `scanOnPush: true`, images are\n   only scanned on `start-image-scan`.\n8. **Lambda code scan permission** — Lambda layers require the\n   Inspector principal `lambda:GetLayerVersion`.\n\n**Coverage baselines (2026):**\n- New EC2 instance with SSM agent online: appears in `list-coverage`\n  within ~15-30 minutes after enable.\n- New ECR image with `scanOnPush: true`: scan completes in 1-5 min.\n- New Lambda function in supported runtime: code scan completes in\n  5-30 min after first invocation or manual trigger.\n- SBOM export: minutes (single account\u002Fregion) to hours (org-wide).\n\n## Mindset\n\nThree Inspector v2 realities drive every operation:\n\n- **Org mode and standalone mode are mutually exclusive.** Once\n  delegated admin is configured, individual member enable\u002Fdisable is\n  performed BY THE DELEGATED ADMIN ACCOUNT, not by the member itself.\n  Enabling Inspector from a member under org mode returns\n  `ConflictException`. Verify `describe-organization-configuration`\n  before any member-level operation.\n\n- **Resource-type coverage is independent.** EC2, ECR, and Lambda\n  coverage are toggled separately at the org level\n  (`autoEnable.ec2\u002Fecr\u002Flambda`). `update-organization-configuration`\n  sets defaults for new member accounts; existing members keep their\n  state. A frequent mistake is enabling EC2 at the org level and\n  assuming ECR and Lambda auto-enable — they don't.\n\n- **Deep inspection requires SSM agent + association.** Standard EC2\n  scanning runs the Inspector agent via SSM; deep inspection adds\n  package-level inventory via the SSM association\n  `AmazonInspector-ManageAWSAgent`. Without that association `ACTIVE`,\n  deep inspection silently no-ops even if\n  `update-ec2-deep-inspection-configuration` succeeded.\n\n## Pre-flight: delegated admin + member + region activation gate\n\n`describe-organization-configuration` returns the org-level Inspector\nstate including `autoEnable`, `maxAccountLimitReached`, and the\ndelegated admin account ID.\n\nProbe commands moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before live-account execution.\n\n**Malformed input:** emit `VERDICT: ERROR` with reason and remediation.\n\nMoved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a pre-check fails or a resource shows a coverage gap.\n\n## Process — operation planning (apply in order)\n\n### Step 0: Expert knowledge — non-obvious Inspector behaviors\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for expert behaviors, edge cases, and recent features.\n\n### Step 1: Pre-check gate — BLOCKED if any check fails\n\nRun ALL pre-checks. If ANY fails, verdict is BLOCKED with failures\nin PRE_CHECKS. Do NOT execute.\n\n**For ALL operations:**\n1. Region is Inspector-supported and opt-in.\n2. Caller IAM role holds the required `inspector2:*` permission.\n3. Account is in Organizations (org-mode operations) OR is a\n   standalone account (non-org operations).\n\n**For enable (single account \u002F region):**\n4. `describe-organization-configuration` returns\n   `autoEnable: false` for the resource type OR the account is\n   standalone.\n5. The account is not already ENABLED for the resource type in the\n   target region.\n6. EC2: at least one SSM-managed instance exists in the region.\n7. ECR: at least one repository exists.\n8. Lambda: at least one function in a supported runtime exists.\n\n**For enable-delegated-admin:**\n4. Caller is the Organizations management account.\n5. No existing delegated admin (or being replaced explicitly).\n6. Target account is a member of the org and in the same root.\n\n**For update-organization-configuration:**\n4. Caller is the existing delegated admin account.\n5. New `autoEnable` values do not disable already-ENABLED members\n   (existing members keep their state).\n6. `maxAccountLimitReached: false`.\n\n**For associate-member:**\n4. Caller is the delegated admin.\n5. Target account is in the org.\n6. Target account is not already associated.\n\n**For update-ec2-deep-inspection-configuration:**\n4. Caller is the delegated admin (org-level) or a standalone admin.\n5. SSM association `AmazonInspector-ManageAWSAgent` is ACTIVE on\n   target instances.\n6. Target instances have `PingStatus: Online` from SSM.\n\n**For enable-lambda-code-scan (via update-org-config or per-account):**\n4. Functions in a supported runtime (python3.x, nodejs.x,\n   java11\u002F17\u002F21, provided.al2023).\n5. Inspector principal has `lambda:GetLayerVersion` on layers used.\n6. Functions in regions where Lambda scanning is supported.\n\n**For export-sbom:**\n4. Target S3 bucket grants `s3:PutObject` to the Inspector service\n   principal.\n5. KMS key `Enabled` and grants `kms:GenerateDataKey` to Inspector.\n6. Bucket and key in the same region as the export scope.\n7. No concurrent SBOM export for the same scope (one active export\n   per account\u002Fregion\u002Fformat).\n\n**For diagnose-coverage:**\n5. `list-coverage` returns the coverage report for the region.\n6. `batch-get-account-status` returns the per-resource-type state.\n7. `list-members` (org-mode) returns associated member states.\n\n### Step 2: READY — emit operation plan\n\nEmit `VERDICT: READY` with exact CLI sequence + CONFIRM gate:\n- Exact AWS CLI command with all flags populated.\n- Expected duration (15-30 min for EC2 first scan, 1-5 min for ECR,\n  5-30 min for Lambda).\n- Expected side-effects (Inspector agent installed via SSM, member\n  ENABLED, deep inspection scanning begins, SBOM export to S3).\n- CONFIRM gate prompt.\n\n### Step 3: Execute behind CONFIRM gate\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing CLI\n  (`enable`, `disable`, `enable-delegated-admin-account`,\n  `update-organization-configuration`, `associate-member`,\n  `update-ec2-deep-inspection-configuration`,\n  `batch-update-ec2-deep-inspection-state`,\n  `start-sbom-export`, `cancel-sbom-export`), emit CONFIRM prompt.\n  Do NOT execute until confirmed.\n- Snapshot current state via `batch-get-account-status --output json\n  > \u002Ftmp\u002Finspector2-$(date +%s).json` for enable\u002Fdisable;\n  `describe-organization-configuration` for org-config changes;\n  `list-sbom-export` for SBOM operations.\n- Execute the CLI.\n- For org-level changes, validate propagation to member accounts\n  (`batch-get-member-ec2-deep-inspection-state` within 5-10 min).\n\n### Step 4: Post-verification — COMPLETED\n\nALL checks must pass for `COMPLETED`:\n1. For enable: `batch-get-account-status` returns `state: ENABLED`\n   for the resource type in the target region.\n2. For delegated admin: `list-delegated-admin-accounts` returns the\n   new account with `status: ENABLED`.\n3. For org-config: `describe-organization-configuration` returns\n   the updated `autoEnable` values.\n4. For member associate: `list-members` returns the new account\n   with `relationshipStatus: ENABLED`.\n5. For EC2 deep inspection:\n   `batch-get-member-ec2-deep-inspection-state` returns `ACTIVE`.\n6. For Lambda code scan: `list-coverage` returns Lambda resources\n   with `scanType: LAMBDA_CODE` and `scanStatus: COMPLETED` (5-30\n   min after enable).\n7. For SBOM export: `list-sbom-export` returns `reportId` with\n   `status: COMPLETED`; verify the S3 object exists in the bucket.\n\nIf ANY verification fails, emit `VERDICT: ERROR` — do not claim COMPLETED.\n\n## Common patterns (boilerplate)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n## Diagnostic flows\n\nMoved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a pre-check fails or a resource shows a coverage gap.\n\n## Output format (per operation)\n\n```text\nOPERATION: \u003Cenable | disable | enable-delegated-admin | update-org-config | associate-member | update-ec2-deep-inspection | enable-lambda-code-scan | configure-ecr-rescan | export-sbom | diagnose-coverage>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Caccount-id \u002F region \u002F instance-id \u002F repository \u002F function \u002F sbom-report-id>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. \u003CCLI command with flags populated>\n  2. \u003Cwait command>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nSTATE: \u003CInspector enable state per resource type, member relationship status, deep inspection state, SBOM export status>\nNOTES: \u003Corg-mode vs standalone, resource-type matrix, scan-type coverage, SSM agent \u002F S3 \u002F KMS caveats, cost impact>\n```\n\n### Worked example — enable EC2 + ECR + Lambda (READY)\n\n```text\nOPERATION: enable\nVERDICT: READY\nTARGET: account 111111111111 region us-east-1\nPRE_CHECKS:\n  - [PASS] Region us-east-1 is Inspector-supported and opt-in\n  - [PASS] describe-organization-configuration returns autoEnable:\n    false for all resource types (standalone enable is valid)\n  - [PASS] batch-get-account-status returns state: DISABLED for EC2,\n    ECR, and LAMBDA in us-east-1\n  - [PASS] Caller IAM role holds inspector2:Enable\n  - [PASS] 12 running EC2 instances, 4 ECR repositories, 8 Lambda\n    functions in supported runtimes\nSTEPS:\n  1. CONFIRM: About to enable Inspector v2 for EC2, ECR, and Lambda\n     in account 111111111111 region us-east-1. This will install the\n     Inspector agent on 12 EC2 instances via SSM, enable ECR scanning\n     on 4 repositories, and start Lambda code scanning on 8\n     functions. Cost accrues per scan per resource per region.\n     Proceed? (yes\u002Fno)\n  2. aws inspector2 enable --account-ids 111111111111 \\\n       --client-token 1723305600 \\\n       --resource-types EC2 ECR LAMBDA \\\n       --region us-east-1\nPOST_VERIFY:\n  - (pending execution)\n  - batch-get-account-status returns state: ENABLED for EC2, ECR,\n    LAMBDA within ~5 minutes\n  - First EC2 scan within 15-30 min; ECR within 1-5 min; Lambda\n    within 5-30 min\nSTATE: pending — Inspector ENABLED within ~5 minutes\nNOTES:\n  - Standalone enable (autoEnable is false at org level or org-mode\n    not configured).\n  - Resource-type coverage is independent — each scans on its own\n    cadence.\n  - Cost accrues per scan per resource per region. Verify budget\n    via list-usage-totals before broad enablement.\n```\n\n### Worked example — enable delegated admin (READY)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n### Worked example — diagnose EC2 coverage gap (BLOCKED)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n## STRICT output contract\n\n### Required output structure\n\nEvery response MUST begin with this block — no preamble, no\nconversational opening:\n\n```text\nOPERATION: \u003Cenable | disable | enable-delegated-admin | update-org-config | associate-member | update-ec2-deep-inspection | enable-lambda-code-scan | configure-ecr-rescan | export-sbom | diagnose-coverage>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Caccount-id \u002F region \u002F instance-id \u002F repository \u002F function \u002F sbom-report-id>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. CONFIRM: About to \u003Coperation> on target \u003Ctarget> in account \u003Caccount> region \u003Cregion>. This will \u003Cconsequence>. Proceed? (yes\u002Fno)\n  2. \u003Cexact CLI command with every flag populated — no placeholders>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nSTATE: \u003CInspector enable state per resource type, member relationship status, deep inspection state, SBOM export status>\nNOTES: \u003Corg-mode vs standalone rationale, scan-type caveats, SSM\u002FS3\u002FKMS prerequisites, cost impact>\n```\n\n### FORBIDDEN output patterns\n\n- NEVER start with conversational preamble (\"Let me analyze…\") — the VERDICT block is the FIRST line, always. Use uppercase verdict values only (`READY`, `BLOCKED`, `COMPLETED`).\n- NEVER omit PRE_CHECKS — every pre-check must appear with `[PASS]` or `[FAIL]` and a specific reason for each failure.\n- NEVER enable Inspector for EC2 without surfacing the SSM-agent dependency and the cost-per-scan-per-resource caveat in NOTES.\n- NEVER list a CLI command with placeholder flags in a READY plan — every flag must be populated with actual values from the input data.\n- NEVER claim COMPLETED without every POST_VERIFY line showing `[PASS]`, and never omit the CONFIRM gate as the first STEPS entry for state-changing operations.\n\n## Anti-Patterns — NEVER do these things\n\n- NEVER call `enable-delegated-admin-account` from a member account. The call must come from the Organizations management account; member accounts receive `AccessDeniedException`. If a delegated admin already exists, the call returns `ConflictException` — surface the existing delegated admin account in NOTES.\n- NEVER assume `autoEnable: true` at the org level flips existing members. Auto-enable applies ONLY to NEW member accounts. Existing members retain their pre-update state; audit and remediate each separately via `list-members`.\n- NEVER enable EC2 deep inspection without verifying the SSM association `AmazonInspector-ManageAWSAgent` is `ACTIVE`. Deep inspection silently no-ops on instances without the association.\n- NEVER start an SBOM export without verifying the target S3 bucket grants `s3:PutObject` and the KMS key grants `kms:GenerateDataKey` to the Inspector service principal. The export silently fails with `status: FAILED`.\n- NEVER diagnose coverage from a single region's `list-coverage` and conclude org-wide coverage. Inspector coverage is per-region; aggregation requires AWS Security Hub or a custom aggregator. List regions covered and NOT covered in NOTES.\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE** before any state-changing CLI.\n- **Snapshot before enable\u002Fdisable** (`batch-get-account-status\n  --output json > \u002Ftmp\u002Finspector2-$(date +%s).json`) for diff\n  against post-apply state.\n- **Verify SSM agent online** before EC2 coverage operations.\n- **Verify S3 + KMS** for SBOM export before `start-sbom-export`.\n- **Estimate cost** via `list-usage-totals` before broad enablement.\n\n## Expert heuristic: standalone vs org-mode enable\n\n```\nORG-MODE (org has delegated admin)\n   ├─ Enabling from a member account?\n   │    └─ YES → BLOCKED — delegated admin must perform enable\n   ├─ Enabling from delegated admin?\n   │    └─ YES → use update-organization-configuration\n   │         (autoEnable applies to NEW members only)\n   │         (existing members keep state; remediate per-member)\n   ├─ Need to enable a specific resource type NOW?\n   │    └─ Use enable --account-ids \u003Clist> --resource-types \u003Clist>\n   │         from the delegated admin account\nSTANDALONE (no org, or org-mode not configured)\n   ├─ Use enable --account-ids \u003Cself> --resource-types \u003Clist>\n   ├─ ec2 \u002F ecr \u002F lambda independent — set each explicitly\n   └─ No delegated admin, no member association\n```\n\n**Per-resource-type prerequisites:**\n\n| Resource Type | What to check |\n|---|---|\n| `EC2` standard | SSM agent installed, `PingStatus: Online`, instance profile with `AmazonSSMManagedInstanceCore` |\n| `EC2` deep | Above + SSM association `AmazonInspector-ManageAWSAgent` ACTIVE |\n| `ECR` basic | Repository in a supported region; native ECR CVE list |\n| `ECR` enhanced | `ecr-enhanced` scan type; Inspector agent pulls deep package inventory |\n| `LAMBDA_FUNCTION` | Supported runtime (python\u002Fnode\u002Fjava\u002Fprovided.al2023); layers grant `lambda:GetLayerVersion` |\n| `LAMBDA_CODE` | Enabled alongside LAMBDA resource type; scans code + dependencies |\n\n**Coverage polling intervals:** EC2 standard 15-30 min; EC2 deep\n30-60 min after SSM association ACTIVE; ECR 1-5 min (basic) \u002F 5-15 min\n(enhanced); Lambda code 5-30 min after enable.\n\nALWAYS pair enable operations with a follow-up coverage audit (24-48\nhours later) — operators frequently enable Inspector and assume\ncoverage is at 100%, missing the SSM-agent-offline instances.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for expert behaviors, edge cases, and recent features.\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked examples and CLI boilerplate patterns moved from this SKILL.md\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — pre-flight attribute effects and per-resource diagnostic flows moved from this SKILL.md\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pre-flight command listing moved from this SKILL.md\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert knowledge and recent AWS features moved from this SKILL.md\n- [references\u002Fecr-ec2-lambda-coverage-guide.md](references\u002Fecr-ec2-lambda-coverage-guide.md) — per-resource-type scan mechanics and coverage gaps\n- [references\u002Forg-mode-and-delegated-admin-guide.md](references\u002Forg-mode-and-delegated-admin-guide.md) — org-mode enablement and delegated admin semantics\n\n## Domain\n\nAWS CloudOps \u002F Amazon Inspector v2 Coverage and Enablement Operations.\n\n## AWS documentation\n\n- **Amazon Inspector User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Finspector_v2.html\n- **Inspector Enablement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fenable-disable-inspector.html\n- **Inspector Organizations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fdesignating-admin.html\n- **Inspector Coverage** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Ffindings.html\n- **EC2 Deep Inspection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fec2-deep-inspection.html\n- **ECR Scanning** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fecr-scanning.html\n- **Lambda Scanning** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Flambda-scanning.html\n- **SBOM Export** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fsbom-export.html\n- **API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Finspector-v2-api.html\n- **AWS CLI inspector2 reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Finspector2\u002F\n- **Inspector Pricing** — https:\u002F\u002Faws.amazon.com\u002Finspector\u002Fpricing\u002F\n\n","# Inspector v2 Coverage Operator\n\n## What this skill does\n\nExecutes Amazon Inspector v2 coverage operations correctly and safely —\nenable\u002Fdisable Inspector per account and region, configure delegated\nadmin for Organizations, manage EC2 coverage (deep inspection, SSM\nagent enrollment), ECR coverage (rescan-on-push, enhanced scan\nfrequency), Lambda coverage (function code + dependency scanning),\nexport SBOMs, and diagnose coverage gaps. Runs deterministic\npre-checks before any state-changing CLI, emits the exact\n`inspector2:*` CLI sequence behind a CONFIRM gate, and verifies\ncoverage state after apply. Every operation surfaces the resource\ntype (EC2 \u002F ECR \u002F Lambda), the scan type, and the org-vs-standalone\nmode so the operator knows the scope.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **§ Quick reference** | Verdict thresholds + pre-check priority + coverage baselines | Before any operation |\n| **§ Mindset** | Org mode vs standalone, resource type matrix, SSM coupling | Understanding the coverage model |\n| **§ Pre-flight** | Delegated admin + member + region activation gate | Before executing any CLI |\n| **§ Process** | Per-operation planning: enable, delegated admin, member, EC2, ECR, Lambda, SBOM, diagnose | When choosing which operation |\n| **§ Common patterns** | Enable org-wide, EC2 deep inspection, ECR rescan, Lambda code scan, SBOM export | Boilerplate lookup |\n| **§ Output format** | Structured output template with VERDICT, COMMANDS, POST_VERIFY | Formatting the response |\n| **§ Anti-Patterns** | NEVER list — common mistakes | Review before risky operations |\n\n## Quick reference — verdict thresholds\n\n| Verdict | Trigger condition | Action |\n|---|---|---|\n| `BLOCKED` | One or more pre-checks failed (account not in Organizations, region not opt-in, delegated admin already set to another account, SSM agent offline, member not associated, ECR in a region Inspector disabled, Lambda layer without scan permission) | List failures, do NOT execute |\n| `READY` | All pre-checks passed; awaiting CONFIRM gate | Emit exact CLI sequence, wait for operator yes |\n| `COMPLETED` | Operation applied and post-verification passed (Inspector status ENABLED for the resource types in the target region, member ACTIVE, deep inspection activated, Lambda code scan enabled, SBOM export COMPLETED) | Emit describe output, coverage count, gap list |\n\n**Priority order for pre-checks (all must pass for READY):**\n\n1. **Delegated admin state** — `describe-organization-configuration`\n   returns whether the org is configured for auto-enable. If\n   `autoEnable` is `false`, individual member enable is required.\n2. **Account membership** — for `enable` on a member account, the\n   account must be in the Organizations root\u002FOU and associated\n   (`list-members` returns `relationshipStatus: ENABLED`).\n3. **Region opt-in** — the region must be Inspector-supported and\n   opt-in.\n4. **Resource-type scan eligibility** — EC2 requires SSM agent\n   (online within 30 min); ECR requires the repository in a\n   region where ECR scanning is enabled; Lambda requires a supported\n   runtime (Python, Node.js, Java, Docker).\n5. **Delegated admin uniqueness** — only one delegated admin per\n   org; `enable-delegated-admin-account` against a non-delegated\n   account BLOCKS.\n6. **Deep inspection state** —\n   `batch-get-member-ec2-deep-inspection-state` must show `ACTIVE`\n   for deep inspection to scan package inventory. The agent must\n   have the SSM association `AmazonInspector-ManageAWSAgent`.\n7. **ECR rescan-on-push** — without `scanOnPush: true`, images are\n   only scanned on `start-image-scan`.\n8. **Lambda code scan permission** — Lambda layers require the\n   Inspector principal `lambda:GetLayerVersion`.\n\n**Coverage baselines (2026):**\n- New EC2 instance with SSM agent online: appears in `list-coverage`\n  within ~15-30 minutes after enable.\n- New ECR image with `scanOnPush: true`: scan completes in 1-5 min.\n- New Lambda function in supported runtime: code scan completes in\n  5-30 min after first invocation or manual trigger.\n- SBOM export: minutes (single account\u002Fregion) to hours (org-wide).\n\n## Mindset\n\nThree Inspector v2 realities drive every operation:\n\n- **Org mode and standalone mode are mutually exclusive.** Once\n  delegated admin is configured, individual member enable\u002Fdisable is\n  performed BY THE DELEGATED ADMIN ACCOUNT, not by the member itself.\n  Enabling Inspector from a member under org mode returns\n  `ConflictException`. Verify `describe-organization-configuration`\n  before any member-level operation.\n\n- **Resource-type coverage is independent.** EC2, ECR, and Lambda\n  coverage are toggled separately at the org level\n  (`autoEnable.ec2\u002Fecr\u002Flambda`). `update-organization-configuration`\n  sets defaults for new member accounts; existing members keep their\n  state. A frequent mistake is enabling EC2 at the org level and\n  assuming ECR and Lambda auto-enable — they don't.\n\n- **Deep inspection requires SSM agent + association.** Standard EC2\n  scanning runs the Inspector agent via SSM; deep inspection adds\n  package-level inventory via the SSM association\n  `AmazonInspector-ManageAWSAgent`. Without that association `ACTIVE`,\n  deep inspection silently no-ops even if\n  `update-ec2-deep-inspection-configuration` succeeded.\n\n## Pre-flight: delegated admin + member + region activation gate\n\n`describe-organization-configuration` returns the org-level Inspector\nstate including `autoEnable`, `maxAccountLimitReached`, and the\ndelegated admin account ID.\n\nProbe commands moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before live-account execution.\n\n**Malformed input:** emit `VERDICT: ERROR` with reason and remediation.\n\nMoved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a pre-check fails or a resource shows a coverage gap.\n\n## Process — operation planning (apply in order)\n\n### Step 0: Expert knowledge — non-obvious Inspector behaviors\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for expert behaviors, edge cases, and recent features.\n\n### Step 1: Pre-check gate — BLOCKED if any check fails\n\nRun ALL pre-checks. If ANY fails, verdict is BLOCKED with failures\nin PRE_CHECKS. Do NOT execute.\n\n**For ALL operations:**\n1. Region is Inspector-supported and opt-in.\n2. Caller IAM role holds the required `inspector2:*` permission.\n3. Account is in Organizations (org-mode operations) OR is a\n   standalone account (non-org operations).\n\n**For enable (single account \u002F region):**\n4. `describe-organization-configuration` returns\n   `autoEnable: false` for the resource type OR the account is\n   standalone.\n5. The account is not already ENABLED for the resource type in the\n   target region.\n6. EC2: at least one SSM-managed instance exists in the region.\n7. ECR: at least one repository exists.\n8. Lambda: at least one function in a supported runtime exists.\n\n**For enable-delegated-admin:**\n4. Caller is the Organizations management account.\n5. No existing delegated admin (or being replaced explicitly).\n6. Target account is a member of the org and in the same root.\n\n**For update-organization-configuration:**\n4. Caller is the existing delegated admin account.\n5. New `autoEnable` values do not disable already-ENABLED members\n   (existing members keep their state).\n6. `maxAccountLimitReached: false`.\n\n**For associate-member:**\n4. Caller is the delegated admin.\n5. Target account is in the org.\n6. Target account is not already associated.\n\n**For update-ec2-deep-inspection-configuration:**\n4. Caller is the delegated admin (org-level) or a standalone admin.\n5. SSM association `AmazonInspector-ManageAWSAgent` is ACTIVE on\n   target instances.\n6. Target instances have `PingStatus: Online` from SSM.\n\n**For enable-lambda-code-scan (via update-org-config or per-account):**\n4. Functions in a supported runtime (python3.x, nodejs.x,\n   java11\u002F17\u002F21, provided.al2023).\n5. Inspector principal has `lambda:GetLayerVersion` on layers used.\n6. Functions in regions where Lambda scanning is supported.\n\n**For export-sbom:**\n4. Target S3 bucket grants `s3:PutObject` to the Inspector service\n   principal.\n5. KMS key `Enabled` and grants `kms:GenerateDataKey` to Inspector.\n6. Bucket and key in the same region as the export scope.\n7. No concurrent SBOM export for the same scope (one active export\n   per account\u002Fregion\u002Fformat).\n\n**For diagnose-coverage:**\n5. `list-coverage` returns the coverage report for the region.\n6. `batch-get-account-status` returns the per-resource-type state.\n7. `list-members` (org-mode) returns associated member states.\n\n### Step 2: READY — emit operation plan\n\nEmit `VERDICT: READY` with exact CLI sequence + CONFIRM gate:\n- Exact AWS CLI command with all flags populated.\n- Expected duration (15-30 min for EC2 first scan, 1-5 min for ECR,\n  5-30 min for Lambda).\n- Expected side-effects (Inspector agent installed via SSM, member\n  ENABLED, deep inspection scanning begins, SBOM export to S3).\n- CONFIRM gate prompt.\n\n### Step 3: Execute behind CONFIRM gate\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing CLI\n  (`enable`, `disable`, `enable-delegated-admin-account`,\n  `update-organization-configuration`, `associate-member`,\n  `update-ec2-deep-inspection-configuration`,\n  `batch-update-ec2-deep-inspection-state`,\n  `start-sbom-export`, `cancel-sbom-export`), emit CONFIRM prompt.\n  Do NOT execute until confirmed.\n- Snapshot current state via `batch-get-account-status --output json\n  > \u002Ftmp\u002Finspector2-$(date +%s).json` for enable\u002Fdisable;\n  `describe-organization-configuration` for org-config changes;\n  `list-sbom-export` for SBOM operations.\n- Execute the CLI.\n- For org-level changes, validate propagation to member accounts\n  (`batch-get-member-ec2-deep-inspection-state` within 5-10 min).\n\n### Step 4: Post-verification — COMPLETED\n\nALL checks must pass for `COMPLETED`:\n1. For enable: `batch-get-account-status` returns `state: ENABLED`\n   for the resource type in the target region.\n2. For delegated admin: `list-delegated-admin-accounts` returns the\n   new account with `status: ENABLED`.\n3. For org-config: `describe-organization-configuration` returns\n   the updated `autoEnable` values.\n4. For member associate: `list-members` returns the new account\n   with `relationshipStatus: ENABLED`.\n5. For EC2 deep inspection:\n   `batch-get-member-ec2-deep-inspection-state` returns `ACTIVE`.\n6. For Lambda code scan: `list-coverage` returns Lambda resources\n   with `scanType: LAMBDA_CODE` and `scanStatus: COMPLETED` (5-30\n   min after enable).\n7. For SBOM export: `list-sbom-export` returns `reportId` with\n   `status: COMPLETED`; verify the S3 object exists in the bucket.\n\nIf ANY verification fails, emit `VERDICT: ERROR` — do not claim COMPLETED.\n\n## Common patterns (boilerplate)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n## Diagnostic flows\n\nMoved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a pre-check fails or a resource shows a coverage gap.\n\n## Output format (per operation)\n\n```text\nOPERATION: \u003Cenable | disable | enable-delegated-admin | update-org-config | associate-member | update-ec2-deep-inspection | enable-lambda-code-scan | configure-ecr-rescan | export-sbom | diagnose-coverage>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Caccount-id \u002F region \u002F instance-id \u002F repository \u002F function \u002F sbom-report-id>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. \u003CCLI command with flags populated>\n  2. \u003Cwait command>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nSTATE: \u003CInspector enable state per resource type, member relationship status, deep inspection state, SBOM export status>\nNOTES: \u003Corg-mode vs standalone, resource-type matrix, scan-type coverage, SSM agent \u002F S3 \u002F KMS caveats, cost impact>\n```\n\n### Worked example — enable EC2 + ECR + Lambda (READY)\n\n```text\nOPERATION: enable\nVERDICT: READY\nTARGET: account 111111111111 region us-east-1\nPRE_CHECKS:\n  - [PASS] Region us-east-1 is Inspector-supported and opt-in\n  - [PASS] describe-organization-configuration returns autoEnable:\n    false for all resource types (standalone enable is valid)\n  - [PASS] batch-get-account-status returns state: DISABLED for EC2,\n    ECR, and LAMBDA in us-east-1\n  - [PASS] Caller IAM role holds inspector2:Enable\n  - [PASS] 12 running EC2 instances, 4 ECR repositories, 8 Lambda\n    functions in supported runtimes\nSTEPS:\n  1. CONFIRM: About to enable Inspector v2 for EC2, ECR, and Lambda\n     in account 111111111111 region us-east-1. This will install the\n     Inspector agent on 12 EC2 instances via SSM, enable ECR scanning\n     on 4 repositories, and start Lambda code scanning on 8\n     functions. Cost accrues per scan per resource per region.\n     Proceed? (yes\u002Fno)\n  2. aws inspector2 enable --account-ids 111111111111 \\\n       --client-token 1723305600 \\\n       --resource-types EC2 ECR LAMBDA \\\n       --region us-east-1\nPOST_VERIFY:\n  - (pending execution)\n  - batch-get-account-status returns state: ENABLED for EC2, ECR,\n    LAMBDA within ~5 minutes\n  - First EC2 scan within 15-30 min; ECR within 1-5 min; Lambda\n    within 5-30 min\nSTATE: pending — Inspector ENABLED within ~5 minutes\nNOTES:\n  - Standalone enable (autoEnable is false at org level or org-mode\n    not configured).\n  - Resource-type coverage is independent — each scans on its own\n    cadence.\n  - Cost accrues per scan per resource per region. Verify budget\n    via list-usage-totals before broad enablement.\n```\n\n### Worked example — enable delegated admin (READY)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n### Worked example — diagnose EC2 coverage gap (BLOCKED)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a secondary example or CLI pattern.\n\n## STRICT output contract\n\n### Required output structure\n\nEvery response MUST begin with this block — no preamble, no\nconversational opening:\n\n```text\nOPERATION: \u003Cenable | disable | enable-delegated-admin | update-org-config | associate-member | update-ec2-deep-inspection | enable-lambda-code-scan | configure-ecr-rescan | export-sbom | diagnose-coverage>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Caccount-id \u002F region \u002F instance-id \u002F repository \u002F function \u002F sbom-report-id>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. CONFIRM: About to \u003Coperation> on target \u003Ctarget> in account \u003Caccount> region \u003Cregion>. This will \u003Cconsequence>. Proceed? (yes\u002Fno)\n  2. \u003Cexact CLI command with every flag populated — no placeholders>\nPOST_VERIFY:\n  - [PASS] \u003Cverification description>\n  - [FAIL] \u003Cverification description> — \u003Creason>\nSTATE: \u003CInspector enable state per resource type, member relationship status, deep inspection state, SBOM export status>\nNOTES: \u003Corg-mode vs standalone rationale, scan-type caveats, SSM\u002FS3\u002FKMS prerequisites, cost impact>\n```\n\n### FORBIDDEN output patterns\n\n- NEVER start with conversational preamble (\"Let me analyze…\") — the VERDICT block is the FIRST line, always. Use uppercase verdict values only (`READY`, `BLOCKED`, `COMPLETED`).\n- NEVER omit PRE_CHECKS — every pre-check must appear with `[PASS]` or `[FAIL]` and a specific reason for each failure.\n- NEVER enable Inspector for EC2 without surfacing the SSM-agent dependency and the cost-per-scan-per-resource caveat in NOTES.\n- NEVER list a CLI command with placeholder flags in a READY plan — every flag must be populated with actual values from the input data.\n- NEVER claim COMPLETED without every POST_VERIFY line showing `[PASS]`, and never omit the CONFIRM gate as the first STEPS entry for state-changing operations.\n\n## Anti-Patterns — NEVER do these things\n\n- NEVER call `enable-delegated-admin-account` from a member account. The call must come from the Organizations management account; member accounts receive `AccessDeniedException`. If a delegated admin already exists, the call returns `ConflictException` — surface the existing delegated admin account in NOTES.\n- NEVER assume `autoEnable: true` at the org level flips existing members. Auto-enable applies ONLY to NEW member accounts. Existing members retain their pre-update state; audit and remediate each separately via `list-members`.\n- NEVER enable EC2 deep inspection without verifying the SSM association `AmazonInspector-ManageAWSAgent` is `ACTIVE`. Deep inspection silently no-ops on instances without the association.\n- NEVER start an SBOM export without verifying the target S3 bucket grants `s3:PutObject` and the KMS key grants `kms:GenerateDataKey` to the Inspector service principal. The export silently fails with `status: FAILED`.\n- NEVER diagnose coverage from a single region's `list-coverage` and conclude org-wide coverage. Inspector coverage is per-region; aggregation requires AWS Security Hub or a custom aggregator. List regions covered and NOT covered in NOTES.\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE** before any state-changing CLI.\n- **Snapshot before enable\u002Fdisable** (`batch-get-account-status\n  --output json > \u002Ftmp\u002Finspector2-$(date +%s).json`) for diff\n  against post-apply state.\n- **Verify SSM agent online** before EC2 coverage operations.\n- **Verify S3 + KMS** for SBOM export before `start-sbom-export`.\n- **Estimate cost** via `list-usage-totals` before broad enablement.\n\n## Expert heuristic: standalone vs org-mode enable\n\n```\nORG-MODE (org has delegated admin)\n   ├─ Enabling from a member account?\n   │    └─ YES → BLOCKED — delegated admin must perform enable\n   ├─ Enabling from delegated admin?\n   │    └─ YES → use update-organization-configuration\n   │         (autoEnable applies to NEW members only)\n   │         (existing members keep state; remediate per-member)\n   ├─ Need to enable a specific resource type NOW?\n   │    └─ Use enable --account-ids \u003Clist> --resource-types \u003Clist>\n   │         from the delegated admin account\nSTANDALONE (no org, or org-mode not configured)\n   ├─ Use enable --account-ids \u003Cself> --resource-types \u003Clist>\n   ├─ ec2 \u002F ecr \u002F lambda independent — set each explicitly\n   └─ No delegated admin, no member association\n```\n\n**Per-resource-type prerequisites:**\n\n| Resource Type | What to check |\n|---|---|\n| `EC2` standard | SSM agent installed, `PingStatus: Online`, instance profile with `AmazonSSMManagedInstanceCore` |\n| `EC2` deep | Above + SSM association `AmazonInspector-ManageAWSAgent` ACTIVE |\n| `ECR` basic | Repository in a supported region; native ECR CVE list |\n| `ECR` enhanced | `ecr-enhanced` scan type; Inspector agent pulls deep package inventory |\n| `LAMBDA_FUNCTION` | Supported runtime (python\u002Fnode\u002Fjava\u002Fprovided.al2023); layers grant `lambda:GetLayerVersion` |\n| `LAMBDA_CODE` | Enabled alongside LAMBDA resource type; scans code + dependencies |\n\n**Coverage polling intervals:** EC2 standard 15-30 min; EC2 deep\n30-60 min after SSM association ACTIVE; ECR 1-5 min (basic) \u002F 5-15 min\n(enhanced); Lambda code 5-30 min after enable.\n\nALWAYS pair enable operations with a follow-up coverage audit (24-48\nhours later) — operators frequently enable Inspector and assume\ncoverage is at 100%, missing the SSM-agent-offline instances.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for expert behaviors, edge cases, and recent features.\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked examples and CLI boilerplate patterns moved from this SKILL.md\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — pre-flight attribute effects and per-resource diagnostic flows moved from this SKILL.md\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pre-flight command listing moved from this SKILL.md\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert knowledge and recent AWS features moved from this SKILL.md\n- [references\u002Fecr-ec2-lambda-coverage-guide.md](references\u002Fecr-ec2-lambda-coverage-guide.md) — per-resource-type scan mechanics and coverage gaps\n- [references\u002Forg-mode-and-delegated-admin-guide.md](references\u002Forg-mode-and-delegated-admin-guide.md) — org-mode enablement and delegated admin semantics\n\n## Domain\n\nAWS CloudOps \u002F Amazon Inspector v2 Coverage and Enablement Operations.\n\n## AWS documentation\n\n- **Amazon Inspector User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Finspector_v2.html\n- **Inspector Enablement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fenable-disable-inspector.html\n- **Inspector Organizations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fdesignating-admin.html\n- **Inspector Coverage** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Ffindings.html\n- **EC2 Deep Inspection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fec2-deep-inspection.html\n- **ECR Scanning** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fecr-scanning.html\n- **Lambda Scanning** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Flambda-scanning.html\n- **SBOM Export** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Fsbom-export.html\n- **API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Finspector\u002Flatest\u002Fuser\u002Finspector-v2-api.html\n- **AWS CLI inspector2 reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Finspector2\u002F\n- **Inspector Pricing** — https:\u002F\u002Faws.amazon.com\u002Finspector\u002Fpricing\u002F\n\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":42},{"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,"requires_llm":37,"verdict_shape":38,"lifecycle_status":39,"invocation_schema":40,"supports_pipeline":37,"activation_triggers":41},"aws-inspector2, security, operate, vulnerability-scanning, ec2-coverage, ecr-coverage, lambda-coverage, delegated-admin, sbom-export, code-vulnerability, organizations, ssm-agent","4","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.1.0","Amazon Inspector v2, Inspector, vulnerability scanning, EC2 scanning, ECR scanning, Lambda scanning, code vulnerability, SBOM export, software bill of materials, deep inspection, SSM agent, coverage gap, delegated admin, AWS Organizations, member account, network reachability, package vulnerability, container image scanning, Inspector delegated admin, Inspector coverage","operate","high","false","capability","Enabling Inspector v2 per account or region, configuring delegated admin for Organizations-wide coverage, diagnosing EC2 coverage gaps (SSM agent missing, deep inspection not enabled), ECR scanning coverage (rescan-on-push, enhanced scan), Lambda function code vulnerability scanning enablement, exporting SBOMs for audit, or verifying that 100% of in-scope resources are covered.","true","READY | BLOCKED | COMPLETED","active","Input: either (a) an Inspector operation intent (enable, disable, enable-delegated-admin, update-org-config, associate-member, update-ec2-deep-inspection, enable-lambda-code-scan, configure-ecr-rescan, export-sbom, diagnose-coverage) with target account\u002Fregion, resource scope, and scan types (EC2 \u002F ECR \u002F Lambda \u002F Member); OR (b) a live coverage report from `aws inspector2 list-coverage` for diagnosis. Output: deterministic OPERATION\u002FVERDICT\u002FPRE_CHECKS\u002FSTEPS\u002FPOST_VERIFY block per operation, where VERDICT is one of READY, BLOCKED, COMPLETED.","enable Inspector, disable Inspector, Inspector v2 coverage, EC2 scanning coverage, ECR scanning coverage, Lambda scanning coverage, Lambda code vulnerability, Inspector delegated admin, Inspector member accounts, Inspector organization scan, Inspector coverage gap, SSM agent missing Inspector, deep inspection EC2, EC2 deep inspection, SBOM export, software bill of materials, Inspector enable region, batch update EC2 deep inspection","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline plan classification. Live-account operations use aws inspector2 enable, disable, update-organization-configuration, describe-organization-configuration, list-coverage, list-members, batch-get-member-ec2-deep-inspection-state, update-ec2-deep-inspection-configuration, list-usage-totals, batch-update-ec2-deep-inspection-state, list-filters, enable-delegated-admin-account...","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Finspector2-coverage-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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill inspector2-coverage-operator",{"tool":57,"command":58},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill inspector2-coverage-operator",{"tool":60,"command":61},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill inspector2-coverage-operator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",8269,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Feval\u002Ftest-cases.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Fbaselines\u002Fdelegated-admin-ready.md",402,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fbaselines\u002Fdelegated-admin-ready.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Fbaselines\u002Fecr-rescan-ready.md",426,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fbaselines\u002Fecr-rescan-ready.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"evals\u002Fbaselines\u002Fenable-standalone-ready.md",386,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fbaselines\u002Fenable-standalone-ready.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"evals\u002Fbaselines\u002Fmember-enable-blocked.md",415,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fbaselines\u002Fmember-enable-blocked.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fbaselines\u002Fsbom-export-completed.md",430,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fbaselines\u002Fsbom-export-completed.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"evals\u002Feval_config.yaml",1764,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Feval_config.yaml",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"evals\u002Fevals.json",4288,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fevals.json",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"evals\u002Fprompts\u002Fdelegated-admin-ready.md",936,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fprompts\u002Fdelegated-admin-ready.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"evals\u002Fprompts\u002Fecr-rescan-ready.md",756,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fprompts\u002Fecr-rescan-ready.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"evals\u002Fprompts\u002Fenable-standalone-ready.md",1192,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fprompts\u002Fenable-standalone-ready.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"evals\u002Fprompts\u002Fmember-enable-blocked.md",767,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fprompts\u002Fmember-enable-blocked.md",{"path":116,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":117,"sourceHtmlUrl":118},"evals\u002Fprompts\u002Fsbom-export-completed.md",1260,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fevals\u002Fprompts\u002Fsbom-export-completed.md",{"path":120,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":121,"sourceHtmlUrl":122},"examples\u002FREADME.md",8253,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fexamples\u002FREADME.md",{"path":124,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fadvanced-patterns.md",4195,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Fadvanced-patterns.md",{"path":128,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fdiagnostic-commands.md",1092,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Fdiagnostic-commands.md",{"path":132,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fecr-ec2-lambda-coverage-guide.md",4907,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Fecr-ec2-lambda-coverage-guide.md",{"path":136,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Ferror-handling.md",3142,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Ferror-handling.md",{"path":140,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Forg-mode-and-delegated-admin-guide.md",3199,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Forg-mode-and-delegated-admin-guide.md",{"path":144,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fworked-examples.md",5593,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Freferences\u002Fworked-examples.md",{"path":148,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":149,"sourceHtmlUrl":150},"skill.usf.yaml",4728,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Finspector2-coverage-operator\u002Fskill.usf.yaml",[152,159,166,173,180,187],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"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":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"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":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"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":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"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":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"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":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"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",[],[]]