AWS AmazonElastiCache documentation change
Summary
Updated serverless cache configuration limits including data size, ECPU metrics, and request arguments constraints
Security assessment
Changes document operational limits and constraints without any security context. The updates appear to be service capability documentation rather than security-related content.
Diff
diff --git a/AmazonElastiCache/latest/dg/RedisConfiguration.md b/AmazonElastiCache/latest/dg/RedisConfiguration.md index 9a6f392a6..ddb2cb044 100644 --- a//AmazonElastiCache/latest/dg/RedisConfiguration.md +++ b//AmazonElastiCache/latest/dg/RedisConfiguration.md @@ -35,0 +36,5 @@ Name | Details | Description +Size per cache | 5,000 GiB | Maximum amount of data that can be stored per serverless cache. +Size per slot | 32 GiB | The maximum size of a single Valkey or Redis OSS hash slot. Clients trying to set more data than this on a single Valkey or Redis OSS slot will trigger the eviction policy on the slot, and if no keys are evictable, will receive an out of memory (`OOM`) error. +ECPU per cache | 15,000,000 ECPU/second | ElastiCache Processing Units (ECPU) metric. The number of ECPUs consumed by your requests depends on the vCPU time taken and the amount of data transferred. +ECPU per slot | 30K - 90K ECPU/second | Maximum of 30K ECPUs/second per slot or 90K ECPUs/second when using Read from Replica using READONLY connections. +Arguments per Request | 3,999 | Maximum number of arguments per request. Clients sending more arguments per request will receive an error. @@ -38 +42,0 @@ Lua script size | 4 MiB | The maximum size of a single Valkey or Redis OSS Lua s -Slot size | 32 GiB | The maximum size of a single Valkey or Redis OSS hash slot. Clients trying to set more data than this on a single Valkey or Redis OSS slot will trigger the eviction policy on the slot, and if no keys are evictable, will receive an out of memory (`OOM`) error.