AWS drs documentation change
Summary
Improved grammatical consistency (e.g., 'will install' → 'installs'), clarified policy requirements for CloudWatch Agent, and updated regional availability wording.
Security assessment
While the documentation discusses security-related elements like IAM policies and SSM permissions, the changes are purely editorial improvements without introducing new security guidance or addressing specific vulnerabilities. The clarification about CloudWatchAgentServerPolicy consequences is a documentation refinement of existing behavior.
Diff
diff --git a/drs/latest/userguide/predefined-post-launch-actions-default.md b/drs/latest/userguide/predefined-post-launch-actions-default.md index 6a588812b..85332b179 100644 --- a//drs/latest/userguide/predefined-post-launch-actions-default.md +++ b//drs/latest/userguide/predefined-post-launch-actions-default.md @@ -38 +38 @@ _**Choose from a variety of predefined post-launch actions**_ -Currently, only the following predefined post-launch actions are supported in the Middle East (UAE) Region: +These predefined post-launch actions are supported in the Middle East: (UAE) Region: @@ -63 +63 @@ Currently, only the following predefined post-launch actions are supported in th -The AWS Systems Manager (AWS SSM) allows AWS Elastic Disaster Recovery to run post-launch actions on your recovery instances after they are launched. When you activate the post-launch actions, AWS Elastic Disaster Recovery will install the **AWS SSM agent**. +The AWS Systems Manager (AWS SSM) allows AWS Elastic Disaster Recovery to run post-launch actions on your recovery instances after they are launched. When you activate the post-launch actions, AWS Elastic Disaster Recovery installs the **AWS SSM agent**. @@ -69 +69 @@ The AWS SSM agent must be installed for any other post-launch action to run. The -Use the **CloudWatch agent installation** feature to install and configure the CloudWatch Agent and Application Insights. The launched instance will require the following policies: +Use the **CloudWatch agent installation** feature to install and configure the CloudWatch Agent and Application Insights. The launched instance requires these policies: @@ -79 +79 @@ To ensure that the launch instance has the right policies, create a role that ha -You must attach both policies to the template for the CloudWatch agent to operate. Without the **CloudWatchAgentServerPolicy** , the action will still be marked as successful but the CloudWatch Agent will not be active. Configuring the Application Insights is optional. You can choose to skip the Application Insights agent configuration and only install the CloudWatch agent. To do so, simply provide the required parameterStoreName parameter and leave the other parameters empty. +You must attach both policies to the template for the CloudWatch agent to operate. Without the **CloudWatchAgentServerPolicy** , the action is still marked as successful but the CloudWatch Agent will not be active. Configuring the Application Insights is optional. You can choose to skip the Application Insights agent configuration and only install the CloudWatch agent. To do so, simply provide the required parameterStoreName parameter and leave the other parameters empty. @@ -87 +87 @@ Use the Create AMI from Instance feature to create a new Amazon Machine Image (A -The action uses the following APIs: +The action uses these APIs: @@ -96 +96 @@ The action uses the following APIs: -To allow the SSM document to run these APIs, you will need to have the required permissions or have access to a role with those permissions and then provide the role’s ARN as an input parameter to the SSM automation document. [Learn more about creating AMI from instance.](https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-aws-createimage.html) +To allow the SSM document to run these APIs, you need to have the required permissions or have access to a role with those permissions and then provide the role’s ARN as an input parameter to the SSM automation document. [Learn more about creating AMI from instance.](https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-aws-createimage.html) @@ -125 +125 @@ Up to 50 volumes can be checked in a single action. -Use the **Process status validation** feature to ensure that processes are in running state following instance launch. You will need to provide a list of processes that you want to verify, and define how long the service should wait before testing begins. +Use the **Process status validation** feature to ensure that processes are in running state following instance launch. You need to provide a list of processes that you want to verify, and define how long the service should wait before testing begins.