AWS wellarchitected documentation change
Summary
Updated blog post title from 'QuickSight' to 'Quick Suite' in data protection context
Security assessment
Service name change in reference material. No modification to data classification or protection mechanisms described.
Diff
diff --git a/wellarchitected/latest/analytics-lens/best-practice-3.3---understand-data-classifications-and-their-protection-policies..md b/wellarchitected/latest/analytics-lens/best-practice-3.3---understand-data-classifications-and-their-protection-policies..md index 02a6878c4..324888842 100644 --- a//wellarchitected/latest/analytics-lens/best-practice-3.3---understand-data-classifications-and-their-protection-policies..md +++ b//wellarchitected/latest/analytics-lens/best-practice-3.3---understand-data-classifications-and-their-protection-policies..md @@ -27 +27 @@ For more details, refer to the following information: - * AWS Big Data Blog: [Enforce column-level authorization with QuickSight and AWS Lake](https://aws.amazon.com/blogs/big-data/enforce-column-level-authorization-with-amazon-quicksight-and-aws-lake-formation/) [Formation](https://aws.amazon.com/blogs/big-data/enforce-column-level-authorization-with-amazon-quicksight-and-aws-lake-formation/). + * AWS Big Data Blog: [Enforce column-level authorization with Quick Suite and AWS Lake](https://aws.amazon.com/blogs/big-data/enforce-column-level-authorization-with-amazon-quicksight-and-aws-lake-formation/) [Formation](https://aws.amazon.com/blogs/big-data/enforce-column-level-authorization-with-amazon-quicksight-and-aws-lake-formation/).