AWS payment-cryptography documentation change
Summary
Removed explanation about alias flexibility and code maintenance benefits
Security assessment
This is a content reduction removing non-security-related information about alias management. No security implications are present as the change doesn't alter security guidance or address vulnerabilities.
Diff
diff --git a/payment-cryptography/latest/userguide/keys-managealias.md b/payment-cryptography/latest/userguide/keys-managealias.md index 0c0ea4f91..77c993197 100644 --- a//payment-cryptography/latest/userguide/keys-managealias.md +++ b//payment-cryptography/latest/userguide/keys-managealias.md @@ -17,2 +16,0 @@ You can also allow and deny access to AWS Payment Cryptography key based on thei -Much of the power of aliases comes from your ability to change the key associated with an alias at any time. Aliases can make your code easier to write and maintain. For example, suppose you use an alias to refer to a particular AWS Payment Cryptography key and you want to change the AWS Payment Cryptography key. In that case, just associate the alias with a different key. You don't need to change your code or application configuration. -