AWS Security ChangesHomeSearch

AWS cloudhsm documentation change

Service: cloudhsm · 2025-03-30 · Documentation low

File: cloudhsm/latest/userguide/login-mfa-cloudhsm-cli.md

Summary

Updated command syntax with angle brackets for parameters and fixed file reference formatting

Security assessment

Syntax standardization without evidence of security fixes

Diff

diff --git a/cloudhsm/latest/userguide/login-mfa-cloudhsm-cli.md b/cloudhsm/latest/userguide/login-mfa-cloudhsm-cli.md
index c38c3caea..b782bba53 100644
--- a/cloudhsm/latest/userguide/login-mfa-cloudhsm-cli.md
+++ b/cloudhsm/latest/userguide/login-mfa-cloudhsm-cli.md
@@ -11 +11 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-        aws-cloudhsm > login --username <USERNAME> --role <ROLE> mfa-token-sign --token unsigned-tokens.json 
+        aws-cloudhsm > login --username <username> --role <role> mfa-token-sign --token <unsigned-tokens.json>
@@ -16 +16 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-        aws-cloudhsm > login --username <USERNAME> --role <ROLE> mfa-token-sign --token unsigned-tokens.json
+        aws-cloudhsm > login --username <username> --role <role> mfa-token-sign --token <unsigned-tokens.json>
@@ -20 +20 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-  3. While prompted to enter the signed token file path, you can inspect the unsigned token file in a separate terminal. Identify the file with unsigned tokens that need to be signed: `unsigned-tokens.json`. The number of tokens in this file depends on the number of HSMs in your cluster. Each token represents one HSM. This file is JSON formatted and contains tokens that need to be signed to prove you have a private key.
+  3. While prompted to enter the signed token file path, you can inspect the unsigned token file in a separate terminal. Identify the file with unsigned tokens that need to be signed: ``<unsigned-tokens.json>``. The number of tokens in this file depends on the number of HSMs in your cluster. Each token represents one HSM. This file is JSON formatted and contains tokens that need to be signed to prove you have a private key.
@@ -22 +22 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-        $ cat unsigned-tokens.json
+        $ cat <unsigned-tokens.json>
@@ -99 +99 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-        aws-cloudhsm > login --username <USERNAME> --role <ROLE> mfa-token-sign --token unsigned-tokens.json
+        aws-cloudhsm > login --username <username> --role <role> mfa-token-sign --token <unsigned-tokens.json>
@@ -105,2 +105,2 @@ Follow these steps to log in AWS CloudHSM users with multi-factor authentication
-        "username": "<USERNAME>",
-        "role": "<ROLE>"
+        "username": "<username>",
+        "role": "<role>"