AWS drs documentation change
Summary
Updated documentation for editing post-launch actions with restructured parameter descriptions, UI terminology changes ('click' to 'choose'), and added details about action activation/configuration parameters including security-related categories.
Security assessment
The changes document security-related configuration options (e.g., security category selection) and clarify how action success impacts launch status reporting. While these relate to security features, there's no evidence of addressing a specific vulnerability. The addition of security category documentation demonstrates expanded security feature awareness.
Diff
diff --git a/drs/latest/userguide/post-launch-action-settings-editing-source.md b/drs/latest/userguide/post-launch-action-settings-editing-source.md index b2879edc5..cba33b621 100644 --- a//drs/latest/userguide/post-launch-action-settings-editing-source.md +++ b//drs/latest/userguide/post-launch-action-settings-editing-source.md @@ -9 +9 @@ Activating, deactivating and editing predefined or custom actions -You can activate, deactivate and edit actions available for this source server. Activating an action will ensure it runs after launching a recovery instance. Likewise, deactivating it, prevents it from being run after launching a recovery instance. The default settings are not affected by activating, deactivating or editing an action for a source server. Editing an action for a source server updates it for that source server. These changes are not reflected on the action, if it exists in the default post-launch actions settings. Changes to actions in the default settings, as to apply to newly added source servers, can be done from the **Settings → Default post-launch actions** page. +You can activate, deactivate and edit actions available for this source server. Activating an action ensures it runs after launching a recovery instance. Likewise, deactivating it, prevents it from being run after launching a recovery instance. The default settings are not affected by activating, deactivating or editing an action for a source server. Editing an action for a source server updates it for that source server. These changes are not reflected on the action, if it exists in the default post-launch actions settings. Changes to actions in the default settings, as to apply to newly added source servers, can be done from the **Settings → Default post-launch actions** page. @@ -19,5 +19 @@ Locate the action you want to edit in the **Actions** card view, or use the sear - - -Click on the action’s card to select it, and then click on the **Edit** button. - - +Choose the action’s card to select it, and then choose the **Edit** button. @@ -27 +23 @@ To activate the action, make sure the **Activate this action setting** is checke -The edit page allows to change the value of some of the parameters for both pre-defined actions and custom actions. Some parameters can only be edited if the action is a custom action. See below for specific information. +The edit page allow you to change the value of some of the parameters for both pre-defined actions and custom actions. Some parameters can only be edited if the action is a custom action. See below for specific information. @@ -31 +27,7 @@ The parameters that appear on the edit page: -**Action name** – Editable for custom actions. The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region. + * **Action name** – Editable for custom actions. The name of the action in AWS DRS, which should be intuitive, meaningful and unique in this AWS account and region. + + * **Activate this action** – Use this checkbox to activate or deactivate the action for this source server. Only active actions run after the launch of a recovery instance. + + * **Mark launch as successful only if this action finishes running successfully** – This checkbox dictates whether or not the launch is marked as successful, based on the successful run of this action. Instances launches progress normally regardless of the success of the action. + + * **System Manager document name** – Editable for custom actions. Select any Systems Manager document that is available to be used in this account. @@ -33 +35 @@ The parameters that appear on the edit page: -**Activate this action** – Use this checkbox to activate or deactivate the action for this source server. Only active actions will run after the launch of a recovery instance. + * **View in Systems Manager** – Click to open **System Managers** and view additional information about the document. @@ -35 +37 @@ The parameters that appear on the edit page: -**Mark launch as successful only if this action finishes running successfully** – This checkbox will dictate whether or not the launch will be marked as successful, based on the successful run of this action. Instances launches will still progress normally regardless of the success of the action. + * **Description** – Editable for custom actions. Add a description or keep the default. @@ -37 +39 @@ The parameters that appear on the edit page: -**System Manager document name** – Editable for custom actions. Select any Systems Manager document that is available to be used in this account. + * **Document version** – Editable for custom actions. Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences. @@ -39 +41 @@ The parameters that appear on the edit page: -**View in Systems Manager** – Click to open **System Managers** and view additional information about the document. + * **Category** – Editable for custom actions. Select from various available categories including monitoring, validation, security and more. @@ -41 +43 @@ The parameters that appear on the edit page: -**Description** – Editable for custom actions. Add a description or keep the default. + * **Order** – Specify the order in which the actions run. The lower the number, the earlier the action runs. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive. @@ -43 +45 @@ The parameters that appear on the edit page: -**Document version** – Editable for custom actions. Select which SSM document version to run. AWS DRS can run a default version, the latest version, or a specific version, according to your preferences. + * **Platform** – Not editable. Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. @@ -45 +47 @@ The parameters that appear on the edit page: -**Category** – Editable for custom actions. Select from various available categories including monitoring, validation, security and more. + * **Creator** – Not editable. Who created the action. For custom actions, the default is always **This account**. @@ -47 +48,0 @@ The parameters that appear on the edit page: -**Order** – Specify the order in which the actions will run. The lower the number, the earlier the action will run. Values allowed are between 2 and 10,000. The numbers must be unique but don’t need to be consecutive. @@ -49 +49,0 @@ The parameters that appear on the edit page: -**Platform** – Not editable. Taken from the SSM document and reports which Operating System platform (Windows/Linux) is supported by the action. @@ -51 +50,0 @@ The parameters that appear on the edit page: -**Creator** – Not editable. Who created the action. For custom actions, the default is always **This account**. @@ -53 +52 @@ The parameters that appear on the edit page: -The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS will dynamically populate the value. Some predefined actions, where applicable allow to use a dynamically populated value for the volumes. This value will be dynamically populated by AWS DRS with the volumes of the instance being launched. +The **Action parameters** change according to the specific SSM document that is selected. Note that for the instance ID parameter, you can choose to use the launch instance ID, in which case, AWS DRS dynamically populates the value. Some predefined actions, where applicable allow to use a dynamically populated value for the volumes. This value is dynamically populated by AWS DRS with the volumes of the instance being launched.