AWS mgn medium security documentation change
Summary
Clarified credential management process using AWS Secrets Manager and console integration
Security assessment
Emphasizes secure credential storage in Secrets Manager and proper access controls for migration operations, improving security documentation for credential handling.
Diff
diff --git a/mgn/latest/ug/connector-register-server-credentials.md b/mgn/latest/ug/connector-register-server-credentials.md index a19a8a14b..792643de1 100644 --- a//mgn/latest/ug/connector-register-server-credentials.md +++ b//mgn/latest/ug/connector-register-server-credentials.md @@ -15 +15 @@ Select the source servers you want to register to the MGN connector. Click the " -In order to perform actions on your source server, you must provide source server credentials. Server credentials are stored in AWS Secrets Manager. You can use an existing secret from the AWS Secrets Manager or create a new one. +To perform actions on your source server, you must provide source server credentials. Server credentials are stored in AWS Secrets Manager. You can use an existing secret from the AWS Secrets Manager or create a new one. You can create the credentials in the MGN console, by choosing **Register server credentials** from the **Actions** men. @@ -19 +19 @@ In order to perform actions on your source server, you must provide source serve - * Using AWS Secrets Manager AWS 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 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.