Policy 360

All Amazon internal data being stored in Andes Data lake must be protected comprehensively, so customer private data is not inadvertently shared without proper permissions. 

Key Ideas & Challenges

Understanding and compliant with data protection policies
Tagging data properly
Protect privacy data


Dataset owners need to clearly understand their dataset and manage privacy related policies and its services.

Problem statement

#Who - Database owners and DataCentral users
#What - Have trouble tagging according to policies
#When - When they are creating tables 
#Why - Because tagging requires deep knowledge of data contained per table and takes too long, so they make the table public without realizing they violated Amazon data protection policies.

Hypothesis

#If - We create policy 360 in DataCentral to guide users with data protection policies
#Then - Users will be 100% compliant with data protection policies 
#Because - We enabled users to create table, tag data with proper policies with ease.

Use cases

#Create table
 
- A dataset owner creates a new table (version) in Andes data lake

#Privacy related questionaire
- A dataset owner answers privacy related questionaire to determine what part of the table needs to be called out to be tagged

#Data categorization
- A dataset owner tags the table according to data protection policies and activate the table for public consumption

© Copyright 2026 CucumberMint - All Rights Reserved

Free AI Website Creator