AWS privateca documentation change
Summary
Removed sentence about access key signing requirements and AWS STS temporary credentials from API access section.
Security assessment
Removal of general authentication process description doesn't indicate a security fix. This appears to be documentation simplification rather than addressing a vulnerability.
Diff
diff --git a/privateca/latest/userguide/infrastructure-security.md b/privateca/latest/userguide/infrastructure-security.md index f90bf1ab6..1a2ad310b 100644 --- a//privateca/latest/userguide/infrastructure-security.md +++ b//privateca/latest/userguide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access AWS Private CA through the network. Cl -Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html) (AWS STS) to generate temporary security credentials to sign requests. -