AWS AmazonElastiCache documentation change
Summary
Updated terminology from 'self-designed clusters' to 'node-based clusters' throughout the document. Changed references from 'cache cluster' to 'cluster' and adjusted link text for consistency.
Security assessment
The changes are purely terminological updates (self-designed → node-based) without altering security requirements or implementations. No evidence of addressing vulnerabilities or security incidents. The encryption enablement process and technical details remain unchanged.
Diff
diff --git a/AmazonElastiCache/latest/dg/in-transit-encryption.md b/AmazonElastiCache/latest/dg/in-transit-encryption.md index d33acb28e..c790280f7 100644 --- a//AmazonElastiCache/latest/dg/in-transit-encryption.md +++ b//AmazonElastiCache/latest/dg/in-transit-encryption.md @@ -11 +11 @@ To help keep your data secure, Amazon ElastiCache and Amazon EC2 provide mechani -All Valkey or Redis OSS serverless caches have in-transit encryption enabled. For self-designed clusters, you can enable in-transit encryption on a replication group by setting the parameter `TransitEncryptionEnabled` to `true` (CLI: `--transit-encryption-enabled`) when you create the replication group. You can do this whether you are creating the replication group using the AWS Management Console, the AWS CLI, or the ElastiCache API. +All Valkey or Redis OSS serverless caches have in-transit encryption enabled. For node-based clusters, you can enable in-transit encryption on a replication group by setting the parameter `TransitEncryptionEnabled` to `true` (CLI: `--transit-encryption-enabled`) when you create the replication group. You can do this whether you are creating the replication group using the AWS Management Console, the AWS CLI, or the ElastiCache API. @@ -13 +13 @@ All Valkey or Redis OSS serverless caches have in-transit encryption enabled. Fo -All serverless caches have in-transit encryption enabled. For self-designed clusters, you can enable in-transit encryption on a cache cluster by setting the parameter `TransitEncryptionEnabled` to `true` (CLI: `--transit-encryption-enabled`) when you create the cache cluster using the `CreateCacheCluster` (CLI: `create-cache-cluster`) operation. +All serverless caches have in-transit encryption enabled. For node-based clusters, you can enable in-transit encryption on a cluster by setting the parameter `TransitEncryptionEnabled` to `true` (CLI: `--transit-encryption-enabled`) when you create the cluster using the `CreateCacheCluster` (CLI: `create-cache-cluster`) operation. @@ -33 +33 @@ All serverless caches have in-transit encryption enabled. For self-designed clus - * [Enabling in-transit encryption on a self-designed Redis OSS Cluster using Python](./in-transit-encryption-enable-python.html) + * [Enabling in-transit encryption on a node-based Redis OSS cluster using Python](./in-transit-encryption-enable-python.html) @@ -65 +65 @@ ElastiCache in-transit encryption implements the following features: -The following constraints on Amazon ElastiCache in-transit encryption should be kept in mind when you plan your self-designed cluster implementation: +The following constraints on Amazon ElastiCache in-transit encryption should be kept in mind when you plan your node-based cluster implementation: @@ -88 +88 @@ For more information, see [Supported node types](./CacheNodes.SupportedTypes.htm -The following constraints on Amazon ElastiCache in-transit encryption should be kept in mind when you plan your self-designed cluster implementation: +The following constraints on Amazon ElastiCache in-transit encryption should be kept in mind when you plan your node-based cluster implementation: