AWS lake-formation medium security documentation change
Summary
Added documentation about Amazon Redshift federated catalog access monitoring and updated section casing
Security assessment
New content explains how to monitor security-sensitive data access patterns for Redshift federated tables, addressing potential gaps in audit logging documentation
Diff
diff --git a/lake-formation/latest/dg/logging-using-cloudtrail.md b/lake-formation/latest/dg/logging-using-cloudtrail.md index 12a891c85..ca8708c38 100644 --- a//lake-formation/latest/dg/logging-using-cloudtrail.md +++ b//lake-formation/latest/dg/logging-using-cloudtrail.md @@ -5 +5 @@ -Lake Formation Information in CloudTrailUnderstanding Lake Formation Events +Lake Formation information in CloudTrailUnderstanding Lake Formation events @@ -7 +7 @@ Lake Formation Information in CloudTrailUnderstanding Lake Formation Events -# Logging AWS Lake Formation API Calls Using AWS CloudTrail +# Logging AWS Lake Formation API calls using AWS CloudTrail @@ -13 +13 @@ To learn more about CloudTrail, see the [_AWS CloudTrail User Guide_](https://do -## Lake Formation Information in CloudTrail +## Lake Formation information in CloudTrail @@ -45 +45 @@ For more information, see the following: -## Understanding Lake Formation Events +## Understanding Lake Formation events @@ -111,0 +112,4 @@ The next example shows a CloudTrail log entry for the `GetDataAccess` action. Pr +###### Amazon Redshift federated catalog access monitoring + +Amazon Redshift federated catalogs in the AWS Glue Data Catalog do not generate `GetDataAccess` events in Lake Formation CloudTrail logs. To track data access for Amazon Redshift tables in the Data Catalog, monitor `GetTable` and `BatchGetTable` events, which capture metadata access patterns for Redshift federated tables, including table name, database name, and catalog ID information +