AWS AmazonElastiCache documentation change
Summary
Changed 'self-designed cluster' to 'node-based cluster' in encryption configuration context
Security assessment
Terminology standardization. No changes to the actual security controls or documentation about encryption features - only cluster type naming was updated.
Diff
diff --git a/AmazonElastiCache/latest/dg/in-transit-encryption-enable.md b/AmazonElastiCache/latest/dg/in-transit-encryption-enable.md index 033e0d81c..227f149e8 100644 --- a//AmazonElastiCache/latest/dg/in-transit-encryption-enable.md +++ b//AmazonElastiCache/latest/dg/in-transit-encryption-enable.md @@ -9 +9 @@ Enabling in-transit encryption using the AWS Management ConsoleEnabling in-trans -All serverless caches have in-transit encryption enabled. On a self-designed cluster, you can enable in-transit encryption using the AWS Management Console, the AWS CLI, or the ElastiCache API. +All serverless caches have in-transit encryption enabled. On a node-based cluster, you can enable in-transit encryption using the AWS Management Console, the AWS CLI, or the ElastiCache API.