AWS proton documentation change
Summary
Removed details about requiring access keys/secret keys and AWS STS for request signing
Security assessment
The removed content described standard AWS security practices (IAM credentials and STS) but did not indicate a vulnerability being fixed. This appears to be a documentation simplification rather than a response to a specific security issue. However, removing security-relevant documentation could reduce clarity about secure access methods.
Diff
diff --git a/proton/latest/userguide/infrastructure-security.md b/proton/latest/userguide/infrastructure-security.md index bac7bc6ce..9308b382e 100644 --- a//proton/latest/userguide/infrastructure-security.md +++ b//proton/latest/userguide/infrastructure-security.md @@ -22,2 +21,0 @@ You use AWS published API calls to access AWS Proton through the network. Client -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. -