AWS transcribe: Transcribe now supports customer-managed KMS keys for custom resources
Summary
A doc-history entry announces that Amazon Transcribe supports customer-managed KMS keys to encrypt artifacts associated with custom vocabularies, custom vocabulary filters, and custom language models, linking to the data-encryption page.
Security assessment
The change documents a new encryption capability (customer-managed KMS keys, i.e., CMEK) for Transcribe custom resource artifacts, a meaningful data-protection control; it is a feature announcement rather than a fix for a known vulnerability.
Evidence
+[Feature Update](https://docs.aws.amazon.com/transcribe/latest/dg/data-encryption.html#kms-resource-encryption)| Amazon Transcribe now supports customer-managed KMS keys to encrypt the artifacts associated with your custom vocabularies, custom vocabulary filters, and custom language models.| September 25, 2026
Diff
diff --git a/transcribe/latest/dg/doc-history.md b/transcribe/latest/dg/doc-history.md index 818939b..74493d8 100644 --- a//transcribe/latest/dg/doc-history.md +++ b//transcribe/latest/dg/doc-history.md @@ -17,0 +18 @@ Change| Description| Date +[Feature Update](https://docs.aws.amazon.com/transcribe/latest/dg/data-encryption.html#kms-resource-encryption)| Amazon Transcribe now supports customer-managed KMS keys to encrypt the artifacts associated with your custom vocabularies, custom vocabulary filters, and custom language models.| September 25, 2026