AWS drs documentation change
Summary
Fixed typos: 'System Manager' to 'Systems Manager' (two occurrences) and 'Advance' to 'Advanced' in EC2 launch template settings.
Security assessment
Changes are typographical corrections and do not address any security vulnerabilities or introduce security features. The change from 'Advance' to 'Advanced' is a spelling fix in a UI label reference.
Diff
diff --git a/drs/latest/userguide/post-launch-action-settings-adding-custom-source.md b/drs/latest/userguide/post-launch-action-settings-adding-custom-source.md index 46e4f0f93..50d2a91f6 100644 --- a//drs/latest/userguide/post-launch-action-settings-adding-custom-source.md +++ b//drs/latest/userguide/post-launch-action-settings-adding-custom-source.md @@ -25 +25 @@ The **Add action** page includes these parameters: - * **System Manager document name** – Select any Systems Manager document that is available to be used in this account. + * **Systems Manager document name** – Select any Systems Manager document that is available to be used in this account. @@ -27 +27 @@ The **Add action** page includes these parameters: - * **View in Systems Manager** – Click to open **System Managers** and view additional information about the document. + * **View in Systems Manager** – Click to open **Systems Manager** and view additional information about the document. @@ -48 +48 @@ The **Action parameters** change according to the specific SSM document that is -AWS Elastic Disaster Recovery (AWS DRS) places **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile on the launch instance if post-launch actions is active for the source server. If you add an SSM command action that requires additional permissions in the launch instance, you must ensure that the instance profile has the right policies or the right permissions. In order to do so, create a role that has the required permissions as per the policies above or has a policy or policies with those permissions attached to it. Go to **Launch settings** > **EC2 launch template** > **Modify** > **Advance** > **IAM instance profile**. Use an existing profile or create a new one using the **Create new IAM profile** link. +AWS Elastic Disaster Recovery (AWS DRS) places **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** instance profile on the launch instance if post-launch actions is active for the source server. If you add an SSM command action that requires additional permissions in the launch instance, you must ensure that the instance profile has the right policies or the right permissions. In order to do so, create a role that has the required permissions as per the policies above or has a policy or policies with those permissions attached to it. Go to **Launch settings** > **EC2 launch template** > **Modify** > **Advanced** > **IAM instance profile**. Use an existing profile or create a new one using the **Create new IAM profile** link.