AWS AmazonElastiCache documentation change
Summary
Updated terminology from 'self-designed clusters' to 'node-based clusters' throughout the document to clarify cluster management types.
Security assessment
The changes are purely terminological (replacing 'self-designed' with 'node-based') and do not reference security vulnerabilities, mitigations, or new security features. The updates clarify cluster management types but do not address security risks or introduce security-related content.
Diff
diff --git a/AmazonElastiCache/latest/dg/VersionManagement.md b/AmazonElastiCache/latest/dg/VersionManagement.md index d15d3ea2e..2e0e31664 100644 --- a//AmazonElastiCache/latest/dg/VersionManagement.md +++ b//AmazonElastiCache/latest/dg/VersionManagement.md @@ -5 +5 @@ -Version management for ElastiCache Serverless CacheVersion management for self-designed ElastiCache clustersSupported versions +Version management for ElastiCache Serverless CacheVersion management for node-based ElastiCache clustersSupported versions @@ -9 +9 @@ Version management for ElastiCache Serverless CacheVersion management for self-d -Manage how you would like to update your ElastiCache caches and self-designed clusters updated for the Valkey, Memcached, and Redis OSS engines. +Manage how you would like to update your ElastiCache caches and node-based clusters updated for the Valkey, Memcached, and Redis OSS engines. @@ -19 +19 @@ When a new major version is available, ElastiCache Serverless will send you a no -## Version management for self-designed ElastiCache clusters +## Version management for node-based ElastiCache clusters @@ -21 +21 @@ When a new major version is available, ElastiCache Serverless will send you a no -When working with self-designed ElastiCache clusters, you can control when the software powering your cache cluster is upgraded to new versions that are supported by ElastiCache. You can control when to upgrade your cache to the latest available major, minor, and patch versions. You initiate engine version upgrades to your cluster or replication group by modifying it and specifying a new engine version. +When working with node-based ElastiCache clusters, you can control when the software powering your cluster is upgraded to new versions that are supported by ElastiCache. You can control when to upgrade your cache to the latest available major, minor, and patch versions. You initiate engine version upgrades to your cluster or replication group by modifying it and specifying a new engine version. @@ -23 +23 @@ When working with self-designed ElastiCache clusters, you can control when the s -You can control if and when the protocol-compliant software powering your cache cluster is upgraded to new versions that are supported by ElastiCache. This level of control enables you to maintain compatibility with specific versions, test new versions with your application before deploying in production, and perform version upgrades on your own terms and timelines. +You can control if and when the protocol-compliant software powering your cluster is upgraded to new versions that are supported by ElastiCache. This level of control enables you to maintain compatibility with specific versions, test new versions with your application before deploying in production, and perform version upgrades on your own terms and timelines. @@ -33 +33 @@ Because version upgrades might involve some compatibility risk, they don't occur - * ElastiCache for Redis OSS versions are identified with a semantic version which comprise a major and minor component. For example, in Redis OSS 6.2, the major version is 6, and the minor version 2. When operating self-designed clusters, ElastiCache for Redis OSS also exposes the patch component, e.g. Redis OSS 6.2.1, and the patch version is 1. + * ElastiCache for Redis OSS versions are identified with a semantic version which comprise a major and minor component. For example, in Redis OSS 6.2, the major version is 6, and the minor version 2. When operating node-based clusters, ElastiCache for Redis OSS also exposes the patch component, e.g. Redis OSS 6.2.1, and the patch version is 1. @@ -44 +44 @@ With Valkey and Redis OSS, you initiate engine version upgrades to your cluster -With Memcached, to upgrade to a newer version you must modify your cache cluster and specify the new engine version you want to use. Upgrading to a newer Memcached version is a destructive process – you lose your data and start with a cold cache. For more information, see [Modifying an ElastiCache cluster](./Clusters.Modify.html). +With Memcached, to upgrade to a newer version you must modify your cluster and specify the new engine version you want to use. Upgrading to a newer Memcached version is a destructive process – you lose your data and start with a cold cache. For more information, see [Modifying an ElastiCache cluster](./Clusters.Modify.html). @@ -63 +63 @@ ElastiCache serverless caches support ElastiCache version 7.2 for Valkey and abo -ElastiCache self-designed caches support ElastiCache version 7.2 for Valkey and above, ElastiCache version 1.4.5 for Memcached and above, and ElastiCache 4.0.10 for Redis OSS and above. +Node-based ElastiCache clusters support ElastiCache version 7.2 for Valkey and above, ElastiCache version 1.4.5 for Memcached and above, and ElastiCache 4.0.10 for Redis OSS and above. @@ -65 +65 @@ ElastiCache self-designed caches support ElastiCache version 7.2 for Valkey and -###### Self-designed ElastiCache clusters support the following Valkey versions: +###### Node-based ElastiCache clusters support the following Valkey versions: @@ -98 +98 @@ Supported Valkey versions below. Note that Valkey supports most features availab - 2. Use the backup to create and seed a Valkey or Redis OSS (cluster mode enabled) cluster with one shard (node group). Specify the new engine version and enable cluster mode when creating the cluster or replication group. For more information, see [Tutorial: Seeding a new self-designed cluster with an externally created backup](./backups-seeding-redis.html). + 2. Use the backup to create and seed a Valkey or Redis OSS (cluster mode enabled) cluster with one shard (node group). Specify the new engine version and enable cluster mode when creating the cluster or replication group. For more information, see [Tutorial: Seeding a new node-based cluster with an externally created backup](./backups-seeding-redis.html). @@ -102 +102 @@ Supported Valkey versions below. Note that Valkey supports most features availab - 4. Scale the new Valkey or Redis OSS (cluster mode enabled) cluster or replication group to the number of shards (node groups) that you need. For more information, see [Scaling clusters in Valkey or Redis OSS (Cluster Mode Enabled)](./scaling-redis-cluster-mode-enabled.html) + 4. Scale the new Valkey or Redis OSS (cluster mode enabled) cluster or replication group to the number of shards (node groups) that you need. For more information, see [Scaling Valkey or Redis OSS (Cluster Mode Enabled) clusters](./scaling-redis-cluster-mode-enabled.html) @@ -125 +125 @@ Clusters and replication groups with multiple shards are processed and patched a -When upgrading a self-designed Memcached cluster, consider the following. +When upgrading a node-based Memcached cluster, consider the following. @@ -174 +174 @@ Here are some of the new features introduced in Valkey 8.0 (compared to ElastiCa - * Newly-introduced per-slot metrics infrastructure for self-designed caches, providing detailed visibility into the performance and resource usage of individual slots. + * Newly-introduced per-slot metrics infrastructure for node-based clusters, providing detailed visibility into the performance and resource usage of individual slots.