AWS kms documentation change
Summary
Updated AWS CLI version reference from '2.0' to 'v2' in message encoding instructions
Security assessment
This is a versioning clarification without security implications. The change does not introduce or modify security-related guidance.
Diff
diff --git a/kms/latest/developerguide/example_kms_Sign_section.md b/kms/latest/developerguide/example_kms_Sign_section.md index 4aaa9746f..d1cf7ecfa 100644 --- a//kms/latest/developerguide/example_kms_Sign_section.md +++ b//kms/latest/developerguide/example_kms_Sign_section.md @@ -28 +28 @@ You must specify a message to sign and a signing algorithm that your asymmetric -In AWS CLI 2.0, the value of the `message` parameter must be Base64-encoded. Or, you can save the message in a file and use the `fileb://` prefix, which tells the AWS CLI to read binary data from the file. +In AWS CLI v2, the value of the `message` parameter must be Base64-encoded. Or, you can save the message in a file and use the `fileb://` prefix, which tells the AWS CLI to read binary data from the file.