AWS athena documentation change
Summary
Removed mention of requiring signed requests using access keys or AWS STS
Security assessment
The removed line described standard AWS authentication practices but there's no evidence this change addresses a specific security vulnerability. It reduces documentation clarity about security practices but isn't tied to a disclosed issue.
Diff
diff --git a/athena/latest/ug/security-infrastructure.md b/athena/latest/ug/security-infrastructure.md index e2af689e3..04f439577 100644 --- a//athena/latest/ug/security-infrastructure.md +++ b//athena/latest/ug/security-infrastructure.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Athena through the network. Clients mu -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. -