AWS payment-cryptography documentation change
Summary
Corrected API reference link from ACM PCA to AWS Private CA documentation for the IssueCertificate operation.
Security assessment
Link correction improves documentation accuracy but doesn't address security vulnerabilities or introduce security features.
Diff
diff --git a/payment-cryptography/latest/userguide/keyexchange-byoca.md b/payment-cryptography/latest/userguide/keyexchange-byoca.md index 3f60cfb60..31abf5069 100644 --- a//payment-cryptography/latest/userguide/keyexchange-byoca.md +++ b//payment-cryptography/latest/userguide/keyexchange-byoca.md @@ -136 +136 @@ After generating the CSR, you need to have it signed by a Certificate Authority -To sign the CSR using AWS Private CA, first decode the base64-encoded CSR and save it to a file, then use the [IssueCertificate](https://docs.aws.amazon.com/acm-pca/latest/APIReference/API_IssueCertificate.html) API. +To sign the CSR using AWS Private CA, first decode the base64-encoded CSR and save it to a file, then use the [IssueCertificate](https://docs.aws.amazon.com/privateca/latest/APIReference/API_IssueCertificate.html) API.