AWS mgn documentation change
Summary
Clarified disk replication requirements when using --no-prompt parameter
Security assessment
Improved clarity about disk selection requirements but no security vulnerabilities or security features addressed
Diff
diff --git a/mgn/latest/ug/linux-agent.md b/mgn/latest/ug/linux-agent.md index 3d313b867..0e627f774 100644 --- a//mgn/latest/ug/linux-agent.md +++ b//mgn/latest/ug/linux-agent.md @@ -108 +108 @@ Available parameters include: -This parameter will run a silent installation. +This parameter runs a silent installation. @@ -116 +116 @@ This parameter specifies which specific disks to replicate. The devices should b -This parameter must be used with the --no-prompt parameter. This parameter will cancel the automatic detection of physical disks to replicate. You will need to specify the exact disks to replicate using the --devices parameter (including the root disk, failure to specify the root disk will cause replication to fail). This parameter should only be used as a troubleshooting tool if the --devices parameter fails to identify the disks correctly. +This parameter must be used with the --no-prompt parameter. This parameter cancels the automatic detection of physical disks to replicate. You need to specify the exact disks to replicate using the --devices parameter (including the root disk, failure to specify the root disk causes replication to fail). This parameter should only be used as a troubleshooting tool if the --devices parameter fails to identify the disks correctly. @@ -158 +158 @@ The installer confirms that the installation of the AWS Replication Agent has st - 6. Once you have entered your credentials, the installer will identify volumes for replication. The installer displays the identified disks and prompt you to choose the disks you want to replicate. + 6. Once you have entered your credentials, the installer identifies volumes for replication. The installer displays the identified disks and prompt you to choose the disks you want to replicate. @@ -176 +176 @@ When identifying specific disks for replication, do not use apostrophes, bracket - * AWS Application Migration Service replicates whole disks. Therefore, if you choose to replicate a partition, its entire disk will appear on the list and will later be replicated. If several partitions on the same disk are selected, then the disk encompassing all of them will appear only once on the list. + * AWS Application Migration Service replicates whole disks. Therefore, if you choose to replicate a partition, its entire disk appears on the list and is later replicated. If several partitions on the same disk are selected then that disk appears only once on the list. @@ -184 +184 @@ If disks are disconnected from a server, AWS Application Migration Service can n -Note that the returned disks will need be replicated from the beginning. Any disk size changes are automatically identified, but this also causes a resync. Perform a test after installing the Agent to ensure that the correct disks have been added. +Note that the returned disks need be replicated from the beginning. Any disk size changes are automatically identified, but this also causes a resync. Perform a test after installing the Agent to ensure that the correct disks have been added. @@ -186 +186 @@ Note that the returned disks will need be replicated from the beginning. Any dis - 7. After all of the disks that to be replicated have been successfully identified, the installer will download and install the AWS Replication Agent on the source server. + 7. After all of the disks that are to be replicated have been successfully identified, the installer downloads and installs the AWS Replication Agent on the source server. @@ -190 +190 @@ Note that the returned disks will need be replicated from the beginning. Any dis - 8. Once the AWS Replication Agent is installed, the server is added to the AWS Application Migration Service Console and undergoes the initial sync process. The installer provides you with the source server's ID. + 8. Once the AWS Replication Agent is installed, the server is added to the AWS Application Migration Service console and undergoes the initial sync process. The installer provides you with the source server's ID.