AWS cloudhsm documentation change
Summary
Standardized placeholder casing in MFA rotation commands and JSON examples
Security assessment
Changes normalize placeholder formatting from <USERNAME> to <username> but do not modify security functionality or address vulnerabilities. Documentation maintains existing security processes.
Diff
diff --git a/cloudhsm/latest/userguide/rotate-mfa-cloudhsm-cli.md b/cloudhsm/latest/userguide/rotate-mfa-cloudhsm-cli.md index 826c9df47..d8a36ffef 100644 --- a/cloudhsm/latest/userguide/rotate-mfa-cloudhsm-cli.md +++ b/cloudhsm/latest/userguide/rotate-mfa-cloudhsm-cli.md @@ -13 +13 @@ Follow these steps to rotate keys for AWS CloudHSM users with multi-factor authe - aws-cloudhsm > user change-mfa token-sign --token unsigned-tokens.json --username <USERNAME> --role crypto-user --change-quorum + aws-cloudhsm > user change-mfa token-sign --token unsigned-tokens.json --username <username> --role crypto-user --change-quorum @@ -104 +101 @@ Follow these steps to rotate keys for AWS CloudHSM users with multi-factor authe - "username": "<USERNAME>", + "username": "<username>", @@ -112 +109 @@ Now we have setup our user with MFA. - "username": "<USERNAME>", + "username": "<username>",