AWS drs documentation change
Summary
Improved grammar in action descriptions and simplified permission attachment instructions
Security assessment
Changes focus on grammatical clarity and consistency in describing existing security controls (IAM roles for SSM automation). No new security capabilities or vulnerability mitigations are introduced. The cross-account SSM document permissions explanation remains functionally unchanged.
Diff
diff --git a/drs/latest/userguide/post-launch-action-settings-overview.md b/drs/latest/userguide/post-launch-action-settings-overview.md index c16a96cd5..5c8e56bb3 100644 --- a//drs/latest/userguide/post-launch-action-settings-overview.md +++ b//drs/latest/userguide/post-launch-action-settings-overview.md @@ -9 +9 @@ Validate disk spaceAmazon EC2 connectivity checksVerify HTTP/HTTPS responseVerif -After finishing the AWS DRS initialization process, you can configure your default post-launch actions settings. The default post-launch actions settings apply to newly added source servers and controls which post-launch actions will run when launching new instances. These settings are created automatically for each server based on the default settings and can be modified at any time for any individual source server. +After finishing the AWS DRS initialization process, you can configure your default post-launch actions settings. The default post-launch actions settings apply to newly added source servers and controls which post-launch actions run when launching new instances. These settings are created automatically for each server based on the default settings and can be modified at any time for any individual source server. @@ -15 +15 @@ Post launch actions can be of two different types: command and automation. Comma -Automation actions run with the credentials of the same IAM entity that started the drill, recovery or failback. In addition some automation actions accept a parameter that is sent to the assumeRole key in the SSM document if provided, the action will assume that role for that action execution. +Automation actions run with the credentials of the same IAM entity that started the drill, recovery or failback. In addition some automation actions accept a parameter that is sent to the assumeRole key in the SSM document if provided, the action assumes that role for that action execution. @@ -30 +30 @@ 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 the following 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 you your IAM entities: @@ -102 +102 @@ Up to 5 Port:IP couples can be checked in a single action. -Use the **Verify HTTP/HTTPS response** feature to conduct HTTP/HTTPS connectivity checks to a predefined list of URLs. The feature will verify that HTTP/HTTPS requests (for example, https://localhost) receive the correct response. +Use the **Verify HTTP/HTTPS response** feature to conduct HTTP/HTTPS connectivity checks to a predefined list of URLs. The feature verifies that HTTP/HTTPS requests (for example, https://localhost) receive the correct response.