AWS transcribe documentation change
Summary
Removed details about requiring signed API requests with IAM access keys or AWS STS temporary credentials
Security assessment
The removed lines described standard security practices (signing requests with IAM credentials or STS tokens) but their deletion does not indicate a resolved vulnerability. This appears to be a documentation simplification rather than a response to a specific security incident. However, removing this guidance could reduce clarity about secure API access requirements for users.
Diff
diff --git a/transcribe/latest/dg/infrastructure-security.md b/transcribe/latest/dg/infrastructure-security.md index 17765da15..231284c00 100644 --- a//transcribe/latest/dg/infrastructure-security.md +++ b//transcribe/latest/dg/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Amazon Transcribe through the network. -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. -