AWS guidance documentation change
Summary
Fixed punctuation and grammar: added missing comma in Organizations trusted access note and corrected punctuation/contraction in account ID specification.
Security assessment
Changes are grammatical improvements without security implications. The trusted access prerequisite mention is unchanged in substance, and no security features or vulnerabilities are addressed.
Diff
diff --git a/guidance/latest/cloud-intelligence-dashboards/data-collection-deployment.md b/guidance/latest/cloud-intelligence-dashboards/data-collection-deployment.md index 032b17f42..769d60647 100644 --- a//guidance/latest/cloud-intelligence-dashboards/data-collection-deployment.md +++ b//guidance/latest/cloud-intelligence-dashboards/data-collection-deployment.md @@ -30 +30 @@ Deployment of the stack consists of 2 steps. First step is in Management Account -Prerequisites: Make sure the [trusted access with AWS Organizations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-activate-trusted-access.html) is activated. The Management Account stack makes use of [stack sets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/what-is-cfnstacksets.html) configured to use [service-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html#stacksets-concepts-stackset-permission-models) to deploy stack instances to linked accounts in the AWS Organization. Typically in Organizations it is already the case. For the new Organization you can activate it by going to [StakSet page of CloudFormation](https://console.aws.amazon.com/cloudformation/home?#/stacksets) if this access is not activated you will see the banner with an action button to do so. **Note:** If you do not have access to the Management Account, you can perform an [alternate deployment](./data-collection-without-org.html) of certain modules with a manually created list of Linked Accounts. +Prerequisites: Make sure the [trusted access with AWS Organizations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-activate-trusted-access.html) is activated. The Management Account stack makes use of [stack sets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/what-is-cfnstacksets.html) configured to use [service-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html#stacksets-concepts-stackset-permission-models) to deploy stack instances to linked accounts in the AWS Organization. Typically in Organizations it is already the case. For the new Organization you can activate it by going to [StakSet page of CloudFormation](https://console.aws.amazon.com/cloudformation/home?#/stacksets) if this access is not activated, you will see the banner with an action button to do so. **Note:** If you do not have access to the Management Account, you can perform an [alternate deployment](./data-collection-without-org.html) of certain modules with a manually created list of Linked Accounts. @@ -52 +52 @@ Login to Management Account and click Launch Stack for deploying [Permission Sta - 1. Please make sure you specify **Data Collection Account Id** correctly. It is not the Management Account Id, its an ID of the dedicated Data Collection Account. + 1. Please make sure you specify **Data Collection Account Id** correctly. It is not the Management Account Id; it’s an ID of the dedicated Data Collection Account.