AWS kendra documentation change
Summary
Removed details about requiring signed API requests with IAM access keys or AWS STS temporary credentials for authentication
Security assessment
The removed content described standard AWS authentication requirements rather than addressing a specific vulnerability. While authentication is security-related, there is no evidence this change fixes a disclosed security issue or weakness. The removal could be part of documentation reorganization rather than a security response.
Diff
diff --git a/kendra/latest/dg/infrastructure-security.md b/kendra/latest/dg/infrastructure-security.md index 1ae63ee70..99b06a7ce 100644 --- a//kendra/latest/dg/infrastructure-security.md +++ b//kendra/latest/dg/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Amazon Kendra through the network. Cli -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. -