[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AA2R0M7MPBDY00Y9C3AVJW":3,"skill-same:01M7AA2R0M7MPBDY00Y9C3AVJW":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7AA2R0M7MPBDY00Y9C3AVJW","macie-data-discovery-operator",null,"Operates Amazon Macie data discovery lifecycle — enables Macie (org-level delegated admin), creates classification jobs (one-time vs scheduled, S3 scope), configures managed data identifiers (PII, financial, credentials), creates custom data identifiers (Regex patterns), manages findings (policy:IAMUser\u002FS3, sensitiveData:S3Object), configures suppression rules, enables automated ML-based discovery, integrates with Security Hub, wires Lambda \u002F Step Functions for auto-remediation. Runs deterministic pre-checks (Macie enabled, delegated admin, S3 scope, IAM), emits exact CLI behind a CONFIRM gate, verifies post-apply state. Emits a verdict (READY | BLOCKED | COMPLETED) per operation. Use when enabling Macie, creating classification jobs, writing custom regex identifiers, suppressing findings, forwarding to Security Hub, or building PII auto-remediation. Triggers: enable Macie, delegated admin, classification job, custom data identifier, Macie findings, Security Hub, automated discovery, remediation Lambda.","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\u002Fmacie-data-discovery-operator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: macie-data-discovery-operator\ndescription: 'Operates Amazon Macie data discovery lifecycle — enables Macie (org-level delegated admin), creates classification jobs (one-time vs scheduled, S3 scope), configures managed data identifiers (PII, financial, credentials), creates custom data identifiers (Regex patterns), manages findings (policy:IAMUser\u002FS3, sensitiveData:S3Object), configures suppression rules, enables automated ML-based discovery, integrates with Security Hub, wires Lambda \u002F Step Functions for auto-remediation. Runs deterministic pre-checks (Macie enabled, delegated admin, S3 scope, IAM), emits exact CLI behind a CONFIRM gate, verifies post-apply state. Emits a verdict (READY | BLOCKED | COMPLETED) per operation. Use when enabling Macie, creating classification jobs, writing custom regex identifiers, suppressing findings, forwarding to Security Hub, or building PII auto-remediation. Triggers: enable Macie, delegated admin, classification job, custom data identifier, Macie findings, Security Hub, automated discovery, remediation Lambda.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live operations: AWS CLI v2 with macie2, s3, iam, sts, securityhub, lambda, and stepfunctions access. Works with Terraform aws_macie2_account \u002F aws_macie2_classification_job \u002F aws_macie2_custom_data_identifier resources and CloudFormation AWS::Macie::* templates.'\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  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, macie, security, cloudops, operate, data-discovery, pii-detection, classification, remediation, security-hub, sensitive-data\n  dependencies: aws-orchestrator\n  keywords: aws, macie, data discovery, cloudops, operate, classification, pii, managed data identifiers, custom data identifiers, regex, findings, suppression rules, automated discovery, security hub, lambda remediation, step functions, delegated admin, s3 scanning, sensitive data, data loss prevention\n  when_to_use: Invoke when the user wants to enable Macie (standalone or org-level delegated admin), create or manage classification jobs (one-time or scheduled), configure managed data identifiers, create custom regex-based data identifiers, manage findings (policy or sensitive-data types), configure suppression rules, enable automated ML-based discovery, forward findings to Security Hub, wire Lambda or Step Functions for auto-remediation of exposed PII, or aggregate cross-account Macie findings. Do NOT invoke for Amazon GuardDuty threat detection, AWS Config rule evaluation, or Security Hub control management (use guardduty-finding-triage or securityhub-finding-triage).\n---\n\n# Macie Data Discovery Operator\n\nAn AWS CloudOps agent skill that operates Amazon Macie data discovery\nlifecycle operations correctly and safely. Runs deterministic pre-checks\nbefore any state-changing CLI, emits the exact CLI behind a CONFIRM gate,\nand verifies state transitions after apply.\n\n## What this skill does\n\nExecutes Macie lifecycle operations: enabling Macie (standalone or\norg-level delegated admin), creating classification jobs (one-time or\nscheduled), configuring managed and custom data identifiers, managing\nfindings and suppression rules, enabling automated ML-based discovery,\nintegrating with Security Hub, and wiring Lambda\u002FStep Functions for\nauto-remediation. Every operation surfaces finding scope, detection\ncoverage, and remediation posture.\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 | classify | custom-id | findings | suppress | auto-discovery | security-hub | remediate | aggregate>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Cmacie-resource-name>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. CONFIRM: About to \u003Coperation> on \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: \u003Cjob status \u002F finding state \u002F Macie status after apply>\nNOTES: \u003Cdetection coverage rationale, finding severity, remediation caveats>\n```\n\n### FORBIDDEN output patterns\n\n- NEVER start with conversational preamble (\"Let me analyze…\") — the\n  VERDICT block is the FIRST line, always. Use uppercase verdict values\n  only (`READY`, `BLOCKED`, `COMPLETED`).\n- NEVER omit PRE_CHECKS — every pre-check must appear with `[PASS]` or\n  `[FAIL]` and a specific reason for each failure.\n- NEVER emit a CLI command with placeholder flags in a READY plan —\n  every flag must be populated with actual values from the input data.\n- NEVER claim COMPLETED without every POST_VERIFY line showing `[PASS]`,\n  and never omit the CONFIRM gate as the first STEPS entry for\n  state-changing operations.\n- NEVER classify as READY if Macie is not enabled in the target account\n  or region — Macie operations fail silently without enablement.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| §\"Mindset\" | Understanding the Macie detection model |\n| §\"Pre-flight\" | Macie enablement + delegated admin gate |\n| §\"Step 1 — Enable Macie\" | Org-level delegated admin setup |\n| §\"Step 2 — Classification jobs\" | One-time vs scheduled S3 scanning |\n| §\"Step 3 — Managed data identifiers\" | PII \u002F financial \u002F credential types |\n| §\"Step 4 — Custom data identifiers\" | Regex-based detection |\n| §\"Step 5 — Findings management\" | Policy and sensitive-data findings |\n| §\"Step 6 — Suppression rules\" | False-positive filtering |\n| §\"Step 7 — Automated discovery\" | ML-based continuous scanning |\n| §\"Step 8 — Security Hub integration\" | Findings forwarding |\n| §\"Step 9 — Auto-remediation\" | Lambda + Step Functions |\n| §\"NEVER do these things\" | Review before risky operations |\n| §\"Output format\" | Structured output template |\n| references\u002Fdetection-and-remediation.md | Deep identifier + remediation patterns |\n| references\u002Foperating-cli-commands.md | Copy-pasteable CLI sequence |\n\n## Mindset\n\nThree Macie realities drive every operation:\n\n→ Extended Mindset rationale moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Pre-flight: Macie enablement + delegated admin gate\n\nRun before any operation. `get-macie-session` returns the Macie\nenablement status. `get-administrator-account` returns the delegated\nadmin (org-level).\n\n→ Live-account pre-flight command listing moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n| Attribute | Effect on operation |\n|---|---|\n| Macie `status: PAUSED` | Classification jobs do not run. Findings not published. Re-enable via `enable-macie-session`. |\n| Delegated admin not set | Org-level operations (cross-account) fail. Must delegate admin first. |\n| No existing classification job | New job creation is safe. |\n| Bucket not in Macie account | `s3:Bucket*` permissions needed for Macie service role. |\n| `findingPublishingFrequency` unset | Defaults to 15 min. Critical findings may delay. |\n\n**Malformed input:** emit `VERDICT: ERROR` with reason and remediation.\n\n## Expert heuristic: finding severity and detection coverage\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## 10-step operating procedure\n\n### Step 1 — Enable Macie (standalone or org-level delegated admin)\n\nMacie must be enabled before any other operation.\n\n**Standalone (single account):**\n\n```bash\naws macie2 enable-macie-session \\\n  --finding-publishing-frequency FIFTEEN_MINUTES \\\n  --status ENABLED\n```\n\n**Org-level delegated admin:**\n\n```bash\n# 1. Designate the admin account (run in management account)\naws macie2 enable-organization-admin-account \\\n  --admin-account-id 123456789012\n\n# 2. In the delegated admin account, enable Macie for the org\naws macie2 enable-macie-session \\\n  --finding-publishing-frequency FIFTEEN_MINUTES \\\n  --status ENABLED\n\n# 3. Configure auto-enable for new member accounts\naws macie2 update-organization-configuration \\\n  --auto-enable true\n```\n\n**Common mistake:** enabling Macie in the management account instead of\ndelegating to a dedicated security admin account. Org-level Macie\nshould use a designated admin account that manages all member accounts.\n\n### Step 2 — Classification jobs (one-time vs scheduled)\n\nClassification jobs scan S3 buckets for sensitive data.\n\n**One-time job:**\n\n```bash\naws macie2 create-classification-job \\\n  --name \"pii-scan-2026-08\" \\\n  --job-type ONE_TIME \\\n  --s3-job-definition \\\n    bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket,financial-records]}]' \\\n  --managed-data-identifier-selector-ids \\\n    USA_SOCIAL_SECURITY_NUMBER USA_PASSPORT_NUMBER CREDIT_CARD_NUMBER \\\n    EMAIL_ADDRESS PHONE_NUMBER \\\n  --description \"One-time PII scan of production data buckets\"\n```\n\n**Scheduled job (CRON):**\n\n```bash\naws macie2 create-classification-job \\\n  --name \"weekly-pii-scan\" \\\n  --job-type SCHEDULED \\\n  --schedule-frequency '{dailySchedule:{}}' \\\n  --s3-job-definition \\\n    bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket]}]' \\\n  --managed-data-identifier-selector ALL \\\n  --description \"Weekly scheduled PII scan\"\n```\n\n**Schedule options:**\n- `{dailySchedule:{}}` — runs daily.\n- `{weeklySchedule:{dayOfWeek=WEDNESDAY}}` — runs weekly.\n- `{monthlySchedule:{dayOfMonth=15}}` — runs monthly.\n\n**Common mistake:** not scoping the S3 bucket list. A job scanning ALL\nbuckets is expensive and noisy. Scope to specific buckets or use bucket\ncriteria (tags, prefixes) for targeted scanning.\n\n### Step 3 — Managed data identifiers (PII, financial, credentials)\n\nMacie provides ~150+ managed data identifiers. Select relevant\nidentifiers per region and data type.\n\n**Categories:**\n- **PII:** SSN, passport, driver's license, national ID (region-specific).\n- **Financial:** credit card numbers, bank account, SWIFT codes.\n- **Credentials:** AWS access keys, private keys, API tokens.\n- **Personal:** email, phone, address, name, date of birth.\n\n**Selection strategies:**\n\n```bash\n# Option A: ALL managed identifiers (comprehensive, expensive)\n--managed-data-identifier-selector ALL\n\n# Option B: Specific identifiers (targeted, cost-efficient)\n--managed-data-identifier-selector-ids \\\n  USA_SOCIAL_SECURITY_NUMBER USA_PASSPORT_NUMBER CREDIT_CARD_NUMBER\n\n# Option C: RECOMMENDED (Macie selects based on bucket content sampling)\n--managed-data-identifier-selector RECOMMENDED\n```\n\n**Common mistake:** using ALL for every job. This scans for 150+\nidentifiers including region-irrelevant ones (e.g., scanning for UK NINO\non US-only data). Use RECOMMENDED or select specific identifiers.\n\n### Step 4 — Custom data identifiers (regex patterns)\n\nCustom identifiers detect organization-specific data formats via regex.\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"employee-id-pattern\" \\\n  --regex \"EMP[0-9]{6}\" \\\n  --keywords \"employee\" \"emp_id\" \"staff\" \\\n  --ignore-words \"example\" \"test\" \"sample\" \\\n  --maximum-match-distance 50 \\\n  --severity-levels HIGH \\\n  --description \"Detects EMP###### employee ID format\"\n```\n\n**Key parameters:**\n- `--regex`: the PCRE-compatible regex pattern.\n- `--keywords`: proximity keywords — Macie only reports matches near\n  these keywords (reduces false positives).\n- `--ignore-words`: words to exclude from matches (test data, examples).\n- `--maximum-match-distance`: max character distance between the regex\n  match and a keyword for the finding to be reported.\n\n**Common mistake:** omitting `--keywords`. Without keywords, every\nregex match is reported, generating massive false positives. Always\nscope with proximity keywords.\n\n### Step 5 — Findings management\n\nMacie publishes findings to the Macie console and (optionally) Security\nHub and EventBridge.\n\n**List and filter findings:**\n\n```bash\n# All high-severity findings in the last 7 days\naws macie2 list-findings \\\n  --finding-criteria \\\n    criterion='{severity:{eq:[HIGH]},createdAt:{gte:\"2026-08-03T00:00:00Z\"}}' \\\n  --output json\n\n# Get finding details\naws macie2 get-findings --finding-ids \u003Cfinding-id-1> \u003Cfinding-id-2>\n```\n\n**Finding types:**\n- `policy:IAMUser\u002FS3\u002FBucketPublic` — publicly accessible bucket.\n- `policy:IAMUser\u002FS3\u002FBucketSharedExternally` — shared with external\n  account.\n- `sensitiveData:S3Object\u002F\u003CIdentifier>` — sensitive data detected.\n\n**Archiving findings (soft delete):**\n\n```bash\naws macie2 update-findings \\\n  --finding-ids \u003Cfinding-id> \\\n  --status ARCHIVED\n```\n\n### Step 6 — Finding suppression rules\n\nSuppression rules auto-archive findings matching criteria (reduces\nnoise from known false positives or accepted-risk patterns).\n\n```bash\naws macie2 put-findings-filter \\\n  --name \"suppress-test-bucket-findings\" \\\n  --action '{archived:true}' \\\n  --finding-criterion \\\n    criterion='{resource.tags.tagKey: {eq: [Environment]}, resource.tags.tagValue: {eq: [test]}}' \\\n  --description \"Auto-archive findings on test-environment buckets\"\n```\n\n**Common mistake:** overly broad suppression rules. Suppressing all\nfindings on a bucket prefix that also contains production data masks\nreal risks. Scope suppression rules tightly (specific tags, specific\nfinding types).\n\n### Step 7 — Automated ML-based discovery (latest feature)\n\nAutomated discovery uses ML to continuously scan all S3 buckets without\nrequiring manual classification jobs.\n\n```bash\n# Enable automated discovery\naws macie2 update-automated-discovery-configuration \\\n  --status ENABLED \\\n  --auto-enable-members true \\\n  --scope ONE_TO_ONE_MEMBERS\n```\n\n**Benefits:**\n- ML-based: adapts to bucket content without explicit identifier\n  selection.\n- Continuous: scans all new and modified objects automatically.\n- No job management: no need to create and schedule classification jobs.\n\n**Limitations:**\n- Still has scan frequency (not instant) — objects are queued.\n- Does NOT replace custom identifiers for organization-specific patterns.\n- Costs more than targeted classification jobs (scans all S3).\n\n**Common mistake:** enabling automated discovery and deleting all\nclassification jobs. Automated discovery and classification jobs serve\ndifferent purposes — keep targeted jobs for specific high-risk buckets.\n\n### Step 8 — Macie + Security Hub integration\n\nForward Macie findings to Security Hub for centralized security posture.\n\n```bash\n# Enable Security Hub integration\naws macie2 put-classification-export-configuration \\\n  --configuration '{securityHubConfiguration:{enableSecurityHubIntegration:true}}'\n\n# Verify\naws macie2 get-classification-export-configuration\n```\n\n**Behavior:**\n- Macie forwards findings to Security Hub as `AWS::Macie::Finding`\n  resources.\n- Security Hub deduplicates, correlates, and aggregates with other\n  security findings.\n- Finding severity maps to Security Hub severity (High, Medium, Low).\n\n**Common mistake:** not enabling Security Hub before Macie integration.\nMacie integration fails if Security Hub is not enabled in the account.\n\n### Step 9 — Macie + Lambda \u002F Step Functions auto-remediation\n\nWire Macie findings to EventBridge → Lambda or Step Functions for\nauto-remediation (e.g., quarantine public PII, restrict bucket ACL).\n\n**EventBridge rule (Macie findings → Lambda):**\n\n```bash\naws events put-rule \\\n  --name \"macie-finding-trigger\" \\\n  --event-pattern '{\n    \"source\": [\"aws.macie\"],\n    \"detail-type\": [\"Macie Finding\"],\n    \"detail\": {\n      \"severity\": [\"High\", \"Critical\"]\n    }\n  }'\n\n# Lambda target for remediation\naws events put-targets \\\n  --rule \"macie-finding-trigger\" \\\n  --targets '[{\"Id\":\"macie-remediation-lambda\",\"Arn\":\"arn:aws:lambda:us-east-1:123456789012:function:macie-remediate\"}]'\n```\n\n**Step Functions workflow (multi-step remediation):**\n\n```bash\naws stepfunctions create-state-machine \\\n  --name \"macie-remediation-workflow\" \\\n  --definition file:\u002F\u002Fremediation-workflow.json \\\n  --role-arn arn:aws:iam::123456789012:role\u002FMacieRemediationRole\n```\n\nThe Step Functions workflow can: (1) parse finding details, (2) check\nbucket exposure, (3) quarantine object (move to isolated bucket or\nencrypt), (4) restrict bucket ACL, (5) notify security team via SNS.\n\n**Common mistake:** not scoping the Lambda\u002FStep Functions remediation to\nspecific finding types. A blanket \"restrict all buckets on any finding\"\nrule can break production applications. Scope to specific finding types\n(e.g., `sensitiveData:S3Object\u002FCredit_Card` on public buckets only).\n\n### Step 10 — Cross-account findings aggregation\n\nFor org-level Macie deployments, aggregate findings from all member\naccounts into the delegated admin account.\n\n```bash\n# In the delegated admin account, list all member accounts\naws macie2 list-members \\\n  --query 'members[*].[accountId,relationshipStatus]' \\\n  --output text\n\n# Query findings across all member accounts\naws macie2 list-findings \\\n  --finding-criteria \\\n    criterion='{severity:{eq:[HIGH,CRITICAL]}}'\n```\n\n**Common mistake:** not verifying member account relationship status.\nAccounts in `Paused` or `Enabled` (but not `Invited`\u002F`Accepted`) do not\nforward findings. Verify `relationshipStatus=Enabled` for all members.\n\n## NEVER do these things (top 5)\n\n1. **NEVER create a classification job without verifying Macie is\n   enabled.** Classification jobs fail silently if Macie is disabled or\n   paused. Run `get-macie-session` first.\n\n2. **NEVER use `--managed-data-identifier-selector ALL` for every job.**\n   This scans for 150+ identifiers including region-irrelevant ones,\n   increasing cost and false positives. Use RECOMMENDED or select\n   specific identifiers.\n\n3. **NEVER create custom data identifiers without `--keywords`.** Without\n   proximity keywords, every regex match is reported — massive false\n   positives. Always scope with keywords and `--maximum-match-distance`.\n\n4. **NEVER enable auto-remediation Lambda without scoping by finding\n   type.** A blanket \"restrict all buckets on any finding\" rule breaks\n   production applications. Scope to specific finding types and\n   severities.\n\n5. **NEVER suppress findings without documenting the risk acceptance.**\n   Suppression rules auto-archive findings. An undocumented suppression\n   on a production bucket masks real risks. Document the suppression\n   rationale in the filter description.\n\n**Additional critical mistakes:** never enable Macie in the management\naccount for org-level (use delegated admin); never enable automated\ndiscovery and delete all classification jobs (keep targeted jobs for\nhigh-risk buckets); never forward findings to Security Hub without\nenabling Security Hub first; never create overly broad suppression rules\n(scope tightly by tags and finding types); never forget to configure\n`findingPublishingFrequency` (defaults to 15 min, critical findings may\ndelay).\n\n## Output format\n\n→ Literal output template moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md); the STRICT output contract above carries the authoritative template.\n\n### Worked example — create classification job (READY)\n\n```text\nOPERATION: classify\nVERDICT: READY\nTARGET: weekly-pii-scan\nPRE_CHECKS:\n  - [PASS] Macie session ENABLED (get-macie-session status=ENABLED)\n  - [PASS] Target bucket prod-data-bucket exists in account 123456789012\n  - [PASS] Managed identifier IDs valid (USA_SOCIAL_SECURITY_NUMBER etc.)\n  - [PASS] IAM role has macie2:CreateClassificationJob permission\nSTEPS:\n  1. CONFIRM: About to create a scheduled classification job weekly-pii-scan on bucket prod-data-bucket in account 123456789012 region us-east-1. This will scan for managed PII identifiers daily. Proceed? (yes\u002Fno)\n  2. aws macie2 create-classification-job --name weekly-pii-scan --job-type SCHEDULED --schedule-frequency '{dailySchedule:{}}' --s3-job-definition bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket]}]' --managed-data-identifier-selector RECOMMENDED --description \"Daily PII scan of production data bucket\"\nPOST_VERIFY: (pending execution)\nSTATE: pending — will be RUNNING after creation, COMPLETE after first scan\nNOTES: RECOMMENDED selector lets Macie sample bucket content and select relevant identifiers. Job runs daily. Findings published at FIFTEEN_MINUTES frequency. For organization-specific data formats, create custom data identifiers separately.\n```\n\n### Worked example — Macie not enabled (BLOCKED)\n\n→ Secondary worked example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: detection coverage gap analysis\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Recent AWS features (2024-2026)\n\n→ Recent AWS features deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — expert-heuristic deep dives, extended Mindset rationale, recent AWS features 2024-2026\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pre-flight command listing\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked example (BLOCKED) and the literal output-format template\n- [references\u002Fdetection-and-remediation.md](references\u002Fdetection-and-remediation.md) — deep identifier + remediation patterns (identifier categories, suppression, auto-remediation)\n- [references\u002Foperating-cli-commands.md](references\u002Foperating-cli-commands.md) — copy-pasteable CLI sequence for every operating step\n\n## Domain\n\nAWS CloudOps \u002F Amazon Macie Data Discovery & Sensitive Data Protection.\n\n## AWS documentation\n\n- **Amazon Macie User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fwhat-is-macie.html\n- **Macie managed data identifiers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fmanaged-data-identifiers.html\n- **Macie custom data identifiers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fcustom-data-identifiers.html\n- **Macie classification jobs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fclassification-jobs.html\n- **Macie findings** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Ffindings.html\n- **Macie + Security Hub** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fsecurityhub-integration.html\n- **Macie automated discovery** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fautomated-discovery.html\n- **Macie API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002FAPIReference\u002F\n","# Macie Data Discovery Operator\n\nAn AWS CloudOps agent skill that operates Amazon Macie data discovery\nlifecycle operations correctly and safely. Runs deterministic pre-checks\nbefore any state-changing CLI, emits the exact CLI behind a CONFIRM gate,\nand verifies state transitions after apply.\n\n## What this skill does\n\nExecutes Macie lifecycle operations: enabling Macie (standalone or\norg-level delegated admin), creating classification jobs (one-time or\nscheduled), configuring managed and custom data identifiers, managing\nfindings and suppression rules, enabling automated ML-based discovery,\nintegrating with Security Hub, and wiring Lambda\u002FStep Functions for\nauto-remediation. Every operation surfaces finding scope, detection\ncoverage, and remediation posture.\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 | classify | custom-id | findings | suppress | auto-discovery | security-hub | remediate | aggregate>\nVERDICT: READY | BLOCKED | COMPLETED\nTARGET: \u003Cmacie-resource-name>\nPRE_CHECKS:\n  - [PASS] \u003Ccheck description>\n  - [FAIL] \u003Ccheck description> — \u003Creason>\nSTEPS:\n  1. CONFIRM: About to \u003Coperation> on \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: \u003Cjob status \u002F finding state \u002F Macie status after apply>\nNOTES: \u003Cdetection coverage rationale, finding severity, remediation caveats>\n```\n\n### FORBIDDEN output patterns\n\n- NEVER start with conversational preamble (\"Let me analyze…\") — the\n  VERDICT block is the FIRST line, always. Use uppercase verdict values\n  only (`READY`, `BLOCKED`, `COMPLETED`).\n- NEVER omit PRE_CHECKS — every pre-check must appear with `[PASS]` or\n  `[FAIL]` and a specific reason for each failure.\n- NEVER emit a CLI command with placeholder flags in a READY plan —\n  every flag must be populated with actual values from the input data.\n- NEVER claim COMPLETED without every POST_VERIFY line showing `[PASS]`,\n  and never omit the CONFIRM gate as the first STEPS entry for\n  state-changing operations.\n- NEVER classify as READY if Macie is not enabled in the target account\n  or region — Macie operations fail silently without enablement.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| §\"Mindset\" | Understanding the Macie detection model |\n| §\"Pre-flight\" | Macie enablement + delegated admin gate |\n| §\"Step 1 — Enable Macie\" | Org-level delegated admin setup |\n| §\"Step 2 — Classification jobs\" | One-time vs scheduled S3 scanning |\n| §\"Step 3 — Managed data identifiers\" | PII \u002F financial \u002F credential types |\n| §\"Step 4 — Custom data identifiers\" | Regex-based detection |\n| §\"Step 5 — Findings management\" | Policy and sensitive-data findings |\n| §\"Step 6 — Suppression rules\" | False-positive filtering |\n| §\"Step 7 — Automated discovery\" | ML-based continuous scanning |\n| §\"Step 8 — Security Hub integration\" | Findings forwarding |\n| §\"Step 9 — Auto-remediation\" | Lambda + Step Functions |\n| §\"NEVER do these things\" | Review before risky operations |\n| §\"Output format\" | Structured output template |\n| references\u002Fdetection-and-remediation.md | Deep identifier + remediation patterns |\n| references\u002Foperating-cli-commands.md | Copy-pasteable CLI sequence |\n\n## Mindset\n\nThree Macie realities drive every operation:\n\n→ Extended Mindset rationale moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Pre-flight: Macie enablement + delegated admin gate\n\nRun before any operation. `get-macie-session` returns the Macie\nenablement status. `get-administrator-account` returns the delegated\nadmin (org-level).\n\n→ Live-account pre-flight command listing moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n| Attribute | Effect on operation |\n|---|---|\n| Macie `status: PAUSED` | Classification jobs do not run. Findings not published. Re-enable via `enable-macie-session`. |\n| Delegated admin not set | Org-level operations (cross-account) fail. Must delegate admin first. |\n| No existing classification job | New job creation is safe. |\n| Bucket not in Macie account | `s3:Bucket*` permissions needed for Macie service role. |\n| `findingPublishingFrequency` unset | Defaults to 15 min. Critical findings may delay. |\n\n**Malformed input:** emit `VERDICT: ERROR` with reason and remediation.\n\n## Expert heuristic: finding severity and detection coverage\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## 10-step operating procedure\n\n### Step 1 — Enable Macie (standalone or org-level delegated admin)\n\nMacie must be enabled before any other operation.\n\n**Standalone (single account):**\n\n```bash\naws macie2 enable-macie-session \\\n  --finding-publishing-frequency FIFTEEN_MINUTES \\\n  --status ENABLED\n```\n\n**Org-level delegated admin:**\n\n```bash\n# 1. Designate the admin account (run in management account)\naws macie2 enable-organization-admin-account \\\n  --admin-account-id 123456789012\n\n# 2. In the delegated admin account, enable Macie for the org\naws macie2 enable-macie-session \\\n  --finding-publishing-frequency FIFTEEN_MINUTES \\\n  --status ENABLED\n\n# 3. Configure auto-enable for new member accounts\naws macie2 update-organization-configuration \\\n  --auto-enable true\n```\n\n**Common mistake:** enabling Macie in the management account instead of\ndelegating to a dedicated security admin account. Org-level Macie\nshould use a designated admin account that manages all member accounts.\n\n### Step 2 — Classification jobs (one-time vs scheduled)\n\nClassification jobs scan S3 buckets for sensitive data.\n\n**One-time job:**\n\n```bash\naws macie2 create-classification-job \\\n  --name \"pii-scan-2026-08\" \\\n  --job-type ONE_TIME \\\n  --s3-job-definition \\\n    bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket,financial-records]}]' \\\n  --managed-data-identifier-selector-ids \\\n    USA_SOCIAL_SECURITY_NUMBER USA_PASSPORT_NUMBER CREDIT_CARD_NUMBER \\\n    EMAIL_ADDRESS PHONE_NUMBER \\\n  --description \"One-time PII scan of production data buckets\"\n```\n\n**Scheduled job (CRON):**\n\n```bash\naws macie2 create-classification-job \\\n  --name \"weekly-pii-scan\" \\\n  --job-type SCHEDULED \\\n  --schedule-frequency '{dailySchedule:{}}' \\\n  --s3-job-definition \\\n    bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket]}]' \\\n  --managed-data-identifier-selector ALL \\\n  --description \"Weekly scheduled PII scan\"\n```\n\n**Schedule options:**\n- `{dailySchedule:{}}` — runs daily.\n- `{weeklySchedule:{dayOfWeek=WEDNESDAY}}` — runs weekly.\n- `{monthlySchedule:{dayOfMonth=15}}` — runs monthly.\n\n**Common mistake:** not scoping the S3 bucket list. A job scanning ALL\nbuckets is expensive and noisy. Scope to specific buckets or use bucket\ncriteria (tags, prefixes) for targeted scanning.\n\n### Step 3 — Managed data identifiers (PII, financial, credentials)\n\nMacie provides ~150+ managed data identifiers. Select relevant\nidentifiers per region and data type.\n\n**Categories:**\n- **PII:** SSN, passport, driver's license, national ID (region-specific).\n- **Financial:** credit card numbers, bank account, SWIFT codes.\n- **Credentials:** AWS access keys, private keys, API tokens.\n- **Personal:** email, phone, address, name, date of birth.\n\n**Selection strategies:**\n\n```bash\n# Option A: ALL managed identifiers (comprehensive, expensive)\n--managed-data-identifier-selector ALL\n\n# Option B: Specific identifiers (targeted, cost-efficient)\n--managed-data-identifier-selector-ids \\\n  USA_SOCIAL_SECURITY_NUMBER USA_PASSPORT_NUMBER CREDIT_CARD_NUMBER\n\n# Option C: RECOMMENDED (Macie selects based on bucket content sampling)\n--managed-data-identifier-selector RECOMMENDED\n```\n\n**Common mistake:** using ALL for every job. This scans for 150+\nidentifiers including region-irrelevant ones (e.g., scanning for UK NINO\non US-only data). Use RECOMMENDED or select specific identifiers.\n\n### Step 4 — Custom data identifiers (regex patterns)\n\nCustom identifiers detect organization-specific data formats via regex.\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"employee-id-pattern\" \\\n  --regex \"EMP[0-9]{6}\" \\\n  --keywords \"employee\" \"emp_id\" \"staff\" \\\n  --ignore-words \"example\" \"test\" \"sample\" \\\n  --maximum-match-distance 50 \\\n  --severity-levels HIGH \\\n  --description \"Detects EMP###### employee ID format\"\n```\n\n**Key parameters:**\n- `--regex`: the PCRE-compatible regex pattern.\n- `--keywords`: proximity keywords — Macie only reports matches near\n  these keywords (reduces false positives).\n- `--ignore-words`: words to exclude from matches (test data, examples).\n- `--maximum-match-distance`: max character distance between the regex\n  match and a keyword for the finding to be reported.\n\n**Common mistake:** omitting `--keywords`. Without keywords, every\nregex match is reported, generating massive false positives. Always\nscope with proximity keywords.\n\n### Step 5 — Findings management\n\nMacie publishes findings to the Macie console and (optionally) Security\nHub and EventBridge.\n\n**List and filter findings:**\n\n```bash\n# All high-severity findings in the last 7 days\naws macie2 list-findings \\\n  --finding-criteria \\\n    criterion='{severity:{eq:[HIGH]},createdAt:{gte:\"2026-08-03T00:00:00Z\"}}' \\\n  --output json\n\n# Get finding details\naws macie2 get-findings --finding-ids \u003Cfinding-id-1> \u003Cfinding-id-2>\n```\n\n**Finding types:**\n- `policy:IAMUser\u002FS3\u002FBucketPublic` — publicly accessible bucket.\n- `policy:IAMUser\u002FS3\u002FBucketSharedExternally` — shared with external\n  account.\n- `sensitiveData:S3Object\u002F\u003CIdentifier>` — sensitive data detected.\n\n**Archiving findings (soft delete):**\n\n```bash\naws macie2 update-findings \\\n  --finding-ids \u003Cfinding-id> \\\n  --status ARCHIVED\n```\n\n### Step 6 — Finding suppression rules\n\nSuppression rules auto-archive findings matching criteria (reduces\nnoise from known false positives or accepted-risk patterns).\n\n```bash\naws macie2 put-findings-filter \\\n  --name \"suppress-test-bucket-findings\" \\\n  --action '{archived:true}' \\\n  --finding-criterion \\\n    criterion='{resource.tags.tagKey: {eq: [Environment]}, resource.tags.tagValue: {eq: [test]}}' \\\n  --description \"Auto-archive findings on test-environment buckets\"\n```\n\n**Common mistake:** overly broad suppression rules. Suppressing all\nfindings on a bucket prefix that also contains production data masks\nreal risks. Scope suppression rules tightly (specific tags, specific\nfinding types).\n\n### Step 7 — Automated ML-based discovery (latest feature)\n\nAutomated discovery uses ML to continuously scan all S3 buckets without\nrequiring manual classification jobs.\n\n```bash\n# Enable automated discovery\naws macie2 update-automated-discovery-configuration \\\n  --status ENABLED \\\n  --auto-enable-members true \\\n  --scope ONE_TO_ONE_MEMBERS\n```\n\n**Benefits:**\n- ML-based: adapts to bucket content without explicit identifier\n  selection.\n- Continuous: scans all new and modified objects automatically.\n- No job management: no need to create and schedule classification jobs.\n\n**Limitations:**\n- Still has scan frequency (not instant) — objects are queued.\n- Does NOT replace custom identifiers for organization-specific patterns.\n- Costs more than targeted classification jobs (scans all S3).\n\n**Common mistake:** enabling automated discovery and deleting all\nclassification jobs. Automated discovery and classification jobs serve\ndifferent purposes — keep targeted jobs for specific high-risk buckets.\n\n### Step 8 — Macie + Security Hub integration\n\nForward Macie findings to Security Hub for centralized security posture.\n\n```bash\n# Enable Security Hub integration\naws macie2 put-classification-export-configuration \\\n  --configuration '{securityHubConfiguration:{enableSecurityHubIntegration:true}}'\n\n# Verify\naws macie2 get-classification-export-configuration\n```\n\n**Behavior:**\n- Macie forwards findings to Security Hub as `AWS::Macie::Finding`\n  resources.\n- Security Hub deduplicates, correlates, and aggregates with other\n  security findings.\n- Finding severity maps to Security Hub severity (High, Medium, Low).\n\n**Common mistake:** not enabling Security Hub before Macie integration.\nMacie integration fails if Security Hub is not enabled in the account.\n\n### Step 9 — Macie + Lambda \u002F Step Functions auto-remediation\n\nWire Macie findings to EventBridge → Lambda or Step Functions for\nauto-remediation (e.g., quarantine public PII, restrict bucket ACL).\n\n**EventBridge rule (Macie findings → Lambda):**\n\n```bash\naws events put-rule \\\n  --name \"macie-finding-trigger\" \\\n  --event-pattern '{\n    \"source\": [\"aws.macie\"],\n    \"detail-type\": [\"Macie Finding\"],\n    \"detail\": {\n      \"severity\": [\"High\", \"Critical\"]\n    }\n  }'\n\n# Lambda target for remediation\naws events put-targets \\\n  --rule \"macie-finding-trigger\" \\\n  --targets '[{\"Id\":\"macie-remediation-lambda\",\"Arn\":\"arn:aws:lambda:us-east-1:123456789012:function:macie-remediate\"}]'\n```\n\n**Step Functions workflow (multi-step remediation):**\n\n```bash\naws stepfunctions create-state-machine \\\n  --name \"macie-remediation-workflow\" \\\n  --definition file:\u002F\u002Fremediation-workflow.json \\\n  --role-arn arn:aws:iam::123456789012:role\u002FMacieRemediationRole\n```\n\nThe Step Functions workflow can: (1) parse finding details, (2) check\nbucket exposure, (3) quarantine object (move to isolated bucket or\nencrypt), (4) restrict bucket ACL, (5) notify security team via SNS.\n\n**Common mistake:** not scoping the Lambda\u002FStep Functions remediation to\nspecific finding types. A blanket \"restrict all buckets on any finding\"\nrule can break production applications. Scope to specific finding types\n(e.g., `sensitiveData:S3Object\u002FCredit_Card` on public buckets only).\n\n### Step 10 — Cross-account findings aggregation\n\nFor org-level Macie deployments, aggregate findings from all member\naccounts into the delegated admin account.\n\n```bash\n# In the delegated admin account, list all member accounts\naws macie2 list-members \\\n  --query 'members[*].[accountId,relationshipStatus]' \\\n  --output text\n\n# Query findings across all member accounts\naws macie2 list-findings \\\n  --finding-criteria \\\n    criterion='{severity:{eq:[HIGH,CRITICAL]}}'\n```\n\n**Common mistake:** not verifying member account relationship status.\nAccounts in `Paused` or `Enabled` (but not `Invited`\u002F`Accepted`) do not\nforward findings. Verify `relationshipStatus=Enabled` for all members.\n\n## NEVER do these things (top 5)\n\n1. **NEVER create a classification job without verifying Macie is\n   enabled.** Classification jobs fail silently if Macie is disabled or\n   paused. Run `get-macie-session` first.\n\n2. **NEVER use `--managed-data-identifier-selector ALL` for every job.**\n   This scans for 150+ identifiers including region-irrelevant ones,\n   increasing cost and false positives. Use RECOMMENDED or select\n   specific identifiers.\n\n3. **NEVER create custom data identifiers without `--keywords`.** Without\n   proximity keywords, every regex match is reported — massive false\n   positives. Always scope with keywords and `--maximum-match-distance`.\n\n4. **NEVER enable auto-remediation Lambda without scoping by finding\n   type.** A blanket \"restrict all buckets on any finding\" rule breaks\n   production applications. Scope to specific finding types and\n   severities.\n\n5. **NEVER suppress findings without documenting the risk acceptance.**\n   Suppression rules auto-archive findings. An undocumented suppression\n   on a production bucket masks real risks. Document the suppression\n   rationale in the filter description.\n\n**Additional critical mistakes:** never enable Macie in the management\naccount for org-level (use delegated admin); never enable automated\ndiscovery and delete all classification jobs (keep targeted jobs for\nhigh-risk buckets); never forward findings to Security Hub without\nenabling Security Hub first; never create overly broad suppression rules\n(scope tightly by tags and finding types); never forget to configure\n`findingPublishingFrequency` (defaults to 15 min, critical findings may\ndelay).\n\n## Output format\n\n→ Literal output template moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md); the STRICT output contract above carries the authoritative template.\n\n### Worked example — create classification job (READY)\n\n```text\nOPERATION: classify\nVERDICT: READY\nTARGET: weekly-pii-scan\nPRE_CHECKS:\n  - [PASS] Macie session ENABLED (get-macie-session status=ENABLED)\n  - [PASS] Target bucket prod-data-bucket exists in account 123456789012\n  - [PASS] Managed identifier IDs valid (USA_SOCIAL_SECURITY_NUMBER etc.)\n  - [PASS] IAM role has macie2:CreateClassificationJob permission\nSTEPS:\n  1. CONFIRM: About to create a scheduled classification job weekly-pii-scan on bucket prod-data-bucket in account 123456789012 region us-east-1. This will scan for managed PII identifiers daily. Proceed? (yes\u002Fno)\n  2. aws macie2 create-classification-job --name weekly-pii-scan --job-type SCHEDULED --schedule-frequency '{dailySchedule:{}}' --s3-job-definition bucketDefinitions='[{accountId=123456789012,buckets=[prod-data-bucket]}]' --managed-data-identifier-selector RECOMMENDED --description \"Daily PII scan of production data bucket\"\nPOST_VERIFY: (pending execution)\nSTATE: pending — will be RUNNING after creation, COMPLETE after first scan\nNOTES: RECOMMENDED selector lets Macie sample bucket content and select relevant identifiers. Job runs daily. Findings published at FIFTEEN_MINUTES frequency. For organization-specific data formats, create custom data identifiers separately.\n```\n\n### Worked example — Macie not enabled (BLOCKED)\n\n→ Secondary worked example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: detection coverage gap analysis\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Recent AWS features (2024-2026)\n\n→ Recent AWS features deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — expert-heuristic deep dives, extended Mindset rationale, recent AWS features 2024-2026\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — live-account pre-flight command listing\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked example (BLOCKED) and the literal output-format template\n- [references\u002Fdetection-and-remediation.md](references\u002Fdetection-and-remediation.md) — deep identifier + remediation patterns (identifier categories, suppression, auto-remediation)\n- [references\u002Foperating-cli-commands.md](references\u002Foperating-cli-commands.md) — copy-pasteable CLI sequence for every operating step\n\n## Domain\n\nAWS CloudOps \u002F Amazon Macie Data Discovery & Sensitive Data Protection.\n\n## AWS documentation\n\n- **Amazon Macie User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fwhat-is-macie.html\n- **Macie managed data identifiers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fmanaged-data-identifiers.html\n- **Macie custom data identifiers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fcustom-data-identifiers.html\n- **Macie classification jobs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fclassification-jobs.html\n- **Macie findings** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Ffindings.html\n- **Macie + Security Hub** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fsecurityhub-integration.html\n- **Macie automated discovery** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002Fuser\u002Fautomated-discovery.html\n- **Macie API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002Flatest\u002FAPIReference\u002F\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, macie, security, cloudops, operate, data-discovery, pii-detection, classification, remediation, security-hub, sensitive-data","4","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.1.0","aws, macie, data discovery, cloudops, operate, classification, pii, managed data identifiers, custom data identifiers, regex, findings, suppression rules, automated discovery, security hub, lambda remediation, step functions, delegated admin, s3 scanning, sensitive data, data loss prevention","operate","high","false","capability","Invoke when the user wants to enable Macie (standalone or org-level delegated admin), create or manage classification jobs (one-time or scheduled), configure managed data identifiers, create custom regex-based data identifiers, manage findings (policy or sensitive-data types), configure suppression rules, enable automated ML-based discovery, forward findings to Security Hub, wire Lambda or Step Functions for auto-remediation of exposed PII, or aggregate cross-account Macie findings. Do NOT invoke for Amazon GuardDuty threat detection, AWS Config rule evaluation, or Security Hub control management (use guardduty-finding-triage or securityhub-finding-triage).","aws-orchestrator","true","READY | BLOCKED | COMPLETED","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live operations: AWS CLI v2 with macie2, s3, iam, sts, securityhub, lambda, and stepfunctions access. Works with Terraform aws_macie2_account \u002F aws_macie2_classification_job \u002F aws_macie2_custom_data_identifier resources and CloudFormation AWS::Macie::* templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fmacie-data-discovery-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 macie-data-discovery-operator",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill macie-data-discovery-operator",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill macie-data-discovery-operator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5641,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fautomated-remediation-step-functions.md",726,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fbaselines\u002Fautomated-remediation-step-functions.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fcreate-classification-job-scheduled.md",714,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fbaselines\u002Fcreate-classification-job-scheduled.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fcustom-data-identifier-regex.md",606,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fbaselines\u002Fcustom-data-identifier-regex.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fenable-macie-org-delegated-admin.md",608,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fbaselines\u002Fenable-macie-org-delegated-admin.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fmacie-not-enabled-blocked.md",715,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fbaselines\u002Fmacie-not-enabled-blocked.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1614,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",12224,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fautomated-remediation-step-functions.md",695,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fprompts\u002Fautomated-remediation-step-functions.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fcreate-classification-job-scheduled.md",593,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fprompts\u002Fcreate-classification-job-scheduled.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fcustom-data-identifier-regex.md",568,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fprompts\u002Fcustom-data-identifier-regex.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fenable-macie-org-delegated-admin.md",603,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fprompts\u002Fenable-macie-org-delegated-admin.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fmacie-not-enabled-blocked.md",428,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fevals\u002Fprompts\u002Fmacie-not-enabled-blocked.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",5806,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",5308,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fdetection-and-remediation.md",9974,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Freferences\u002Fdetection-and-remediation.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fdiagnostic-commands.md",874,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Freferences\u002Fdiagnostic-commands.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Foperating-cli-commands.md",5749,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Freferences\u002Foperating-cli-commands.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",1364,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4563,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmacie-data-discovery-operator\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]