Technical requirementsThe many different aspects of data governanceData security, access, and privacyCommon data regulatory requirementsCore data protection conceptsPersonally identifiable information (PII)Personal dataEncryptionAnonymized dataPseudonymized data/tokenizationAuthenticationAuthorizationPutting these concepts togetherData quality, data profiling, and data lineageData qualityData profilingData lineageBusiness and technical data catalogsImplementing a data catalog to avoid creating a data swampBusiness data catalogsTechnical data catalogsAWS services that help with data governanceThe AWS Glue/Lake Formation technical data catalogAWS Glue DataBrew for profiling datasetsAWS Glue Data QualityAWS Key Management Service (KMS) for data encryptionAmazon Macie for detecting PII data in Amazon S3 objectsThe AWS Glue Studio Detect PII transform for detecting PII data in datasetsAmazon GuardDuty for detecting threats in an AWS accountAWS Identity and Access Management (IAM) serviceUsing AWS Lake Formation to manage data lake accessPermissions management before Lake FormationPermissions management using AWS Lake FormationHands-on – configuring Lake Formation permissionsCreating a new user with IAM permissionsTransitioning to managing fine-grained permissions with AWS Lake FormationActivating Lake Formation permissions for a database and tableGranting Lake Formation permissionsSummary