AWS Security ChangesHomeSearch

AWS drs documentation change

Service: drs · 2025-05-28 · Documentation low

File: drs/latest/userguide/failback-failover-drsfa.md

Summary

Corrected grammatical errors (ran->run), capitalization (ram->RAM), removed redundant image references, and clarified Python version requirements

Security assessment

Changes consist of grammatical corrections, typo fixes, and image removal without any references to security vulnerabilities, mitigations, or security feature enhancements. The RAM/Python version requirements and communication prerequisites appear to be standard operational requirements rather than security controls.

Diff

diff --git a/drs/latest/userguide/failback-failover-drsfa.md b/drs/latest/userguide/failback-failover-drsfa.md
index 742e99823..5dcce626c 100644
--- a//drs/latest/userguide/failback-failover-drsfa.md
+++ b//drs/latest/userguide/failback-failover-drsfa.md
@@ -27 +27 @@ These are the prerequisites for performing failback automation with the DRSFA cl
-  3. Each server that is being failed back must have at least 3 GB of ram.
+  3. Each server that is being failed back must have at least 3 GB of RAM.
@@ -35 +35 @@ These are the prerequisites for performing failback automation with the DRSFA cl
-  7. The server on which the DRSFA client is ran needs to be able to communicate with your vCenter environment. 
+  7. The server on which the DRSFA client is run needs to be able to communicate with your vCenter environment. 
@@ -37 +37 @@ These are the prerequisites for performing failback automation with the DRSFA cl
-  8. The server on which the DRSFA client is ran must have at least 4 GB of ram.
+  8. The server on which the DRSFA client is run must have at least 4 GB of RAM.
@@ -39 +39 @@ These are the prerequisites for performing failback automation with the DRSFA cl
-  9. The server on which the DRSFA client is ran must run Python 3.9.4 with pip installed (other versions of Python will not work). 
+  9. The server on which the DRSFA client is run must run Python 3.9.4 with pip installed (other versions of Python will not work). 
@@ -43 +43 @@ These are the prerequisites for performing failback automation with the DRSFA cl
-The installation procedure shown below uses Ubuntu 20.04 which has the required Python version preinstalled. 
+The installation procedure shown below uses Ubuntu 20.04 running Python 3.9.4.
@@ -45 +45 @@ The installation procedure shown below uses Ubuntu 20.04 which has the required
-  10. The server on which the DRSFA client is ran requires these tools for DRSFA Client installation. The installer will attempt to install them if they are not already present:: 
+  10. The server on which the DRSFA client is run requires these tools for DRSFA Client installation. The installer will attempt to install them if they are not already present:: 
@@ -147 +147 @@ The DRSFA client has a one-time installation. The DRSFA client will be installed
-Once installation is complete, you will need to set up a password for the VM on which the DRSFA client is ran. This is done by generating a seed.iso file that you must upload to your Datastore. Run these commands to generate the seed.iso file:
+Once installation is complete, you will need to set up a password for the VM on which the DRSFA client is run. This is done by generating a seed.iso file that you must upload to your Datastore. Run these commands to generate the seed.iso file:
@@ -260,2 +259,0 @@ The client will initiate failback. You can see the failback progress on the **Re
-![Recovery instances table showing two in-progress instances with data replication status.](/images/drs/latest/userguide/images/drsfa25.png)
-
@@ -408,2 +405,0 @@ The Client will initiate failback. You can see the failback progress on the **Re
-![Recovery instances table showing two in-progress instances with data replication status.](/images/drs/latest/userguide/images/drsfa25.png)
-
@@ -493 +489 @@ You should verify the hash of the installer after running the installation comma
-  * To troubleshoot the DRSFA Client, review the `drs_failback_automation.log` file that is generated in the `/drs_failback_automation_client/` folder on the server from which the client is ran. 
+  * To troubleshoot the DRSFA Client, review the `drs_failback_automation.log` file that is generated in the `/drs_failback_automation_client/` folder on the server from which the client is run.