AWS mgn documentation change
Summary
Updated terminology from 'click' to 'choose' and simplified phrasing about Secrets Manager credentials
Security assessment
Terminology changes don't alter security posture. Minor phrasing update about Secrets Manager doesn't introduce new security documentation or address vulnerabilities.
Diff
diff --git a/mgn/latest/ug/connector-register-server-credentials.md b/mgn/latest/ug/connector-register-server-credentials.md index 444b67378..efd1abedd 100644 --- a//mgn/latest/ug/connector-register-server-credentials.md +++ b//mgn/latest/ug/connector-register-server-credentials.md @@ -11 +11 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -Once you have the MGN connector set up and ready to use, you can register source servers to the MGN connector. To do so click on the MGN connector name, then click “Register servers“. +Once you have the MGN connector set up and ready to use, you can register source servers to the MGN connector. To do so choose on the MGN connector name, then choose “Register servers“. @@ -15 +15 @@ The servers list contain the source servers that were imported via the import fe -Select the source servers you want to register to the MGN connector. Click the "Register servers with the MGN connector" button. +Select the source servers you want to register to the MGN connector. Choose the "Register servers with the MGN connector" button. @@ -21 +21 @@ To perform actions on your source server, you must provide source server credent - * Using AWS Secrets Manager MGN can use the stored source server credentials and API keys in order to connect to the source machine and perform actions on it. You must specify the secret that stores the source server credentials, using an existing secret. + * Using AWS Secrets Manager MGN can use the stored source server credentials and API keys to connect to the source machine and perform actions on it. You must specify the secret that stores the source server credentials, using an existing secret.