AWS AWSCloudFormation documentation change
Summary
Added link to prerequisites documentation and updated CLI command syntax for stack set creation
Security assessment
The changes are related to documentation improvements and CLI command syntax updates, with no specific security context or vulnerability addressed.
Diff
diff --git a/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create-self-managed.md index 162617f58..ac02736a9 100644 --- a/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create-self-managed.md +++ b/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create-self-managed.md @@ -11 +11 @@ With `self-managed` permissions, you can deploy stack instances to specific AWS -Before you complete one of the following procedures, verify that the IAM roles `AWSCloudFormationStackSetExecutionRole` and `AWSCloudFormationStackSetAdministrationRole` exist in your administrator account. To launch stacks in accounts other than your administrator account, verify that the IAM role `AWSCloudFormationStackSetExecutionRole` exists in the target accounts. +Before you complete one of the following procedures, verify that the IAM roles `AWSCloudFormationStackSetExecutionRole` and `AWSCloudFormationStackSetAdministrationRole` exist in your administrator account. To launch stacks in accounts other than your administrator account, verify that the IAM role `AWSCloudFormationStackSetExecutionRole` exists in the target accounts. For more information, see [Give all users of the administrator account permissions to manage stacks in all target accounts](./stacksets-prereqs-self-managed.html#stacksets-prereqs-accountsetup). @@ -109 +109 @@ When you create stack sets by using AWS CLI commands, you run two separate comma - 1. Start by running the following [create-stack-set](https://docs.aws.amazon.com/cli/latest/reference/cloudformation/create-stack-set.html) command to upload the sample template that enables AWS Config. For the `--template-url` option, provide the URL of the Amazon S3 bucket where your template is located. In this example, we use `my-awsconfig-stackset` as the value of the `--stack-set-name` option. + 1. Start by running the following [create-stack-set](https://docs.aws.amazon.com/cli/latest/reference/cloudformation/create-stack-set.html) command to upload the sample template that enables AWS Config. For the `--template-url` option, provide the URL of the Amazon S3 bucket where your template is located. In this example, we use `my-awsconfig-stackset` as the value of the `--stack-set-name` option. The `--parameters` option is included to work with the `EnableAWSConfig.yml` template we include. If you use your own template, adjust the command to your needs. @@ -113 +113,2 @@ When you create stack sets by using AWS CLI commands, you run two separate comma - --template-url https://s3.amazonaws.com/cloudformation-stackset-sample-templates-us-east-1/EnableAWSConfig.yml + --template-url https://s3.amazonaws.com/cloudformation-stackset-sample-templates-us-east-1/EnableAWSConfig.yml \ + --parameters ParameterKey=RecordingFrequency,ParameterValue="DAILY" @@ -129,2 +130,2 @@ You can't modify your stack set's execution configuration while there are runnin - --accounts '["account_ID_1","account_ID_2"]' \ - --regions '["us-west-2","us-east-1"]' + --accounts account_ID_1 account_ID_2 \ + --regions us-west-2 us-east-1