implementing-aws-macie-for-data-classification

Configure Amazon Macie to discover and classify sensitive data in S3 buckets.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill implementing-aws-macie-for-data-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-aws-macie-for-data-classification
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/cloud-security/implementing-aws-macie-for-data-classification
Command: npx skills add https://github.com/xalgord/xalgorix --skill implementing-aws-macie-for-data-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations storing data in Amazon S3 often lack visibility into where PII, financial records, and credentials actually reside, making compliance and breach prevention difficult. This Skill guides the deployment of Amazon Macie to automatically discover, classify, and report sensitive data across S3 buckets.

Core Features & Use Cases

  • Automated Sensitive Data Discovery: Enable Macie and its automated discovery configuration via AWS CLI or Terraform, with verification commands to confirm scanning is actually running.
  • Classification Jobs & Custom Identifiers: Create one-time or scheduled classification jobs with scoping rules, plus custom regex-based data identifiers and allow lists to reduce false positives.
  • Findings Management & Response: Query and export findings, integrate with Security Hub and EventBridge, and trigger Lambda-based automated remediation such as tagging and SNS alerting.
  • Use Case: A security engineer needs to prove GDPR compliance for customer data in S3. Use this Skill to enable Macie across an AWS Organization, run scheduled scans on production buckets, and route high-severity findings to the security team automatically.

Quick Start

Enable Amazon Macie in my AWS account, turn on automated sensitive data discovery, and create a scheduled classification job for my production S3 buckets.

Frequently Asked Questions about implementing-aws-macie-for-data-classification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable Amazon Macie for S3 data classification?

Enable Macie with the AWS CLI command aws macie2 enable-macie, then activate scanning with update-automated-discovery-configuration --status ENABLED. Verify both steps using get-macie-session and get-automated-discovery-configuration, since enabling Macie alone does not start scanning.

How to create a custom data identifier in Amazon Macie?

Use aws macie2 create-custom-data-identifier with a regex pattern, description, and severity thresholds based on occurrence counts. You can also add keywords and a maximum match distance to improve detection accuracy for formats like internal employee IDs or project codes.

Why is Macie not scanning objects in my S3 bucket?

Objects encrypted with a customer-managed KMS key are skipped unless the Macie service-linked role has kms:Decrypt permission, appearing under unclassifiableObjectCount. Also check that job scoping terms for OBJECT_KEY or OBJECT_EXTENSION actually match your data prefixes.

Does Amazon Macie support multi-account AWS Organizations deployment?

Yes, designate an administrator account with enable-organization-admin-account from the management account, then add members with create-member. New organization accounts are not auto-covered, so configure auto-enable and verify member status with list-members.

How long are Macie findings retained and how do I export them?

Sensitive data findings expire after 90 days unless you configure an S3 export destination with a KMS key. Confirm the export is active with get-classification-export-configuration, and note that Security Hub integration requires both services enabled in the same region.