AWS drs documentation change
Summary
Minor grammatical corrections and typo fixes (e.g., 'this settings' to 'these settings', 'disc space' to 'disk space'). Also corrected a JSON example by changing 'MyAutomation' to 'MyCommand' in a resource ARN for consistency with the example context.
Security assessment
The changes are purely editorial and grammatical. The correction in the JSON example fixes a potential inconsistency in the example policy but does not indicate a security vulnerability or weakness. No security features are added or modified.
Diff
diff --git a/drs/latest/userguide/post-launch-action-settings-overview.md b/drs/latest/userguide/post-launch-action-settings-overview.md index fb53fde64..60cb43a59 100644 --- a//drs/latest/userguide/post-launch-action-settings-overview.md +++ b//drs/latest/userguide/post-launch-action-settings-overview.md @@ -13 +13 @@ After finishing the AWS DRS initialization process, you can configure your defau -You can also use this settings to install the IAM roles required for post-launch actions to work, if the roles were not already installed in your account during the first initialization of AWS DRS. The IAM roles need to be installed once per AWS account, regardless of the region used. +You can also use these settings to install the IAM roles required for post-launch actions to work, if the roles were not already installed in your account during the first initialization of AWS DRS. The IAM roles need to be installed once per AWS account, regardless of the region used. @@ -15 +15 @@ You can also use this settings to install the IAM roles required for post-launch -Post launch actions can be of two different types: command and automation. Command post-launch actions run on the launched instance using the instance profile attached to the instance. Note that if no instance profile is defined on the EC2 launch template, AWS Elastic Disaster Recovery (AWS DRS) places the **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile by default if post-launch actions is active for the source server. +Post-launch actions can be of two different types: command and automation. Command post-launch actions run on the launched instance using the instance profile attached to the instance. Note that if no instance profile is defined on the EC2 launch template, AWS Elastic Disaster Recovery (AWS DRS) places the **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile by default if post-launch actions are active for the source server. @@ -48 +48 @@ In order to run an SSM command or Automation document owned by a different accou -For example, if you have shared the SSM documents MyCommand (command) and MyAutomation (automation) from account 111111111111, you should attach these permissions to you your IAM entities: +For example, if you have shared the SSM documents MyCommand (command) and MyAutomation (automation) from account 111111111111, you should attach these permissions to your IAM entities: @@ -58 +58 @@ For example, if you have shared the SSM documents MyCommand (command) and MyAuto - "Resource": "arn:aws:ssm:*:111111111111:document/MyAutomation", + "Resource": "arn:aws:ssm:*:111111111111:document/MyCommand", @@ -110 +110 @@ For example, if you have shared the SSM documents MyCommand (command) and MyAuto -Use the **Disk space validation** feature to obtain visibility into the disc space that you have at your disposal, as well as logs with actionable insights. +Use the **Disk space validation** feature to obtain visibility into the disk space that you have at your disposal, as well as logs with actionable insights.