AWS wellarchitected documentation change
Summary
Updated blog post title to use 'QuickSight' instead of 'Amazon QuickSight'
Security assessment
Branding change in reference documentation link. No security content modification or new security features added.
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 8e7dd8a8a..02a6878c4 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 Amazon 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 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/).