AWS mgn documentation change
Summary
Restructured installation requirements documentation, split OS support into separate sections, added detailed disk space checks, clarified paravirtualization limitations, and explicitly noted Secure Boot unsupported in Linux.
Security assessment
The change adds documentation about Secure Boot being unsupported (a security feature) and clarifies paravirtualization limitations, but there's no evidence these changes address an active security vulnerability or incident.
Diff
diff --git a/mgn/latest/ug/installation-requirements.md b/mgn/latest/ug/installation-requirements.md index 84fea327d..0a5e20812 100644 --- a/mgn/latest/ug/installation-requirements.md +++ b/mgn/latest/ug/installation-requirements.md @@ -5 +5 @@ -General requirementsSource server requirementsLinux installation requirementsWindows installation requirements +General requirementsLinux installation requirementsWindows installation requirements @@ -9 +9 @@ General requirementsSource server requirementsLinux installation requirementsWin -Before installing the AWS Replication Agent on your source servers, ensure that they meet the following requirements: +Before installing the AWS Replication Agent on your source servers, ensure that they meet these requirements: @@ -13 +13,5 @@ Before installing the AWS Replication Agent on your source servers, ensure that - * Ensure that the source server operating system is supported by AWS. [Learn more about supported operating systems.](./Supported-Operating-Systems.html) + * Ensure that the source server operating system is supported by AWS. + + * [Supported Windows operating systems.](./Supported-Operating-Systems-Windows.html) + + * [Supported Linux operating systems.](./Supported-Operating-Systems-Linux.html) @@ -18,0 +23 @@ Before installing the AWS Replication Agent on your source servers, ensure that + * AWS Application Migration Service does not support fully paravirtualized source servers. Source servers with partial paravirtualization, such as VMWare's paravirtualization of I/O devices, is supported. @@ -19,0 +25 @@ Before installing the AWS Replication Agent on your source servers, ensure that + * The AWS Replication Agent installer supports multipath. @@ -22 +27,0 @@ Before installing the AWS Replication Agent on your source servers, ensure that -## Source server requirements @@ -24,3 +28,0 @@ Before installing the AWS Replication Agent on your source servers, ensure that -The following are universal requirements for both Linux and Windows source servers: - - * Root directory – Verify that your source server has at least 2 GB of free disk space on the root directory (/) . @@ -28 +30 @@ The following are universal requirements for both Linux and Windows source serve - * RAM – Verify that your source server has at least 300 MB of free RAM to run the AWS Replication Agent. +### Source server requirements @@ -29,0 +32 @@ The following are universal requirements for both Linux and Windows source serve +These are universal requirements for both Linux and Windows source servers: @@ -30,0 +34 @@ The following are universal requirements for both Linux and Windows source serve + * Root directory – Verify that your source server has at least 2 GB of free disk space on the root directory (/) . @@ -31,0 +36 @@ The following are universal requirements for both Linux and Windows source serve + * Verify that your source server has at least 300 MB of free RAM to run the AWS Replication Agent. @@ -33 +38 @@ The following are universal requirements for both Linux and Windows source serve -###### Note + * Application Migration Service only supports operating systems built for the x86 system architecture. @@ -35 +39,0 @@ The following are universal requirements for both Linux and Windows source serve -AWS Application Migration Service does not support fully paravirtualized source servers. Source servers with partial paravirtualization, such as VMWare's paravirtualization of I/O devices, is supported. @@ -37 +40,0 @@ AWS Application Migration Service does not support fully paravirtualized source -###### Note @@ -39 +41,0 @@ AWS Application Migration Service does not support fully paravirtualized source -The AWS Replication Agent installer supports multipath. @@ -43 +45 @@ The AWS Replication Agent installer supports multipath. -Ensure that your Linux source server meets the following installation requirements prior to installing the AWS Replication Agent: +Ensure that your Linux source server meets these installation requirements prior to installing the AWS Replication Agent: @@ -47 +49 @@ Ensure that your Linux source server meets the following installation requiremen - * The following tools are required for agent installation only. The installer will attempt to install them if they are not present already: + * These tools are required for agent installation only. The installer will attempt to install them if they are not present already: @@ -51 +53 @@ Ensure that your Linux source server meets the following installation requiremen - * Verify that you have at least 2 GB of free disk space on the root directory (/) of your source server for the installation. To check the available disk space on the root directory, run the following command: `df -h /` + * Verify that you meet these disk space requirements: @@ -53 +55 @@ Ensure that your Linux source server meets the following installation requiremen - * Free disk space on the _/tmp_ directory – for the duration of the installation process only, verify that you have at least 500 MB of free disk space on the _/tmp_ directory. To check the available disk space on the _/tmp_ directory run the following command: `df -h /tmp` + * At least 2 GB of free disk space on the root directory (/) of your source server for the installation. To check the available disk space on the root directory, run the `df -h /` command. @@ -55 +57,5 @@ Ensure that your Linux source server meets the following installation requiremen -After you have entered the above commands for checking the available disk space, the results will be displayed as follows: + * At least 500 MB of free diskspace on the _/tmp_ directory for the duration of the installation process. To check the available disk space on the /tmp directory run the `df -h /tmp` command. + + * If `/boot` is a separate partition, ensure that it has a minimum of 50 MB free space needed for the installation. To check the available disk space on the /boot directory run the `df -h /boot` command. + +After you have entered the commands for checking the available disk space, the results are displayed as: @@ -59 +65,9 @@ After you have entered the above commands for checking the available disk space, - * The active bootloader software is GRUB 1 or 2. + * Ensure that you have Python installed on the source server (version 2.4+, version 3.0+) for Agent installation. + + * Only servers using the GRUB bootloader (GRUB 1 or 2) are supported. + + * Machines that boot off a disk configured with GPT partitioning must have the package 'grub2-pc-modules' installed + + * Secure Boot is not supported in Linux. + + * Boot disks that span multiple physical disks are not supported. @@ -65 +79 @@ After you have entered the above commands for checking the available disk space, -To verify that the _/tmp_ directory is mounted without the noexec option, run the following command: `sudo mount | grep '/tmp'` +To verify that the _/tmp_ directory is mounted without the noexec option, run this command: `sudo mount | grep '/tmp'` @@ -67 +81 @@ To verify that the _/tmp_ directory is mounted without the noexec option, run th -If the result is similar to the following example, it means that the issue exists in your OS: +If the result is similar to this example, it means that the issue exists in your OS: @@ -72 +86 @@ If the result is similar to the following example, it means that the issue exist -To fix and remove the _noexec_ option from the mounted _/tmp_ directory, run the following command: `sudo mount -o remount,exec /tmp` +To fix and remove the _noexec_ option from the mounted _/tmp_ directory, run this command: `sudo mount -o remount,exec /tmp` @@ -74 +88 @@ To fix and remove the _noexec_ option from the mounted _/tmp_ directory, run the -The following example illustrates the troubleshooting procedure: +This example illustrates the troubleshooting procedure: @@ -110 +124 @@ The _uname -r_ output version should match the version of one of the installed k -To identify the version of your running kernel, run the following command: +To identify the version of your running kernel, run this command: @@ -130 +144 @@ Sometimes, the content of the _kernel-devel/linux-headers_ , which match the ver -To verify that the folder that contains the _kernel-devel/linux-headers_ is not a symbolic link, run the following command: +To verify that the folder that contains the _kernel-devel/linux-headers_ is not a symbolic link, run this command: @@ -146 +160 @@ In the above example, the results show that the actual **linux-headers-*** folde -If you found that the content of the _kernel-devel/linux-headers_ , which match the version of the kernel, is a symbolic link, you need to delete the link. Run the following command: `rm /usr/src/<LINK NAME>` +If you found that the content of the _kernel-devel/linux-headers_ , which match the version of the kernel, is a symbolic link, you need to delete the link. Run this command: `rm /usr/src/<LINK NAME>` @@ -162 +176 @@ For everything to work, you need to install a kernel headers package with the ex -To install the correct _kernel-devel/linux-headers_ , run the following command: +To install the correct _kernel-devel/linux-headers_ , run this command: @@ -184 +198 @@ If no matching package was found on the repositories configured on your server, -To download the matching _kernel-devel/linux-headers_ package, navigate to the following sites: +To download the matching _kernel-devel/linux-headers_ package, navigate to these sites: @@ -201 +215 @@ If the kernel-devel/linux-headers packages are not available for the current run -Ensure that your source server operating system is supported. [Learn more about supported operating systems.](./Supported-Operating-Systems.html) +Ensure that your source server operating system is supported. See [Supported Windows operating systems.](./Supported-Operating-Systems-Windows.html) @@ -207 +221,3 @@ Ensure that your source server meets the agent installation hardware requirement - * At least 300 MB of free RAM + * Install all available Windows updates on the server. + + * A graceful reboot from the OS menu or Windows CLI of a Windows source server does not triggers a rescan in Application Migration Service once the source server is restarted. Hard reboots, disk changes, and crashes trigger a rescan. @@ -208,0 +225 @@ Ensure that your source server meets the agent installation hardware requirement + * Mount points must be assigned a drive letter to be recognized by AWS Application Migration Service. A folder path is not recognized. @@ -212 +228,0 @@ Ensure that your source server meets the agent installation hardware requirement -[Learn more about AWS Replication Agent installation hardware requirements.](./installation-requirements.html) @@ -220 +236 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Supported operating systems +Adding source servers @@ -222 +238 @@ Supported operating systems -Installing the AWS Replication Agent +Supported Windows operating systems