AWS Security ChangesHomeSearch

AWS drs documentation change

Service: drs · 2025-06-16 · Documentation low

File: drs/latest/userguide/post-launch-action-settings-activation-default.md

Summary

Updated activation/deactivation instructions with minor wording changes (click→select) and removed image references

Security assessment

Changes are editorial improvements to user interface instructions and grammar. No security vulnerabilities or new security features are mentioned. The IAM role requirement was already documented previously.

Diff

diff --git a/drs/latest/userguide/post-launch-action-settings-activation-default.md b/drs/latest/userguide/post-launch-action-settings-activation-default.md
index be2441985..bb72e185a 100644
--- a//drs/latest/userguide/post-launch-action-settings-activation-default.md
+++ b//drs/latest/userguide/post-launch-action-settings-activation-default.md
@@ -7 +7 @@
-Activate post-launch actions in the default settings, to make it active by default for newly added source servers, and to allow to update the default list of actions. Activating and deactivating is only possible if the required IAM roles have been installed.
+Activate post-launch actions in the default settings, to make it active by default for newly added source servers and to enable updating of the default list of actions. Activating and deactivating is only possible if the required IAM roles have been installed.
@@ -9 +9 @@ Activate post-launch actions in the default settings, to make it active by defau
-To activate, make sure the required IAM role is installed by following [this guide](https://docs.aws.amazon.com/drs/latest/userguide/post-launch-action-settings-roles.html). After that, go to **Settings → Default post-launch actions** and check **Post-launch actions settings** to see if **Post-launch actions** is set to **Active**. In case it is not, click **Edit** and make sure **Post-launch actions activated** is checked. Then click **Save** to store these settings. 
+To activate, make sure the required IAM role is installed by following [this guide](https://docs.aws.amazon.com/drs/latest/userguide/post-launch-action-settings-roles.html). After that, go to **Settings → Default post-launch actions** and check **Post-launch actions settings** to see if **Post-launch actions** is set to **Active**. In case it is not, select **Edit** and make sure **Post-launch actions activated** is checked. Then select **Save** to store these settings. 
@@ -11,5 +11 @@ To activate, make sure the required IAM role is installed by following [this gui
-![AWS Elastic Disaster Recovery settings page for default post-launch actions configuration.](/images/drs/latest/userguide/images/drs-new-post-launch-actions-2.png)
-
-To deactivate go to **Settings → Default post-launch actions** and check **Post-launch actions settings** to see if **Post-launch actions** is set to **Not active**. In case it is not, click **Edit** and make sure **Post-launch actions activated** is not checked. Then click **Save** to store these settings. 
-
-![AWS Elastic Disaster Recovery settings page for configuring default post-launch actions.](/images/drs/latest/userguide/images/drs-new-post-launch-actions-3.png)
+To deactivate go to **Settings → Default post-launch actions** and check **Post-launch actions settings** to see if **Post-launch actions** is set to **Not active**. In case it is not, select **Edit** and make sure **Post-launch actions activated** is not checked. Then select **Save** to store these settings.