---
title: "AWS Macie"
slug: "aws-macie"
updated: 2026-10-26T14:40:03Z
published: 2026-10-26T14:40:03Z
canonical: "docs.databee.buzz/aws-macie"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS Macie

Amazon Macie is a fully managed data security and data privacy service. Macie uses machine learning and pattern matching to help you discover, monitor, and protect your sensitive data in Amazon S3. For more information on AWS Macie, click [here](https://docs.aws.amazon.com/macie/latest/user/what-is-macie.html).

**Integration Method:** API

**Tables**: Detection Finding (2004)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Findings | Get the finding details from different services. |
| Data Sources | Get details of the data sources. |

This integration supports the following versions.

| AWS Macie API version | 2020-05-13 |
| --- | --- |

> [!NOTE]
> **Note:**
> 
> AWS Macie is a continuously updated SaaS service. As of this document preparation, the latest update to the sensitive data discovery was on March 03, 2025.

## Prerequisites

- To Configure AWS Macie, refer [here](https://docs.aws.amazon.com/macie/latest/user/getting-started.html).
- Refer to this [common procedure](https://docs.databee.buzz/docs/prerequisites-aws-configuration) on how to create an IAM user, configure the AWS Access Key and AWS Secret Key, attach an IAM policy with required permissions.
- The user should have access to the DataBee console.

> **Test Connection**
> 
> The AWS Macie integration supports the **Test Connection** button in the DataBee feed configuration. Use this to validate that DataBee can successfully reach the AWS Macie API with the credentials you have provided before saving the feed configuration.

## Configuration Overview

1. Generate an AWS Access Key & Secret Key with the required IAM policies.
2. Add the [AWS Macie](/user-manual/docs/aws-macie#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameter** | **AWS Macie Parameter** |
| --- | --- |
| Access Key | AWS Access Key |
| Secret Key | AWS Secret Key |
| AWS Region | AWS Region |
| Service Name | macie2 |

## AWS Macie Configuration

1. Start by creating an IAM user with the API credentials. This common step is documented at [AWS Configuration Prerequisites](https://docs.databee.buzz/docs/prerequisites-aws-configuration).
2. Once the IAM user has been created, Refer this document [GuardDuty Setup](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_settingup.html) for further steps.
3. Ensure AWS Access Key is attached to an IAM policy with following Actions allowed on the Macie resource. Refer [here](https://docs.aws.amazon.com/guardduty/latest/ug/security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonGuardDutyReadOnlyAccess) more info on the policy.

### Minimum Required IAM Policy

```plaintext
{
    "Version": "2012-10-17",
    "Statement":
    [
        {
            "Effect": "Allow",
            "Action":
            [
                "macie2:Describe*",
                "macie2:Get*",
                "macie2:List*",
                "macie2:BatchGetCustomDataIdentifiers",
                "macie2:SearchResources"
            ],
            "Resource": "*"
        }
    ]
}
```

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-macie-apr2025-image-yzeg6s3i.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A19%3A30Z&se=2026-10-30T13%3A19%3A30Z&sr=c&sp=r&sig=7YZc7bS3UiLxj2L2iKjdqal8xgkxEv6BgCA65TJdi5M%3D)
2. Search for the **AWS Macie** and click it as shown below. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-macie-apr2025-image-a2wj2m8p.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A19%3A30Z&se=2026-10-30T13%3A19%3A30Z&sr=c&sp=r&sig=7YZc7bS3UiLxj2L2iKjdqal8xgkxEv6BgCA65TJdi5M%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-macie-apr2025-image-l00x8rep.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A19%3A30Z&se=2026-10-30T13%3A19%3A30Z&sr=c&sp=r&sig=7YZc7bS3UiLxj2L2iKjdqal8xgkxEv6BgCA65TJdi5M%3D)
4. Enter feed contact information and click **Next**. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-macie-apr2025-image-w3lh1hq8.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A19%3A30Z&se=2026-10-30T13%3A19%3A30Z&sr=c&sp=r&sig=7YZc7bS3UiLxj2L2iKjdqal8xgkxEv6BgCA65TJdi5M%3D)
5. In the configuration page, confirm the following:
6. API Base URL: this is the base URL that DataBee will interact with. Replace with appropriate AWS region.
7. Authorization Method: AWS Signature.
8. Access Key: paste the AWS Client Access Key.
9. Secret Key: paste the AWS Client Secret Key.
10. AWS Region: type the AWS region . Refer [endpoints](https://docs.aws.amazon.com/general/latest/gr/macie.html) for regions.
11. Session Token: can be left empty.
12. Service Name: macie2
13. Event Types: preselected for all the event types that integration pulls.

![A screenshot of a login form AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-macie-apr2025-image-vq7ct0hi.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A19%3A30Z&se=2026-10-30T13%3A19%3A30Z&sr=c&sp=r&sig=7YZc7bS3UiLxj2L2iKjdqal8xgkxEv6BgCA65TJdi5M%3D) 6. Click **Submit**.

## Troubleshooting Tips

- Ensure the Access Key, Secret Key, Region are pasted correctly. Since you cannot view the Secret Key after the 1st time, re-create the AWS Access Key & AWS Secret Key, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
- Ensure the AWS Macie scopes/permissions are correctly attached to the AWS Access Key.