AWS guidance documentation change
Summary
Updated references from 'Quicksight' to 'Quick Sight' throughout documentation for naming consistency.
Security assessment
Documentation standardization change without any functional impact. Security controls and configurations remain unchanged.
Diff
diff --git a/guidance/latest/cloud-intelligence-dashboards/row-level-security.md b/guidance/latest/cloud-intelligence-dashboards/row-level-security.md index e8f37687f..bf4be4514 100644 --- a//guidance/latest/cloud-intelligence-dashboards/row-level-security.md +++ b//guidance/latest/cloud-intelligence-dashboards/row-level-security.md @@ -107 +107 @@ Login to Management Account and click Launch Stack for deploying [Permission Sta -You must tag the AWS Organization Resources with the emails of the Quicksight Users that you wish to allow access to see the resources cost data. The below will show you how to tag a resource and this can be repeated. We will be using **AWS Quicksight User Emails** , see more [here](https://docs.aws.amazon.com/quicksight/latest/user/managing-users.html). If you have a large list of accounts and want to use a script, please see the section below Use script to tag accounts. +You must tag the AWS Organization Resources with the emails of the Quick Sight Users that you wish to allow access to see the resources cost data. The below will show you how to tag a resource and this can be repeated. We will be using **AWS Quick Sight User Emails** , see more [here](https://docs.aws.amazon.com/quicksight/latest/user/managing-users.html). If you have a large list of accounts and want to use a script, please see the section below Use script to tag accounts. @@ -173 +173 @@ Using AWS CloudFormation we will deploy the lambda function to collect these tag - * `DestinationBucket` \- Amazon S3 Bucket in your account in the same region (this can be one from your Optimization data collector where where your CUR is stored). This bucket must have access to Amazon Quicksight + * `DestinationBucket` \- Amazon S3 Bucket in your account in the same region (this can be one from your Optimization data collector where where your CUR is stored). This bucket must have access to Amazon Quick Sight