Skip to main content

AWS Solutions Library

Guidance for Sensitive Information Scanning with Amazon Macie on AWS

Go to sample code

Overview

This Guidance demonstrates how organizations can leverage Amazon Macie to enhance their data security posture by systematically scanning artifacts for sensitive information. It shows a flexible, prescriptive architecture that can be seamlessly integrated into existing applications or deployed as a standalone microservice. The guidance helps businesses protect valuable data assets by identifying and securing PII, financial information, and credentials. By showcasing the interaction between Macie and other AWS services, this architecture empowers companies to implement robust data discovery and protection measures, ultimately reducing the risk of data breaches and ensuring compliance with data privacy regulations.

Benefits

Deploy automated scanning that streamlines sensitive information discovery with instant alerts. Reduce compliance overhead through continuous monitoring and detailed audit trails.

Focus on core business value with a ready-to-implement scanning architecture. Eliminate infrastructure management while maintaining enterprise-grade security controls.

Reduce operational complexity through centralized monitoring and automated response workflows. Free up security teams to focus on high-value activities rather than infrastructure management.

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Deploy with confidence

Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs. 

Go to sample code

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.