AWS AmazonElastiCache: Distributed KV caching requires in-transit encryption
Summary
Documents that distributed KV caching clusters require TransitEncryptionMode=required and cannot disable it, and that BLOB.RDMA_* data travels over EFA encrypted by Nitro hardware rather than TLS.
Security assessment
The change documents a mandatory in-transit encryption requirement and clarifies the encryption mechanism (Nitro hardware encryption over EFA) for RDMA traffic, which is security-relevant guidance about protecting data in transit, but it does not remediate a specific vulnerability.
Evidence
+ * Distributed KV caching clusters require in-transit encryption with `TransitEncryptionMode` set to `required`. You can't turn off in-transit encryption or change this mode on these clusters. The data of `BLOB.RDMA_*` commands moves over Elastic Fabric Adapter (EFA), not TLS. The Nitro hardware encrypts this traffic for supported client instance types in the same VPC. For more information, see [Security in distributed KV caching](./distributed-kv-caching-security.html).
Diff
diff --git a/AmazonElastiCache/latest/dg/in-transit-encryption.md b/AmazonElastiCache/latest/dg/in-transit-encryption.md index 8efdb91..879911b 100644 --- a//AmazonElastiCache/latest/dg/in-transit-encryption.md +++ b//AmazonElastiCache/latest/dg/in-transit-encryption.md @@ -89,0 +90,2 @@ If your cluster runs an engine version that doesn't support this modification, t + + * Distributed KV caching clusters require in-transit encryption with `TransitEncryptionMode` set to `required`. You can't turn off in-transit encryption or change this mode on these clusters. The data of `BLOB.RDMA_*` commands moves over Elastic Fabric Adapter (EFA), not TLS. The Nitro hardware encrypts this traffic for supported client instance types in the same VPC. For more information, see [Security in distributed KV caching](./distributed-kv-caching-security.html).