AWS drs documentation change
Summary
Minor grammatical and clarity improvements in documentation (e.g., 'will need' to 'need', 'triggers' to 'trigger') without altering technical meaning
Security assessment
Changes are purely grammatical corrections and phrasing improvements. No security vulnerabilities, mitigations, or security-related procedures were added or modified. The content about MAC address stability and reboot behavior remains functionally identical.
Diff
diff --git a/drs/latest/userguide/installation-requirements.md b/drs/latest/userguide/installation-requirements.md index de0106390..02e91a04d 100644 --- a//drs/latest/userguide/installation-requirements.md +++ b//drs/latest/userguide/installation-requirements.md @@ -34 +34 @@ Before installing the AWS Replication Agent on your source servers, ensure that - * Ensure MAC address stability – ensure that the MAC addresses of the source servers do not change upon a reboot or any other common changes in your network environment. AWS Elastic Disaster Recovery calculates the unique ID of the source server from the MAC address. When a MAC address changes, AWS Elastic Disaster Recovery is no longer able to correctly identify the source server. Consequently, replication will stop. If this happens, you will need to reinstall the AWS Replication Agent and start replication from the beginning. + * Ensure MAC address stability – ensure that the MAC addresses of the source servers do not change upon a reboot or any other common changes in your network environment. AWS Elastic Disaster Recovery calculates the unique ID of the source server from the MAC address. When a MAC address changes, AWS Elastic Disaster Recovery is no longer able to correctly identify the source server. Consequently, replication stops. If this happens, you need to reinstall the AWS Replication Agent and start replication from the beginning. @@ -110 +110 @@ The version number of the kernel headers should be identical to the version numb - 3. Verify that the folder that contains the kernel-devel/linux-headers is not a symbolic link. If the content of the kernel-devel/linux-headers, which match the version of the kernel, is actually a symbolic link, you will need to remove the link before installing the required package. + 3. Verify that the folder that contains the kernel-devel/linux-headers is not a symbolic link. If the content of the kernel-devel/linux-headers, which match the version of the kernel, is actually a symbolic link, you need to remove the link before installing the required package. @@ -163 +163 @@ To download the matching kernel-devel/linux-headers package, navigate to: - * A graceful reboot from the OS menu or Windows CLI of a Windows source server does not triggers a rescan in AWS DRS once the source server is restarted. Hard reboots, disk changes, and crashes trigger a rescan. + * A graceful reboot from the OS menu or Windows CLI of a Windows source server does not trigger a rescan in AWS DRS once the source server is restarted. Hard reboots, disk changes, and crashes trigger a rescan.