AWS wellarchitected documentation change
Summary
Updated product name from 'Quick Suite' to 'Quick' in data authorization reference
Security assessment
Change only updates the product name in a blog reference. No security implications as column-level authorization concepts remain identical. Data classification and protection policies are not modified.
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 324888842..7272206a2 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 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/). + * AWS Big Data Blog: [Enforce column-level authorization with Quick 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/).