AWS AmazonElastiCache documentation change
Summary
Changed 'self-designed' to 'node-based' in encryption documentation for clarity
Security assessment
The change clarifies terminology around cluster types but does not modify encryption implementation details or address security vulnerabilities. The existing encryption guidance remains functionally identical.
Diff
diff --git a/AmazonElastiCache/latest/dg/at-rest-encryption.md b/AmazonElastiCache/latest/dg/at-rest-encryption.md index 1d4b98f9c..cdca82d05 100644 --- a//AmazonElastiCache/latest/dg/at-rest-encryption.md +++ b//AmazonElastiCache/latest/dg/at-rest-encryption.md @@ -26 +26 @@ ElastiCache offers default (service managed) encryption at rest, as well as abil -Enabling At-Rest Encryption on an existing self-designed Valkey or Redis OSS cluster involves deleting your existing replication group, **after** running backup and restore on the replication group. +Enabling At-Rest Encryption on an existing node-based Valkey or Redis OSS cluster involves deleting your existing replication group, **after** running backup and restore on the replication group. @@ -136 +136 @@ All serverless caches have at-rest encryption enabled. -When creating a self-designed cluster, you can enable at-rest encryption by setting the parameter `AtRestEncryptionEnabled` to `true`. You can't enable at-rest encryption on existing replication groups. +When creating a node-based cluster, you can enable at-rest encryption by setting the parameter `AtRestEncryptionEnabled` to `true`. You can't enable at-rest encryption on existing replication groups.