AWS codepipeline high security documentation change
Summary
Removed documentation about request signing requirements using access keys or AWS STS
Security assessment
Deleting authentication details (access keys/STS) weakens documentation about securing API access. This could lead to insecure implementations if users are unaware of signing requirements, increasing risk of unauthorized access.
Diff
diff --git a/codepipeline/latest/userguide/infrastructure-security.md b/codepipeline/latest/userguide/infrastructure-security.md index c17fbee75..2d333b98f 100644 --- a//codepipeline/latest/userguide/infrastructure-security.md +++ b//codepipeline/latest/userguide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access CodePipeline through the network. Clie -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. -