AWS mgn medium security documentation change
Summary
Updated guidance to recommend using same policy for long-term credentials as temporary credentials instead of linking to separate documentation
Security assessment
The change emphasizes policy consistency between credential types, reducing risk of misconfigured long-term credentials which are more vulnerable to compromise. By aligning policies, it reinforces security best practices for sensitive credentials.
Diff
diff --git a/mgn/latest/ug/credentials.md b/mgn/latest/ug/credentials.md index 0603a785b..e9cda65c9 100644 --- a//mgn/latest/ug/credentials.md +++ b//mgn/latest/ug/credentials.md @@ -34 +34 @@ An example of generating temporary credentials via AWS CLI can be found [here](h -Where possible, we recommend using temporary credentials instead of creating users who have long-term credentials such as passwords and access keys. However, there are specific use cases that require long-term credentials (for example, agentless snapshot based replications). [Learn more about long-term credentials.](./vcenter-credentials-mgn.html) +Where possible, we recommend using temporary credentials instead of creating users who have long-term credentials such as passwords and access keys. However, there are specific use cases that require long-term credentials (for example, agentless snapshot based replications). In general, you should be able to use the same policy as recommended above in _Temporary Credentials_.