> ## Documentation Index > Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt > Use this file to discover all available pages before exploring further. # ElastiCache (Valkey/Redis) > ElastiCache (Valkey/Redis) APIs with Cloud Adapter. This page describes how ElastiCache (Valkey/Redis) maps to services in the environment where the application runs. Some profiles adapt origin API calls; others translate infrastructure or document target-native behavior. ## Supported environments | Environment | Mapping | | ------------------ | -------------- | | Akamai | Infrastructure | | Azure | Infrastructure | | Google Cloud | Infrastructure | | Private Kubernetes | Infrastructure | | Scaleway | Infrastructure | API means the profile adapts origin API behavior. Infrastructure means the profile changes provisioned resources or documents a target-native alternative without promising an origin API endpoint. Check the operation and capability tables for the behavior your application depends on. ## How the targets compare Each row compares a capability of ElastiCache (Valkey/Redis) with its adaptation on each target. A dash means this profile does not state the capability for that target. ### Cloud Adapter | Capability | ElastiCache (Valkey/Redis) | Akamai, Private Kubernetes, and Scaleway · Bitnami Valkey | Azure | Google Cloud | Scaleway · Scaleway Managed Database for Redis | | ---------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------- | | Redis wire protocol | Valkey (RESP2; RESP3 after HELLO) | native; clients unchanged | native; clients unchanged | native; clients unchanged | - | | Engine + version | Valkey 7.2 to 9.1, the version you pick | Valkey, the same engine (chart image 8.1.3; set the tag to match) | Redis Enterprise 7.4 (Azure Managed Redis) | Redis 7.2 (classic instance) | - | | Durability / HA owner · who operates the cache | AWS-managed | you (self-managed on the target cluster) | Microsoft (Azure Managed Redis) | Google (Memorystore) | - | | Sizing model · what you pick to buy capacity | a node type per node (r7g / m7g families; r6gd with data tiering) | pod memory limit + CPU request from the node type; PVC size | SKU (Balanced / Memory / Compute / Flash Optimized) + memory size; no scale-down | tier (Basic / Standard) + memory size, up to 300 GB | - | | Cluster mode / sharding | cluster mode on or off; up to 500 shards | primary with replicas by default; Valkey Cluster is your setup | OSS, Enterprise or Non-clustered (25 GB or less) policy; shard count is the SKU's | one primary shard; Memorystore for Redis Cluster for sharding | - | | Replication / HA · read replicas + failover | up to 5 replicas per shard, Multi-AZ automatic failover, 99.99% SLA | replica count + Sentinel from the origin settings; no SLA | HA by default: replica shards on a second node, zone-distributed, auto-failover | Standard: cross-zone replica + auto-failover, 1 to 5 read replicas, 99.9% SLA | - | | Persistence | daily RDB snapshots, plus the Multi-AZ durability log on Valkey 9.0+ | RDB + AOF on a PersistentVolume | optional RDB or AOF to a managed disk | RDB snapshots every 1 to 24 hours; no AOF | - | | Encryption in transit | Yes | Partial - follows the origin setting; cert-manager issued; off when off on the origin | Yes - TLS 1.2 minimum on every tier; follows the origin setting | Yes - TLS 1.2+ when enabled on the instance; follows the origin setting | - | | Encryption at rest | AWS-managed key or your own KMS key | the storage class's and node disks' | platform key by default; CMK via Key Vault on every tier | CMEK at create (covers snapshots and backups) | - | | AUTH / ACL / RBAC | AUTH token, RBAC user groups, or IAM authentication | password AUTH (Kubernetes secret); ACL users via config; no IAM | Entra ID (default) or access keys; control-plane ACLs | one AUTH string; no ACL users, no IAM | - | | Eviction (maxmemory-policy) | all 8 policies via the parameter group; default volatile-lru | all 8 policies via chart config; engine default noeviction, set it | all 8 policies via the eviction setting; RediSearch needs noeviction | all 8 policies via configuration flags; default volatile-lru | - | | JSON / Bloom / search | JSON; Bloom on 8.1+; vector search on 8.2+; full-text search on 9.0+ | none bundled; build valkey-json / bloom / search into the image | RediSearch + JSON + Bloom + TimeSeries built in (JSON only on Flash Optimized) | none on the classic instance; Memorystore for Valkey for JSON / Bloom / search | - | | API coverage | full | high | high | high | high | ## On Akamai, Private Kubernetes, and Scaleway ### Bitnami Valkey | Operation | Area | Support | Depth | Notes | | --------------------------------------------------------------------------------------- | ------------------- | ------------ | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BITCOUNT | Bitmaps | Supported | Full surface | - | | BITFIELD | Bitmaps | Supported | Full surface | arbitrary-width integer ops | | BITFIELD\_RO | Bitmaps | Supported | Full surface | read-only BITFIELD | | BITOP | Bitmaps | Supported | Full surface | bitwise AND/OR/XOR/NOT | | BITPOS | Bitmaps | Supported | Full surface | first set/clear bit | | GETBIT | Bitmaps | Supported | Full surface | - | | SETBIT | Bitmaps | Supported | Full surface | - | | Backup / snapshot / restore | Durability | Partial | Most usage | a manual SAVE / BGSAVE and a copy of dump.rdb off the PersistentVolume, or a volume snapshot from your storage class; there is no scheduled snapshot window unless you add one | | Persistence (RDB / AOF) | Durability | Supported | Most usage | RDB snapshots and AOF on a PersistentVolume sized from your replication group; the Valkey 9.0 Multi-AZ durability log has no analog, so durability is AOF's fsync policy plus your storage class | | Search / JSON / modules (FT.\* / JSON.\*) | Extensions | Out of scope | Full surface | core Valkey types only; the chart's image bundles no modules, so JSON, Bloom and FT.\* search calls from a Valkey 8.1+ replication group return an unknown-command error unless you build valkey-json, valkey-bloom and valkey-search into the image and load them | | GEOADD | Geo | Supported | Full surface | - | | GEODIST | Geo | Supported | Full surface | - | | GEOHASH | Geo | Supported | Full surface | geohash strings | | GEOPOS | Geo | Supported | Full surface | member coordinates | | GEORADIUS | Geo | Supported | Full surface | deprecated radius query (use GEOSEARCH) | | GEORADIUSBYMEMBER | Geo | Supported | Full surface | deprecated radius-by-member (use GEOSEARCH) | | GEORADIUSBYMEMBER\_RO | Geo | Supported | Full surface | read-only deprecated radius-by-member | | GEORADIUS\_RO | Geo | Supported | Full surface | read-only deprecated radius query | | GEOSEARCH | Geo | Supported | Full surface | - | | GEOSEARCHSTORE | Geo | Supported | Full surface | search + store result | | HDEL | Hashes | Supported | Common | - | | HEXISTS | Hashes | Supported | Most usage | - | | HEXPIRE | Hashes | Partial | Most usage | per-field TTL (seconds); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HEXPIREAT | Hashes | Partial | Most usage | per-field expiry at unix time; a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HEXPIRETIME | Hashes | Partial | Full surface | absolute per-field expiry (s); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HGET | Hashes | Supported | Common | - | | HGETALL | Hashes | Supported | Common | - | | HGETDEL | Hashes | Partial | Most usage | get and delete field(s); a Valkey 9.1 command, served once the chart's image is set to Valkey 9.1 or later (the chart ships 8.1.3) | | HGETEX | Hashes | Partial | Most usage | get field(s) and set or refresh their expiry; a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HINCRBY | Hashes | Supported | Most usage | - | | HINCRBYFLOAT | Hashes | Supported | Most usage | - | | HKEYS | Hashes | Supported | Most usage | - | | HLEN | Hashes | Supported | Most usage | - | | HMGET | Hashes | Supported | Common | - | | HMSET | Hashes | Supported | Full surface | deprecated alias of HSET | | HPERSIST | Hashes | Partial | Most usage | remove a field's TTL; a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HPEXPIRE | Hashes | Partial | Most usage | per-field TTL (ms); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HPEXPIREAT | Hashes | Partial | Most usage | per-field expiry at ms unix time; a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HPEXPIRETIME | Hashes | Partial | Full surface | absolute per-field expiry (ms); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HPTTL | Hashes | Partial | Most usage | remaining per-field TTL (ms); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HRANDFIELD | Hashes | Supported | Full surface | - | | HSET | Hashes | Supported | Common | - | | HSETEX | Hashes | Partial | Most usage | set field(s) with expiry; a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HSETNX | Hashes | Supported | Most usage | set field if not exists | | HSTRLEN | Hashes | Supported | Full surface | - | | HTTL | Hashes | Partial | Most usage | remaining per-field TTL (s); a Valkey 9.0 command, served once the chart's image is set to Valkey 9.0 or later (the chart ships 8.1.3) | | HVALS | Hashes | Supported | Most usage | - | | PFADD | HyperLogLog | Supported | Full surface | - | | PFCOUNT | HyperLogLog | Supported | Full surface | - | | PFMERGE | HyperLogLog | Supported | Full surface | - | | CLUSTERSCAN | Keys & TTL | Partial | Full surface | cluster-wide key scan across every node (Valkey 9.1); served once the chart's image is set to a Valkey release that has it (the chart ships 8.1.3) | | COPY | Keys & TTL | Supported | Full surface | copy key | | DEL | Keys & TTL | Supported | Common | - | | DELIFEQ | Keys & TTL | Partial | Full surface | delete a key only if its value matches (Valkey 9.0); served once the chart's image is set to a Valkey release that has it (the chart ships 8.1.3) | | DUMP | Keys & TTL | Supported | Full surface | - | | EXISTS | Keys & TTL | Supported | Common | - | | EXPIRE | Keys & TTL | Supported | Common | - | | EXPIREAT | Keys & TTL | Supported | Most usage | expire at unix time | | EXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (s) | | HSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | KEYS | Keys & TTL | Supported | Common | - | | OBJECT | Keys & TTL | Supported | Full surface | ENCODING / IDLETIME / REFCOUNT | | PERSIST | Keys & TTL | Supported | Common | - | | PEXPIRE | Keys & TTL | Supported | Common | - | | PEXPIREAT | Keys & TTL | Supported | Most usage | expire at ms unix time | | PEXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (ms) | | PTTL | Keys & TTL | Supported | Most usage | ms TTL | | RANDOMKEY | Keys & TTL | Supported | Full surface | - | | RENAME | Keys & TTL | Supported | Common | - | | RENAMENX | Keys & TTL | Supported | Most usage | rename if target absent | | RESTORE | Keys & TTL | Supported | Full surface | - | | SCAN | Keys & TTL | Supported | Most usage | cursor iteration | | SORT | Keys & TTL | Supported | Full surface | sort list/set/zset | | SORT\_RO | Keys & TTL | Supported | Full surface | read-only SORT (replica-safe) | | SSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | TOUCH | Keys & TTL | Supported | Full surface | bump last-access | | TTL | Keys & TTL | Supported | Common | - | | TYPE | Keys & TTL | Supported | Common | - | | UNLINK | Keys & TTL | Supported | Most usage | async delete | | WAIT | Keys & TTL | Supported | Full surface | block until N replicas acknowledge | | WAITAOF | Keys & TTL | Supported | Full surface | block until AOF fsync, with AOF enabled in the chart's configuration | | ZSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | BLMOVE | Lists | Supported | Full surface | blocking move | | BLMPOP | Lists | Supported | Full surface | blocking multi-list pop | | BLPOP | Lists | Supported | Most usage | blocking pop | | BRPOP | Lists | Supported | Most usage | blocking pop | | BRPOPLPUSH | Lists | Supported | Full surface | blocking legacy move | | LINDEX | Lists | Supported | Most usage | - | | LINSERT | Lists | Supported | Most usage | insert before/after pivot | | LLEN | Lists | Supported | Most usage | - | | LMOVE | Lists | Supported | Full surface | atomic move between lists | | LMPOP | Lists | Supported | Full surface | multi-list pop | | LPOP | Lists | Supported | Common | - | | LPOS | Lists | Supported | Full surface | index of matching element | | LPUSH | Lists | Supported | Common | - | | LPUSHX | Lists | Supported | Full surface | push only if list exists | | LRANGE | Lists | Supported | Most usage | - | | LREM | Lists | Supported | Most usage | - | | LSET | Lists | Supported | Most usage | set by index | | LTRIM | Lists | Supported | Most usage | - | | RPOP | Lists | Supported | Common | - | | RPOPLPUSH | Lists | Supported | Most usage | legacy atomic move | | RPUSH | Lists | Supported | Common | - | | RPUSHX | Lists | Supported | Full surface | push only if list exists | | Eviction (maxmemory-policy) | Memory | Supported | Most usage | the full maxmemory-policy family through the chart's configuration; set it explicitly, because the engine's default is noeviction while ElastiCache's parameter group defaults to volatile-lru | | Replication / HA / failover | Operations | Partial | Most usage | your replication group's replica count maps to the chart (one replica pod per ElastiCache replica) and its automatic-failover setting enables Sentinel; there is no vendor SLA, and failover time is Sentinel's quorum and down-after-milliseconds settings, which you tune | | PSUBSCRIBE | Pub/Sub | Supported | Most usage | - | | PUBLISH | Pub/Sub | Supported | Most usage | - | | PUBSUB | Pub/Sub | Supported | Most usage | introspect pub/sub state | | PUNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from patterns | | SPUBLISH | Pub/Sub | Partial | Full surface | sharded pub/sub publish; the chart deploys a primary with replicas, so this is plain pub/sub unless you enable Valkey Cluster | | SSUBSCRIBE | Pub/Sub | Partial | Full surface | sharded pub/sub subscribe; the chart deploys a primary with replicas, so this is plain pub/sub unless you enable Valkey Cluster | | SUBSCRIBE | Pub/Sub | Supported | Most usage | - | | SUNSUBSCRIBE | Pub/Sub | Partial | Full surface | sharded pub/sub unsubscribe; the chart deploys a primary with replicas, so this is plain pub/sub unless you enable Valkey Cluster | | UNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from channels | | Admin / config / replication commands (CONFIG / DEBUG / SAVE / SLAVEOF / CLUSTER admin) | Restricted admin | Out of scope | Full surface | self-hosted, so nothing is restricted: CONFIG, DEBUG, SAVE, REPLICAOF and CLUSTER admin all run, because you operate the server and its consequences are yours | | EVAL | Scripting | Supported | Most usage | server-side Lua | | EVALSHA | Scripting | Supported | Most usage | - | | EVALSHA\_RO | Scripting | Supported | Most usage | read-only EVALSHA | | EVAL\_RO | Scripting | Supported | Most usage | read-only EVAL (replica-safe) | | SCRIPT | Scripting | Supported | Most usage | - | | AUTH / ACL / RBAC | Security | Partial | Most usage | password AUTH is on by default, with the password held in a Kubernetes secret; Valkey ACL users are engine configuration you add, and IAM authentication has no analog | | Encryption at rest | Security | Partial | Most usage | the engine has no at-rest encryption of its own; the PersistentVolume's storage class and the node disks provide it, which is your cluster's setting | | Encryption in transit (TLS) | Security | Partial | Common | your replication group's in-transit setting turns on TLS with a cert-manager issued certificate; when it is off on the origin it is off here | | AUTH | Server & connection | Supported | Common | authenticate the connection | | ECHO | Server & connection | Supported | Common | - | | HELLO | Server & connection | Supported | Common | RESP3 handshake + AUTH/SETNAME | | INFO | Server & connection | Supported | Common | - | | PING | Server & connection | Supported | Common | - | | QUIT | Server & connection | Supported | Full surface | close the connection (deprecated) | | RESET | Server & connection | Supported | Full surface | reset connection state | | SELECT | Server & connection | Supported | Common | logical database select; multiple databases on the chart's primary-replica deployment, database 0 only if you enable Valkey Cluster | | SADD | Sets | Supported | Common | - | | SCARD | Sets | Supported | Common | - | | SDIFF | Sets | Supported | Most usage | + SDIFFSTORE | | SDIFFSTORE | Sets | Supported | Most usage | store difference | | SINTER | Sets | Supported | Most usage | + SINTERSTORE | | SINTERCARD | Sets | Supported | Full surface | intersection cardinality | | SINTERSTORE | Sets | Supported | Most usage | store intersection | | SISMEMBER | Sets | Supported | Common | - | | SMEMBERS | Sets | Supported | Common | - | | SMISMEMBER | Sets | Supported | Full surface | multi-membership test | | SMOVE | Sets | Supported | Full surface | atomic move between sets | | SPOP | Sets | Supported | Most usage | pop random member(s) | | SRANDMEMBER | Sets | Supported | Most usage | random member(s) | | SREM | Sets | Supported | Common | - | | SUNION | Sets | Supported | Most usage | + SUNIONSTORE | | SUNIONSTORE | Sets | Supported | Most usage | store union | | Serverless / auto-scaling | Sizing | Out of scope | Most usage | this is the provisioned origin, so there is no serverless surface to carry | | BZMPOP | Sorted sets | Supported | Full surface | blocking multi-key pop | | BZPOPMAX | Sorted sets | Supported | Full surface | blocking pop highest | | BZPOPMIN | Sorted sets | Supported | Full surface | blocking pop lowest | | ZADD | Sorted sets | Supported | Common | - | | ZCARD | Sorted sets | Supported | Common | - | | ZCOUNT | Sorted sets | Supported | Most usage | count in score range | | ZDIFF | Sorted sets | Supported | Full surface | + ZDIFFSTORE | | ZDIFFSTORE | Sorted sets | Supported | Most usage | store difference | | ZINCRBY | Sorted sets | Supported | Most usage | - | | ZINTER | Sorted sets | Supported | Full surface | + ZINTERSTORE / ZINTERCARD | | ZINTERCARD | Sorted sets | Supported | Full surface | intersection cardinality | | ZINTERSTORE | Sorted sets | Supported | Most usage | store intersection | | ZLEXCOUNT | Sorted sets | Supported | Full surface | count in lex range | | ZMPOP | Sorted sets | Supported | Full surface | multi-key pop | | ZMSCORE | Sorted sets | Supported | Full surface | multi-member scores | | ZPOPMAX | Sorted sets | Supported | Most usage | pop highest score | | ZPOPMIN | Sorted sets | Supported | Most usage | pop lowest score | | ZRANDMEMBER | Sorted sets | Supported | Full surface | random member(s) | | ZRANGE | Sorted sets | Supported | Most usage | - | | ZRANGEBYLEX | Sorted sets | Supported | Full surface | lexicographic range | | ZRANGEBYSCORE | Sorted sets | Supported | Most usage | - | | ZRANGESTORE | Sorted sets | Supported | Full surface | store a range result | | ZRANK | Sorted sets | Supported | Most usage | - | | ZREM | Sorted sets | Supported | Common | - | | ZREMRANGEBYLEX | Sorted sets | Supported | Full surface | remove by lex range | | ZREMRANGEBYRANK | Sorted sets | Supported | Full surface | remove by rank range | | ZREMRANGEBYSCORE | Sorted sets | Supported | Full surface | remove by score range | | ZREVRANGE | Sorted sets | Supported | Most usage | descending range | | ZREVRANGEBYLEX | Sorted sets | Supported | Full surface | descending lex range | | ZREVRANGEBYSCORE | Sorted sets | Supported | Most usage | descending range by score | | ZREVRANK | Sorted sets | Supported | Most usage | descending rank | | ZSCORE | Sorted sets | Supported | Common | - | | ZUNION | Sorted sets | Supported | Full surface | + ZUNIONSTORE | | ZUNIONSTORE | Sorted sets | Supported | Most usage | store union | | XACK | Streams | Supported | Full surface | - | | XADD | Streams | Supported | Full surface | - | | XAUTOCLAIM | Streams | Supported | Full surface | auto-claim idle pending | | XCLAIM | Streams | Supported | Full surface | claim pending messages | | XDEL | Streams | Supported | Full surface | delete entries | | XGROUP | Streams | Supported | Full surface | consumer-group create/destroy/setid | | XINFO | Streams | Supported | Full surface | stream/groups/consumers introspection | | XLEN | Streams | Supported | Full surface | - | | XPENDING | Streams | Supported | Full surface | pending-entries summary | | XRANGE | Streams | Supported | Full surface | - | | XREAD | Streams | Supported | Full surface | - | | XREADGROUP | Streams | Supported | Full surface | consumer-group read | | XREVRANGE | Streams | Supported | Full surface | reverse range | | XSETID | Streams | Supported | Full surface | set last-id | | XTRIM | Streams | Supported | Full surface | trim to maxlen/minid | | APPEND | Strings | Supported | Most usage | - | | DECR | Strings | Supported | Common | - | | DECRBY | Strings | Supported | Most usage | - | | GET | Strings | Supported | Common | - | | GETDEL | Strings | Supported | Most usage | get and delete | | GETEX | Strings | Supported | Most usage | get and set expiry | | GETRANGE | Strings | Supported | Most usage | - | | GETSET | Strings | Supported | Common | - | | INCR | Strings | Supported | Common | - | | INCRBY | Strings | Supported | Common | - | | INCRBYFLOAT | Strings | Supported | Most usage | - | | LCS | Strings | Supported | Full surface | longest common subsequence | | MGET | Strings | Supported | Common | - | | MSET | Strings | Supported | Common | - | | MSETEX | Strings | Partial | Full surface | set several keys with one shared expiry (Valkey 9.1); served once the chart's image is set to a Valkey release that has it (the chart ships 8.1.3) | | MSETNX | Strings | Supported | Most usage | multi-set if none exist | | PSETEX | Strings | Supported | Most usage | set with ms expiry | | SET | Strings | Supported | Common | - | | SETEX | Strings | Supported | Common | set with expiry | | SETNX | Strings | Supported | Common | set if not exists | | SETRANGE | Strings | Supported | Most usage | - | | STRLEN | Strings | Supported | Most usage | - | | SUBSTR | Strings | Supported | Full surface | deprecated alias of GETRANGE | | Cluster mode (slot topology) | Topology | Partial | Most usage | the chart deploys a primary with replicas rather than Valkey Cluster; the engine supports Cluster sharding and enabling it is your setup, so a cluster-mode-enabled replication group lands on one primary sized for the whole keyspace unless you configure Cluster deliberately | | DISCARD | Transactions | Supported | Most usage | - | | EXEC | Transactions | Supported | Most usage | - | | MULTI | Transactions | Supported | Most usage | - | | UNWATCH | Transactions | Supported | Most usage | forget all WATCHed keys | | WATCH | Transactions | Supported | Most usage | optimistic lock | #### How it works On AWS your cache is a provisioned **Valkey** replication group: a node type you chose, one or more shards, up to five replicas per shard and Multi-AZ failover, reached over the Redis wire protocol (RESP). On the target cluster the same application runs against a **Valkey** deployment from the Bitnami Helm chart, the same engine ElastiCache runs (the chart ships Valkey 8.1.3), and the Redis client connects to the deployment's in-cluster service over the same wire. No adapter sits between the client and the cache. The deployment takes its shape from the replication group: the node type sets the pod's memory and CPU, the replica count becomes one replica pod per ElastiCache replica, automatic failover enables Sentinel, in-transit encryption enables TLS with a cert-manager certificate, and password AUTH is on with the password held in a Kubernetes secret. The ElastiCache management calls an application makes to locate its cache still work: `DescribeReplicationGroups` and `DescribeCacheClusters` are answered by the Tensor9 service adapter from the deployment's service names, port 6379 and status. A runtime `CreateReplicationGroup`, `ModifyReplicationGroup` or `DeleteReplicationGroup` from the application is refused with an ElastiCache error. * **The same engine:** the data plane runs on Valkey itself, so commands, data structures, eviction and the Valkey-specific additions behave as they did, at whichever engine version the chart's image is set to. * **Your settings follow you:** node type, replica count, automatic failover and in-transit encryption on the replication group become pod resources, replica pods, Sentinel and TLS on the chart. * **Endpoint discovery through the AWS SDK is answered in-cluster.** `DescribeReplicationGroups` returns the in-cluster primary and replica service names on port 6379; an application that reads its endpoint from configuration never makes the call. #### Limitations The engine is the same, so the divergences are operational: what AWS ran for you, you now configure and run, and three defaults differ from ElastiCache's. △ Where a Valkey replication group and self-hosted Valkey diverge * **No managed SLA:** availability and durability are bounded by how the cluster is run. Sentinel elects a new primary when the old one fails, with a failover time set by its quorum and down-after-milliseconds settings rather than ElastiCache's Multi-AZ promotion, and there is no 99.99% commitment behind it. * **The engine version is the image tag:** the chart ships Valkey 8.1.3. A replication group on 9.0 or 9.1 that uses hash-field TTL, `DELIFEQ`, `MSETEX` or `CLUSTERSCAN` gets an unknown-command error until the image is set to the matching release; set it before cutover, and upgrades from then on are yours. * **Modules are not bundled.** JSON, Bloom and `FT.*` search are separate Valkey modules that the chart's image does not include; an application that used them on ElastiCache gets an unknown-command error unless you build the modules into the image and load them. * **Primary-replica by default, and noeviction by default:** the chart deploys a primary with replicas rather than Valkey Cluster, so a cluster-mode-enabled replication group's keyspace lands on one primary unless you configure Cluster; and the engine's default eviction policy is noeviction where ElastiCache's parameter group defaults to volatile-lru, so a cache that filled up and evicted on AWS returns out-of-memory errors on writes here until you set the policy. #### Other considerations What remains is the operating work a managed service did for you: sizing, durability, encryption, access and the open admin surface. * **Sizing:** the node type becomes the primary pod's memory limit and CPU request, and the PersistentVolume size bounds what a snapshot or AOF can hold; there is no larger node to move to without editing the release, and no headroom beyond the pod's limit. Read replicas scale with a replica HPA if you enable it; the primary does not autoscale. * **Durability.** RDB snapshots and AOF write to the PersistentVolume; surviving a node loss depends on the storage class's replication plus AOF's fsync policy, and the Valkey 9.0 Multi-AZ durability log has no analog. A volume snapshot from your storage class is the scheduled-backup equivalent. * **Encryption.** TLS follows the replication group's in-transit setting and is issued by cert-manager; at-rest encryption is whatever the storage class and node disks provide, since the engine encrypts nothing itself. * **Access:** password AUTH is on, with the password in a Kubernetes secret; Valkey ACL users are engine configuration you add, and IAM authentication has no analog, so an IAM-authenticated client switches to the password or an ACL user. * **The admin surface is open.** `CONFIG`, `SAVE`, `REPLICAOF` and `CLUSTER` admin all run, because you operate the server; an application that could not issue them on ElastiCache gains nothing from this, and an operator gains the whole toolset and its consequences. * **Data migration:** most caches re-warm. A replication group that holds durable data exports an RDB to S3 and seeds the deployment with it as dump.rdb on the primary's PersistentVolume before first start. ## On Azure ### Azure Managed Redis | Operation | Area | Support | Depth | Notes | | --------------------------------------------------------------------------------------- | ------------------- | ------------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BITCOUNT | Bitmaps | Supported | Full surface | - | | BITFIELD | Bitmaps | Supported | Full surface | arbitrary-width integer ops | | BITFIELD\_RO | Bitmaps | Supported | Full surface | read-only BITFIELD | | BITOP | Bitmaps | Supported | Full surface | bitwise AND/OR/XOR/NOT | | BITPOS | Bitmaps | Supported | Full surface | first set/clear bit | | GETBIT | Bitmaps | Supported | Full surface | - | | SETBIT | Bitmaps | Supported | Full surface | - | | Backup / snapshot / restore | Durability | Supported | Most usage | Import and Export of RDB files through a storage account on every tier | | Persistence (RDB / AOF) | Durability | Partial | Most usage | optional RDB or AOF to a managed disk, to recover the same cache after an outage; no analog of the Valkey 9.0 Multi-AZ durability log's synchronous acknowledgement | | Search / JSON / modules (FT.\* / JSON.\*) | Extensions | Supported | Full surface | RediSearch (vector and full-text), RedisJSON, RedisBloom and RedisTimeSeries are built in on the in-memory tiers (Flash Optimized has JSON only); the JSON.*, BF.* and FT.\* families a Valkey 8.1+ replication group uses are served by the modules of the same names, and RediSearch needs the Enterprise clustering policy | | GEOADD | Geo | Supported | Full surface | - | | GEODIST | Geo | Supported | Full surface | - | | GEOHASH | Geo | Supported | Full surface | geohash strings | | GEOPOS | Geo | Supported | Full surface | member coordinates | | GEORADIUS | Geo | Supported | Full surface | deprecated radius query (use GEOSEARCH) | | GEORADIUSBYMEMBER | Geo | Supported | Full surface | deprecated radius-by-member (use GEOSEARCH) | | GEORADIUSBYMEMBER\_RO | Geo | Supported | Full surface | read-only deprecated radius-by-member | | GEORADIUS\_RO | Geo | Supported | Full surface | read-only deprecated radius query | | GEOSEARCH | Geo | Supported | Full surface | - | | GEOSEARCHSTORE | Geo | Supported | Full surface | search + store result | | HDEL | Hashes | Supported | Common | - | | HEXISTS | Hashes | Supported | Most usage | - | | HEXPIRE | Hashes | Supported | Most usage | per-field TTL (seconds); in the Redis 7.4 engine | | HEXPIREAT | Hashes | Supported | Most usage | per-field expiry at unix time; in the Redis 7.4 engine | | HEXPIRETIME | Hashes | Supported | Full surface | absolute per-field expiry (s); in the Redis 7.4 engine | | HGET | Hashes | Supported | Common | - | | HGETALL | Hashes | Supported | Common | - | | HGETDEL | Hashes | Out of scope | Most usage | get and delete field(s); a Valkey 9.1 / Redis 8.0 command, absent on the Redis 7.4 engine | | HGETEX | Hashes | Out of scope | Most usage | get field(s) and set or refresh their expiry; a Valkey 9.0 / Redis 8.0 command, absent on the Redis 7.4 engine | | HINCRBY | Hashes | Supported | Most usage | - | | HINCRBYFLOAT | Hashes | Supported | Most usage | - | | HKEYS | Hashes | Supported | Most usage | - | | HLEN | Hashes | Supported | Most usage | - | | HMGET | Hashes | Supported | Common | - | | HMSET | Hashes | Supported | Full surface | deprecated alias of HSET | | HPERSIST | Hashes | Supported | Most usage | remove a field's TTL; in the Redis 7.4 engine | | HPEXPIRE | Hashes | Supported | Most usage | per-field TTL (ms); in the Redis 7.4 engine | | HPEXPIREAT | Hashes | Supported | Most usage | per-field expiry at ms unix time; in the Redis 7.4 engine | | HPEXPIRETIME | Hashes | Supported | Full surface | absolute per-field expiry (ms); in the Redis 7.4 engine | | HPTTL | Hashes | Supported | Most usage | remaining per-field TTL (ms); in the Redis 7.4 engine | | HRANDFIELD | Hashes | Supported | Full surface | - | | HSET | Hashes | Supported | Common | - | | HSETEX | Hashes | Out of scope | Most usage | set field(s) with expiry; a Valkey 9.0 / Redis 8.0 command, absent on the Redis 7.4 engine | | HSETNX | Hashes | Supported | Most usage | set field if not exists | | HSTRLEN | Hashes | Supported | Full surface | - | | HTTL | Hashes | Supported | Most usage | remaining per-field TTL (s); in the Redis 7.4 engine | | HVALS | Hashes | Supported | Most usage | - | | PFADD | HyperLogLog | Supported | Full surface | - | | PFCOUNT | HyperLogLog | Supported | Full surface | - | | PFMERGE | HyperLogLog | Supported | Full surface | - | | CLUSTERSCAN | Keys & TTL | Out of scope | Full surface | cluster-wide key scan across every node (Valkey 9.1); absent on the Redis 7.4 engine | | COPY | Keys & TTL | Supported | Full surface | copy key | | DEL | Keys & TTL | Supported | Common | - | | DELIFEQ | Keys & TTL | Out of scope | Full surface | delete a key only if its value matches (Valkey 9.0); absent on the Redis 7.4 engine | | DUMP | Keys & TTL | Supported | Full surface | - | | EXISTS | Keys & TTL | Supported | Common | - | | EXPIRE | Keys & TTL | Supported | Common | - | | EXPIREAT | Keys & TTL | Supported | Most usage | expire at unix time | | EXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (s) | | HSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | KEYS | Keys & TTL | Supported | Common | - | | OBJECT | Keys & TTL | Supported | Full surface | ENCODING / IDLETIME / REFCOUNT | | PERSIST | Keys & TTL | Supported | Common | - | | PEXPIRE | Keys & TTL | Supported | Common | - | | PEXPIREAT | Keys & TTL | Supported | Most usage | expire at ms unix time | | PEXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (ms) | | PTTL | Keys & TTL | Supported | Most usage | ms TTL | | RANDOMKEY | Keys & TTL | Supported | Full surface | - | | RENAME | Keys & TTL | Supported | Common | - | | RENAMENX | Keys & TTL | Supported | Most usage | rename if target absent | | RESTORE | Keys & TTL | Supported | Full surface | - | | SCAN | Keys & TTL | Supported | Most usage | cursor iteration | | SORT | Keys & TTL | Supported | Full surface | sort list/set/zset | | SORT\_RO | Keys & TTL | Supported | Full surface | read-only SORT (replica-safe) | | SSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | TOUCH | Keys & TTL | Supported | Full surface | bump last-access | | TTL | Keys & TTL | Supported | Common | - | | TYPE | Keys & TTL | Supported | Common | - | | UNLINK | Keys & TTL | Supported | Most usage | async delete | | WAIT | Keys & TTL | Supported | Full surface | block until N replicas acknowledge | | WAITAOF | Keys & TTL | Supported | Full surface | block until AOF fsync, with AOF persistence enabled on the cache | | ZSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | BLMOVE | Lists | Supported | Full surface | blocking move | | BLMPOP | Lists | Supported | Full surface | blocking multi-list pop | | BLPOP | Lists | Supported | Most usage | blocking pop | | BRPOP | Lists | Supported | Most usage | blocking pop | | BRPOPLPUSH | Lists | Supported | Full surface | blocking legacy move | | LINDEX | Lists | Supported | Most usage | - | | LINSERT | Lists | Supported | Most usage | insert before/after pivot | | LLEN | Lists | Supported | Most usage | - | | LMOVE | Lists | Supported | Full surface | atomic move between lists | | LMPOP | Lists | Supported | Full surface | multi-list pop | | LPOP | Lists | Supported | Common | - | | LPOS | Lists | Supported | Full surface | index of matching element | | LPUSH | Lists | Supported | Common | - | | LPUSHX | Lists | Supported | Full surface | push only if list exists | | LRANGE | Lists | Supported | Most usage | - | | LREM | Lists | Supported | Most usage | - | | LSET | Lists | Supported | Most usage | set by index | | LTRIM | Lists | Supported | Most usage | - | | RPOP | Lists | Supported | Common | - | | RPOPLPUSH | Lists | Supported | Most usage | legacy atomic move | | RPUSH | Lists | Supported | Common | - | | RPUSHX | Lists | Supported | Full surface | push only if list exists | | Eviction (maxmemory-policy) | Memory | Supported | Most usage | the full maxmemory-policy family through the cache's eviction policy; RediSearch requires noeviction | | Replication / HA / failover | Operations | Supported | Most usage | high availability on by default: a replica shard of every primary on a second node, zone-distributed where the region has zones, automatic failover under Azure's SLA; a replication group's replicas-per-shard count does not carry as a number | | PSUBSCRIBE | Pub/Sub | Supported | Most usage | - | | PUBLISH | Pub/Sub | Supported | Most usage | - | | PUBSUB | Pub/Sub | Supported | Most usage | introspect pub/sub state | | PUNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from patterns | | SPUBLISH | Pub/Sub | Supported | Full surface | sharded pub/sub publish under the OSS clustering policy; plain pub/sub under Enterprise and Non-clustered | | SSUBSCRIBE | Pub/Sub | Supported | Full surface | sharded pub/sub subscribe under the OSS clustering policy; plain pub/sub under Enterprise and Non-clustered | | SUBSCRIBE | Pub/Sub | Supported | Most usage | - | | SUNSUBSCRIBE | Pub/Sub | Supported | Full surface | sharded pub/sub unsubscribe under the OSS clustering policy; plain pub/sub under Enterprise and Non-clustered | | UNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from channels | | Admin / config / replication commands (CONFIG / DEBUG / SAVE / SLAVEOF / CLUSTER admin) | Restricted admin | Out of scope | Full surface | the admin / replication / cluster surface AWS ElastiCache already restricts moves to the Azure control plane; Azure additionally disables the ACL command, SELECT has one database, and FLUSHALL / FLUSHDB are blocked under active geo-replication | | EVAL | Scripting | Supported | Most usage | server-side Lua | | EVALSHA | Scripting | Supported | Most usage | - | | EVALSHA\_RO | Scripting | Supported | Most usage | read-only EVALSHA | | EVAL\_RO | Scripting | Supported | Most usage | read-only EVAL (replica-safe) | | SCRIPT | Scripting | Supported | Most usage | - | | AUTH / ACL / RBAC | Security | Supported | Most usage | Microsoft Entra ID (the default on new caches) or access keys; RBAC user groups map to Entra identities and data-access ACLs set on the control plane, and ACL SETUSER at runtime is disabled | | Encryption at rest | Security | Supported | Most usage | a platform-managed key by default; a customer-managed key through Key Vault on every tier | | Encryption in transit (TLS) | Security | Supported | Common | TLS 1.2 minimum on every tier; your replication group's in-transit setting carries | | AUTH | Server & connection | Supported | Common | authenticate the connection | | ECHO | Server & connection | Supported | Common | - | | HELLO | Server & connection | Supported | Common | RESP3 handshake + AUTH/SETNAME | | INFO | Server & connection | Supported | Common | - | | PING | Server & connection | Supported | Common | - | | QUIT | Server & connection | Supported | Full surface | close the connection (deprecated) | | RESET | Server & connection | Out of scope | Full surface | not served by the Redis Enterprise engine | | SELECT | Server & connection | Out of scope | Common | logical database select; Redis Enterprise exposes one logical database per cache, so there is nothing to switch to on any clustering policy | | SADD | Sets | Supported | Common | - | | SCARD | Sets | Supported | Common | - | | SDIFF | Sets | Supported | Most usage | + SDIFFSTORE | | SDIFFSTORE | Sets | Supported | Most usage | store difference | | SINTER | Sets | Supported | Most usage | + SINTERSTORE | | SINTERCARD | Sets | Supported | Full surface | intersection cardinality | | SINTERSTORE | Sets | Supported | Most usage | store intersection | | SISMEMBER | Sets | Supported | Common | - | | SMEMBERS | Sets | Supported | Common | - | | SMISMEMBER | Sets | Supported | Full surface | multi-membership test | | SMOVE | Sets | Supported | Full surface | atomic move between sets | | SPOP | Sets | Supported | Most usage | pop random member(s) | | SRANDMEMBER | Sets | Supported | Most usage | random member(s) | | SREM | Sets | Supported | Common | - | | SUNION | Sets | Supported | Most usage | + SUNIONSTORE | | SUNIONSTORE | Sets | Supported | Most usage | store union | | Serverless / auto-scaling | Sizing | Out of scope | Most usage | this is the provisioned origin, so there is no serverless surface to carry | | BZMPOP | Sorted sets | Supported | Full surface | blocking multi-key pop | | BZPOPMAX | Sorted sets | Supported | Full surface | blocking pop highest | | BZPOPMIN | Sorted sets | Supported | Full surface | blocking pop lowest | | ZADD | Sorted sets | Supported | Common | - | | ZCARD | Sorted sets | Supported | Common | - | | ZCOUNT | Sorted sets | Supported | Most usage | count in score range | | ZDIFF | Sorted sets | Supported | Full surface | + ZDIFFSTORE | | ZDIFFSTORE | Sorted sets | Supported | Most usage | store difference | | ZINCRBY | Sorted sets | Supported | Most usage | - | | ZINTER | Sorted sets | Supported | Full surface | + ZINTERSTORE / ZINTERCARD | | ZINTERCARD | Sorted sets | Supported | Full surface | intersection cardinality | | ZINTERSTORE | Sorted sets | Supported | Most usage | store intersection | | ZLEXCOUNT | Sorted sets | Supported | Full surface | count in lex range | | ZMPOP | Sorted sets | Supported | Full surface | multi-key pop | | ZMSCORE | Sorted sets | Supported | Full surface | multi-member scores | | ZPOPMAX | Sorted sets | Supported | Most usage | pop highest score | | ZPOPMIN | Sorted sets | Supported | Most usage | pop lowest score | | ZRANDMEMBER | Sorted sets | Supported | Full surface | random member(s) | | ZRANGE | Sorted sets | Supported | Most usage | - | | ZRANGEBYLEX | Sorted sets | Supported | Full surface | lexicographic range | | ZRANGEBYSCORE | Sorted sets | Supported | Most usage | - | | ZRANGESTORE | Sorted sets | Supported | Full surface | store a range result | | ZRANK | Sorted sets | Supported | Most usage | - | | ZREM | Sorted sets | Supported | Common | - | | ZREMRANGEBYLEX | Sorted sets | Supported | Full surface | remove by lex range | | ZREMRANGEBYRANK | Sorted sets | Supported | Full surface | remove by rank range | | ZREMRANGEBYSCORE | Sorted sets | Supported | Full surface | remove by score range | | ZREVRANGE | Sorted sets | Supported | Most usage | descending range | | ZREVRANGEBYLEX | Sorted sets | Supported | Full surface | descending lex range | | ZREVRANGEBYSCORE | Sorted sets | Supported | Most usage | descending range by score | | ZREVRANK | Sorted sets | Supported | Most usage | descending rank | | ZSCORE | Sorted sets | Supported | Common | - | | ZUNION | Sorted sets | Supported | Full surface | + ZUNIONSTORE | | ZUNIONSTORE | Sorted sets | Supported | Most usage | store union | | XACK | Streams | Supported | Full surface | - | | XADD | Streams | Supported | Full surface | - | | XAUTOCLAIM | Streams | Supported | Full surface | auto-claim idle pending | | XCLAIM | Streams | Supported | Full surface | claim pending messages | | XDEL | Streams | Supported | Full surface | delete entries | | XGROUP | Streams | Supported | Full surface | consumer-group create/destroy/setid | | XINFO | Streams | Supported | Full surface | stream/groups/consumers introspection | | XLEN | Streams | Supported | Full surface | - | | XPENDING | Streams | Supported | Full surface | pending-entries summary | | XRANGE | Streams | Supported | Full surface | - | | XREAD | Streams | Supported | Full surface | - | | XREADGROUP | Streams | Supported | Full surface | consumer-group read | | XREVRANGE | Streams | Supported | Full surface | reverse range | | XSETID | Streams | Supported | Full surface | set last-id | | XTRIM | Streams | Supported | Full surface | trim to maxlen/minid | | APPEND | Strings | Supported | Most usage | - | | DECR | Strings | Supported | Common | - | | DECRBY | Strings | Supported | Most usage | - | | GET | Strings | Supported | Common | - | | GETDEL | Strings | Supported | Most usage | get and delete | | GETEX | Strings | Supported | Most usage | get and set expiry | | GETRANGE | Strings | Supported | Most usage | - | | GETSET | Strings | Supported | Common | - | | INCR | Strings | Supported | Common | - | | INCRBY | Strings | Supported | Common | - | | INCRBYFLOAT | Strings | Supported | Most usage | - | | LCS | Strings | Supported | Full surface | longest common subsequence | | MGET | Strings | Supported | Common | - | | MSET | Strings | Supported | Common | - | | MSETEX | Strings | Out of scope | Full surface | set several keys with one shared expiry (Valkey 9.1); absent on the Redis 7.4 engine | | MSETNX | Strings | Supported | Most usage | multi-set if none exist | | PSETEX | Strings | Supported | Most usage | set with ms expiry | | SET | Strings | Supported | Common | - | | SETEX | Strings | Supported | Common | set with expiry | | SETNX | Strings | Supported | Common | set if not exists | | SETRANGE | Strings | Supported | Most usage | - | | STRLEN | Strings | Supported | Most usage | - | | SUBSTR | Strings | Supported | Full surface | deprecated alias of GETRANGE | | Cluster mode (slot topology) | Topology | Supported | Most usage | three clustering policies: OSS (the Redis Cluster API a cluster-mode-enabled client already speaks; initial connection on port 10000), Enterprise (one endpoint, the service routes), and Non-clustered for caches of 25 GB or less; the shard count is the SKU's, never a number you set | | DISCARD | Transactions | Supported | Most usage | - | | EXEC | Transactions | Supported | Most usage | - | | MULTI | Transactions | Supported | Most usage | - | | UNWATCH | Transactions | Supported | Most usage | forget all WATCHed keys | | WATCH | Transactions | Supported | Most usage | optimistic lock | #### How it works On AWS your cache is a provisioned **Valkey** replication group: a node type you chose, one or more shards, up to five replicas per shard and Multi-AZ failover, reached over the Redis wire protocol (RESP). On Azure the same application runs against an **Azure Managed Redis** cache built on the Redis Enterprise engine, and the Redis client connects to that cache's endpoint over the same wire. No adapter sits between the client and the cache; every command runs on the Enterprise engine itself. The ElastiCache management calls an application makes to locate its cache still work. When your code calls `DescribeReplicationGroups` or `DescribeCacheClusters` at startup, the Tensor9 service adapter answers from the cache's host name and its database's port and state (Azure keeps the two on separate resources), in the response shape the AWS SDK expects. A runtime `CreateReplicationGroup`, `ModifyReplicationGroup` or `DeleteReplicationGroup` from the application is refused with an ElastiCache error; provisioning belongs to your deployment. * **Same client, same wire:** the application keeps its Redis client and speaks RESP straight to the cache; under the OSS clustering policy the initial connection is port 10000 and the client discovers shard ports through `CLUSTER NODES`, as a cluster-mode-enabled ElastiCache client already does. * **The AWS SDK still finds the cache.** `DescribeReplicationGroups` and `DescribeCacheClusters` return the cache's host, port and status; an application that reads its endpoint from configuration never makes the call. * **A managed cache.** Microsoft operates the engine, replication, zone distribution and failover. You choose the SKU and memory size. #### Limitations Azure Managed Redis runs a different engine from a Valkey replication group and buys capacity differently; the divergences below are the ones that decide a cutover. △ Where a Valkey replication group and Azure Managed Redis diverge * **The engine is Redis Enterprise 7.4:** a multi-threaded, sharded-by-default implementation of the Redis wire. It serves the Redis 7.4 command set, so the hash-field TTL family is present, but Valkey's own additions are absent: `DELIFEQ`, `MSETEX`, `CLUSTERSCAN` and the Valkey 9 / Redis 8 `HGETEX`, `HSETEX` and `HGETDEL` return an unknown-command error. An application that depends on single-threaded ordering across connections should validate against the Enterprise engine. * **Shards belong to the SKU:** a replication group's shard count and replicas-per-shard become a SKU (Balanced, Memory Optimized, Compute Optimized or Flash Optimized) and a memory size; the service picks the shard count, and there is no scale-down, so a cache sized for a peak stays that size. * **One logical database, and slot-bound multi-key commands.** Redis Enterprise exposes one logical database, so `SELECT` has nothing to switch to; under the OSS and Enterprise policies a multi-key command whose keys hash to different slots returns `CROSSSLOT` (Enterprise allows `DEL`, `MSET`, `MGET`, `EXISTS`, `UNLINK` and `TOUCH` across slots). A cluster-mode-disabled replication group that relied on cross-key `MULTI` blocks picks the Non-clustered policy, which is limited to 25 GB. * **Search constrains policy and eviction.** RediSearch requires the Enterprise clustering policy and the noeviction policy, so a cache that serves `FT.*` queries cannot use the OSS Cluster API and cannot evict under memory pressure; size it for its full keyspace. #### Other considerations What remains is operational: how the replication group's sizing, failover, identity, persistence and data translate to a cache Microsoft runs. * **Sizing:** pick the tier by the memory-to-vCPU ratio your node type implied (Memory Optimized 8:1, Balanced 4:1, Compute Optimized 2:1), then the memory size; about a fifth of each cache's memory is reserved for replication and failover buffers, so size the SKU above the replication group's used memory rather than at it. * **Failover:** high availability keeps a replica shard of every primary on a second node, zone-distributed by default where the region has zones, and fails over automatically under Azure's SLA; clients reconnect to the same endpoint, as they do after an ElastiCache Multi-AZ failover. * **Authentication:** new caches default to Microsoft Entra ID (managed identity) with access keys still available; a replication group's RBAC user groups map to Entra identities and data-access ACLs set on the control plane, and `ACL SETUSER` at runtime is disabled. * **Persistence and backups.** RDB or AOF persistence to a managed disk recovers the same cache after an outage; a copy you keep is an Export to a storage account, and a new cache starts empty unless you Import one. * **Configuration:** the eviction policy, the TLS minimum version and the module set are cache settings on the control plane; `CONFIG SET` is refused at runtime, as it is on ElastiCache. * **Data migration:** most caches re-warm. A replication group that holds durable data exports an RDB to S3 and Imports it from a storage account before cutover. ## On Google Cloud ### Memorystore for Redis | Operation | Area | Support | Depth | Notes | | --------------------------------------------------------------------------------------- | ------------------- | ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BITCOUNT | Bitmaps | Supported | Full surface | - | | BITFIELD | Bitmaps | Supported | Full surface | arbitrary-width integer ops | | BITFIELD\_RO | Bitmaps | Supported | Full surface | read-only BITFIELD | | BITOP | Bitmaps | Supported | Full surface | bitwise AND/OR/XOR/NOT | | BITPOS | Bitmaps | Supported | Full surface | first set/clear bit | | GETBIT | Bitmaps | Supported | Full surface | - | | SETBIT | Bitmaps | Supported | Full surface | - | | Backup / snapshot / restore | Durability | Supported | Most usage | RDB export to and import from Cloud Storage; a restore seeds a new instance rather than replacing a live one | | Persistence (RDB / AOF) | Durability | Partial | Most usage | RDB snapshots on a 1, 6, 12 or 24 hour schedule; no AOF on the classic instance, and no analog of the Valkey 9.0 Multi-AZ durability log, so a write acknowledged as durable on ElastiCache 9.0 is at risk here until the next snapshot lands | | Search / JSON / modules (FT.\* / JSON.\*) | Extensions | Out of scope | Full surface | core Redis 7.2 types only; JSON, Bloom and FT.\* search calls from a Valkey 8.1+ replication group target Memorystore for Valkey, a distinct product | | GEOADD | Geo | Supported | Full surface | - | | GEODIST | Geo | Supported | Full surface | - | | GEOHASH | Geo | Supported | Full surface | geohash strings | | GEOPOS | Geo | Supported | Full surface | member coordinates | | GEORADIUS | Geo | Supported | Full surface | deprecated radius query (use GEOSEARCH) | | GEORADIUSBYMEMBER | Geo | Supported | Full surface | deprecated radius-by-member (use GEOSEARCH) | | GEORADIUSBYMEMBER\_RO | Geo | Supported | Full surface | read-only deprecated radius-by-member | | GEORADIUS\_RO | Geo | Supported | Full surface | read-only deprecated radius query | | GEOSEARCH | Geo | Supported | Full surface | - | | GEOSEARCHSTORE | Geo | Supported | Full surface | search + store result | | HDEL | Hashes | Supported | Common | - | | HEXISTS | Hashes | Supported | Most usage | - | | HEXPIRE | Hashes | Out of scope | Most usage | per-field TTL (seconds); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HEXPIREAT | Hashes | Out of scope | Most usage | per-field expiry at unix time; a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HEXPIRETIME | Hashes | Out of scope | Full surface | absolute per-field expiry (s); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HGET | Hashes | Supported | Common | - | | HGETALL | Hashes | Supported | Common | - | | HGETDEL | Hashes | Out of scope | Most usage | get and delete field(s); a Valkey 9.1 command, absent on the classic instance's Redis 7.2 engine | | HGETEX | Hashes | Out of scope | Most usage | get field(s) and set or refresh their expiry; a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HINCRBY | Hashes | Supported | Most usage | - | | HINCRBYFLOAT | Hashes | Supported | Most usage | - | | HKEYS | Hashes | Supported | Most usage | - | | HLEN | Hashes | Supported | Most usage | - | | HMGET | Hashes | Supported | Common | - | | HMSET | Hashes | Supported | Full surface | deprecated alias of HSET | | HPERSIST | Hashes | Out of scope | Most usage | remove a field's TTL; a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HPEXPIRE | Hashes | Out of scope | Most usage | per-field TTL (ms); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HPEXPIREAT | Hashes | Out of scope | Most usage | per-field expiry at ms unix time; a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HPEXPIRETIME | Hashes | Out of scope | Full surface | absolute per-field expiry (ms); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HPTTL | Hashes | Out of scope | Most usage | remaining per-field TTL (ms); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HRANDFIELD | Hashes | Supported | Full surface | - | | HSET | Hashes | Supported | Common | - | | HSETEX | Hashes | Out of scope | Most usage | set field(s) with expiry; a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HSETNX | Hashes | Supported | Most usage | set field if not exists | | HSTRLEN | Hashes | Supported | Full surface | - | | HTTL | Hashes | Out of scope | Most usage | remaining per-field TTL (s); a Valkey 9.0 command, absent on the classic instance's Redis 7.2 engine | | HVALS | Hashes | Supported | Most usage | - | | PFADD | HyperLogLog | Supported | Full surface | - | | PFCOUNT | HyperLogLog | Supported | Full surface | - | | PFMERGE | HyperLogLog | Supported | Full surface | - | | CLUSTERSCAN | Keys & TTL | Out of scope | Full surface | cluster-wide key scan across every node (Valkey 9.1); absent on the classic instance's Redis 7.2 engine | | COPY | Keys & TTL | Supported | Full surface | copy key | | DEL | Keys & TTL | Supported | Common | - | | DELIFEQ | Keys & TTL | Out of scope | Full surface | delete a key only if its value matches (Valkey 9.0); absent on the classic instance's Redis 7.2 engine | | DUMP | Keys & TTL | Supported | Full surface | - | | EXISTS | Keys & TTL | Supported | Common | - | | EXPIRE | Keys & TTL | Supported | Common | - | | EXPIREAT | Keys & TTL | Supported | Most usage | expire at unix time | | EXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (s) | | HSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | KEYS | Keys & TTL | Supported | Common | - | | OBJECT | Keys & TTL | Partial | Full surface | ENCODING / IDLETIME / REFCOUNT; blocked on the classic instance, served on the Memorystore for Redis Cluster / Valkey products | | PERSIST | Keys & TTL | Supported | Common | - | | PEXPIRE | Keys & TTL | Supported | Common | - | | PEXPIREAT | Keys & TTL | Supported | Most usage | expire at ms unix time | | PEXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (ms) | | PTTL | Keys & TTL | Supported | Most usage | ms TTL | | RANDOMKEY | Keys & TTL | Supported | Full surface | - | | RENAME | Keys & TTL | Supported | Common | - | | RENAMENX | Keys & TTL | Supported | Most usage | rename if target absent | | RESTORE | Keys & TTL | Supported | Full surface | - | | SCAN | Keys & TTL | Supported | Most usage | cursor iteration | | SORT | Keys & TTL | Supported | Full surface | sort list/set/zset | | SORT\_RO | Keys & TTL | Supported | Full surface | read-only SORT (replica-safe) | | SSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | TOUCH | Keys & TTL | Supported | Full surface | bump last-access | | TTL | Keys & TTL | Supported | Common | - | | TYPE | Keys & TTL | Supported | Common | - | | UNLINK | Keys & TTL | Supported | Most usage | async delete | | WAIT | Keys & TTL | Supported | Full surface | block until N replicas acknowledge | | WAITAOF | Keys & TTL | Out of scope | Full surface | block until AOF fsync; the classic instance persists by RDB snapshot only, so there is no AOF to wait on | | ZSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | BLMOVE | Lists | Supported | Full surface | blocking move | | BLMPOP | Lists | Supported | Full surface | blocking multi-list pop | | BLPOP | Lists | Supported | Most usage | blocking pop | | BRPOP | Lists | Supported | Most usage | blocking pop | | BRPOPLPUSH | Lists | Supported | Full surface | blocking legacy move | | LINDEX | Lists | Supported | Most usage | - | | LINSERT | Lists | Supported | Most usage | insert before/after pivot | | LLEN | Lists | Supported | Most usage | - | | LMOVE | Lists | Supported | Full surface | atomic move between lists | | LMPOP | Lists | Supported | Full surface | multi-list pop | | LPOP | Lists | Supported | Common | - | | LPOS | Lists | Supported | Full surface | index of matching element | | LPUSH | Lists | Supported | Common | - | | LPUSHX | Lists | Supported | Full surface | push only if list exists | | LRANGE | Lists | Supported | Most usage | - | | LREM | Lists | Supported | Most usage | - | | LSET | Lists | Supported | Most usage | set by index | | LTRIM | Lists | Supported | Most usage | - | | RPOP | Lists | Supported | Common | - | | RPOPLPUSH | Lists | Supported | Most usage | legacy atomic move | | RPUSH | Lists | Supported | Common | - | | RPUSHX | Lists | Supported | Full surface | push only if list exists | | Eviction (maxmemory-policy) | Memory | Supported | Most usage | the full maxmemory-policy family through the instance's Redis configuration; default volatile-lru, the same default as ElastiCache | | Replication / HA / failover | Operations | Supported | Most usage | Standard Tier: a cross-zone replica with automatic failover plus 1 to 5 read replicas, 99.9% SLA; Basic Tier is one node with no replica and no SLA, so a Multi-AZ replication group maps to Standard | | PSUBSCRIBE | Pub/Sub | Supported | Most usage | - | | PUBLISH | Pub/Sub | Supported | Most usage | - | | PUBSUB | Pub/Sub | Supported | Most usage | introspect pub/sub state | | PUNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from patterns | | SPUBLISH | Pub/Sub | Partial | Full surface | sharded pub/sub publish; the classic instance is one shard, so it behaves as plain pub/sub | | SSUBSCRIBE | Pub/Sub | Partial | Full surface | sharded pub/sub subscribe; the classic instance is one shard, so it behaves as plain pub/sub | | SUBSCRIBE | Pub/Sub | Supported | Most usage | - | | SUNSUBSCRIBE | Pub/Sub | Partial | Full surface | sharded pub/sub unsubscribe; the classic instance is one shard, so it behaves as plain pub/sub | | UNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from channels | | Admin / config / replication commands (CONFIG / DEBUG / SAVE / SLAVEOF / CLUSTER admin) | Restricted admin | Out of scope | Full surface | the admin / replication / cluster surface AWS ElastiCache already restricts moves to the Google Cloud control plane; Memorystore additionally blocks CLIENT / COMMAND / OBJECT / ACL / MODULE, and CONFIG moves to the instance's configuration flags | | EVAL | Scripting | Supported | Most usage | server-side Lua | | EVALSHA | Scripting | Supported | Most usage | - | | EVALSHA\_RO | Scripting | Supported | Most usage | read-only EVALSHA | | EVAL\_RO | Scripting | Supported | Most usage | read-only EVAL (replica-safe) | | SCRIPT | Scripting | Supported | Most usage | - | | AUTH / ACL / RBAC | Security | Partial | Most usage | one 36-character AUTH string per instance; the classic instance has no ACL users and no IAM authentication (those belong to Memorystore for Redis Cluster / Valkey), so RBAC user groups collapse to a single shared credential | | Encryption at rest | Security | Partial | Most usage | a customer-managed key (CMEK) binds when the instance is created and cannot be added later; it covers snapshots and backups, while the working set in memory is not encrypted, as on ElastiCache | | Encryption in transit (TLS) | Security | Supported | Common | TLS 1.2 or later when in-transit encryption is enabled on the instance; your replication group's in-transit setting is applied | | AUTH | Server & connection | Supported | Common | authenticate the connection | | ECHO | Server & connection | Supported | Common | - | | HELLO | Server & connection | Supported | Common | RESP3 handshake + AUTH/SETNAME | | INFO | Server & connection | Supported | Common | - | | PING | Server & connection | Supported | Common | - | | QUIT | Server & connection | Supported | Full surface | close the connection (deprecated) | | RESET | Server & connection | Supported | Full surface | reset connection state | | SELECT | Server & connection | Supported | Common | logical database select; the classic instance serves databases 0 to 15, as a cluster-mode-disabled replication group does | | SADD | Sets | Supported | Common | - | | SCARD | Sets | Supported | Common | - | | SDIFF | Sets | Supported | Most usage | + SDIFFSTORE | | SDIFFSTORE | Sets | Supported | Most usage | store difference | | SINTER | Sets | Supported | Most usage | + SINTERSTORE | | SINTERCARD | Sets | Supported | Full surface | intersection cardinality | | SINTERSTORE | Sets | Supported | Most usage | store intersection | | SISMEMBER | Sets | Supported | Common | - | | SMEMBERS | Sets | Supported | Common | - | | SMISMEMBER | Sets | Supported | Full surface | multi-membership test | | SMOVE | Sets | Supported | Full surface | atomic move between sets | | SPOP | Sets | Supported | Most usage | pop random member(s) | | SRANDMEMBER | Sets | Supported | Most usage | random member(s) | | SREM | Sets | Supported | Common | - | | SUNION | Sets | Supported | Most usage | + SUNIONSTORE | | SUNIONSTORE | Sets | Supported | Most usage | store union | | Serverless / auto-scaling | Sizing | Out of scope | Most usage | this is the provisioned origin, so there is no serverless surface to carry | | BZMPOP | Sorted sets | Supported | Full surface | blocking multi-key pop | | BZPOPMAX | Sorted sets | Supported | Full surface | blocking pop highest | | BZPOPMIN | Sorted sets | Supported | Full surface | blocking pop lowest | | ZADD | Sorted sets | Supported | Common | - | | ZCARD | Sorted sets | Supported | Common | - | | ZCOUNT | Sorted sets | Supported | Most usage | count in score range | | ZDIFF | Sorted sets | Supported | Full surface | + ZDIFFSTORE | | ZDIFFSTORE | Sorted sets | Supported | Most usage | store difference | | ZINCRBY | Sorted sets | Supported | Most usage | - | | ZINTER | Sorted sets | Supported | Full surface | + ZINTERSTORE / ZINTERCARD | | ZINTERCARD | Sorted sets | Supported | Full surface | intersection cardinality | | ZINTERSTORE | Sorted sets | Supported | Most usage | store intersection | | ZLEXCOUNT | Sorted sets | Supported | Full surface | count in lex range | | ZMPOP | Sorted sets | Supported | Full surface | multi-key pop | | ZMSCORE | Sorted sets | Supported | Full surface | multi-member scores | | ZPOPMAX | Sorted sets | Supported | Most usage | pop highest score | | ZPOPMIN | Sorted sets | Supported | Most usage | pop lowest score | | ZRANDMEMBER | Sorted sets | Supported | Full surface | random member(s) | | ZRANGE | Sorted sets | Supported | Most usage | - | | ZRANGEBYLEX | Sorted sets | Supported | Full surface | lexicographic range | | ZRANGEBYSCORE | Sorted sets | Supported | Most usage | - | | ZRANGESTORE | Sorted sets | Supported | Full surface | store a range result | | ZRANK | Sorted sets | Supported | Most usage | - | | ZREM | Sorted sets | Supported | Common | - | | ZREMRANGEBYLEX | Sorted sets | Supported | Full surface | remove by lex range | | ZREMRANGEBYRANK | Sorted sets | Supported | Full surface | remove by rank range | | ZREMRANGEBYSCORE | Sorted sets | Supported | Full surface | remove by score range | | ZREVRANGE | Sorted sets | Supported | Most usage | descending range | | ZREVRANGEBYLEX | Sorted sets | Supported | Full surface | descending lex range | | ZREVRANGEBYSCORE | Sorted sets | Supported | Most usage | descending range by score | | ZREVRANK | Sorted sets | Supported | Most usage | descending rank | | ZSCORE | Sorted sets | Supported | Common | - | | ZUNION | Sorted sets | Supported | Full surface | + ZUNIONSTORE | | ZUNIONSTORE | Sorted sets | Supported | Most usage | store union | | XACK | Streams | Supported | Full surface | - | | XADD | Streams | Supported | Full surface | - | | XAUTOCLAIM | Streams | Supported | Full surface | auto-claim idle pending | | XCLAIM | Streams | Supported | Full surface | claim pending messages | | XDEL | Streams | Supported | Full surface | delete entries | | XGROUP | Streams | Supported | Full surface | consumer-group create/destroy/setid | | XINFO | Streams | Supported | Full surface | stream/groups/consumers introspection | | XLEN | Streams | Supported | Full surface | - | | XPENDING | Streams | Supported | Full surface | pending-entries summary | | XRANGE | Streams | Supported | Full surface | - | | XREAD | Streams | Supported | Full surface | - | | XREADGROUP | Streams | Supported | Full surface | consumer-group read | | XREVRANGE | Streams | Supported | Full surface | reverse range | | XSETID | Streams | Supported | Full surface | set last-id | | XTRIM | Streams | Supported | Full surface | trim to maxlen/minid | | APPEND | Strings | Supported | Most usage | - | | DECR | Strings | Supported | Common | - | | DECRBY | Strings | Supported | Most usage | - | | GET | Strings | Supported | Common | - | | GETDEL | Strings | Supported | Most usage | get and delete | | GETEX | Strings | Supported | Most usage | get and set expiry | | GETRANGE | Strings | Supported | Most usage | - | | GETSET | Strings | Supported | Common | - | | INCR | Strings | Supported | Common | - | | INCRBY | Strings | Supported | Common | - | | INCRBYFLOAT | Strings | Supported | Most usage | - | | LCS | Strings | Supported | Full surface | longest common subsequence | | MGET | Strings | Supported | Common | - | | MSET | Strings | Supported | Common | - | | MSETEX | Strings | Out of scope | Full surface | set several keys with one shared expiry (Valkey 9.1); absent on the classic instance's Redis 7.2 engine | | MSETNX | Strings | Supported | Most usage | multi-set if none exist | | PSETEX | Strings | Supported | Most usage | set with ms expiry | | SET | Strings | Supported | Common | - | | SETEX | Strings | Supported | Common | set with expiry | | SETNX | Strings | Supported | Common | set if not exists | | SETRANGE | Strings | Supported | Most usage | - | | STRLEN | Strings | Supported | Most usage | - | | SUBSTR | Strings | Supported | Full surface | deprecated alias of GETRANGE | | Cluster mode (slot topology) | Topology | Partial | Most usage | the classic instance is one primary shard (Standard Tier: a primary plus up to 5 read replicas behind a read endpoint, 300 GB at most); a cluster-mode-enabled replication group maps to Memorystore for Redis Cluster or Memorystore for Valkey, distinct products, rather than this instance | | DISCARD | Transactions | Supported | Most usage | - | | EXEC | Transactions | Supported | Most usage | - | | MULTI | Transactions | Supported | Most usage | - | | UNWATCH | Transactions | Supported | Most usage | forget all WATCHed keys | | WATCH | Transactions | Supported | Most usage | optimistic lock | #### How it works On AWS your cache is a provisioned **Valkey** replication group: a node type you chose, one or more shards, up to five replicas per shard and Multi-AZ failover, reached over the Redis wire protocol (RESP) from a Redis client. On Google Cloud the same application runs against a **Memorystore for Redis** instance, the classic single-primary product, and the Redis client connects to that instance's private endpoint over the same wire. No adapter sits between the client and the cache; every command runs on the instance's own Redis 7.2 engine. The ElastiCache management calls an application makes to locate its cache still work. When your code calls `DescribeReplicationGroups` or `DescribeCacheClusters` at startup to learn its endpoint, the Tensor9 service adapter answers from the Memorystore instance's host, port and state, in the response shape the AWS SDK expects. A runtime `CreateReplicationGroup`, `ModifyReplicationGroup` or `DeleteReplicationGroup` from the application is refused with an ElastiCache error; provisioning belongs to your deployment, not to application code. * **Same client, same wire:** the application keeps its Redis client and speaks RESP straight to the Memorystore instance; there is no proxy in the data path. * **Endpoint discovery through the AWS SDK still works.** `DescribeReplicationGroups` and `DescribeCacheClusters` return the Memorystore host, port and status; an application that reads its endpoint from configuration never makes the call. * **A managed cache.** Google operates the instance: the cross-zone replica, automatic failover, snapshots and patching. You choose the tier and capacity. #### Limitations Memorystore for Redis is a different engine and a different shape from a Valkey replication group; the four divergences below decide whether it fits. △ Where a Valkey replication group and Memorystore for Redis diverge * **The engine is Redis 7.2:** the classic instance tops out at Redis 7.2, so JSON and the commands ElastiCache added at Valkey 8.1 and later are absent: Bloom filters, `FT.*` vector and full-text search, the hash-field TTL family (`HEXPIRE`, `HTTL` and the rest), `DELIFEQ`, `MSETEX` and `CLUSTERSCAN` return an unknown-command error. An application that uses them targets Memorystore for Valkey instead. * **One primary shard:** the classic instance is one primary with up to five read replicas and a 300 GB ceiling; it does not shard the keyspace. A cluster-mode-disabled replication group maps directly; a cluster-mode-enabled group that spreads slots across shards maps to Memorystore for Redis Cluster, a distinct product with its own resource. * **One AUTH string:** access is a single 36-character AUTH string per instance; there are no ACL users and no IAM authentication on the classic product, so RBAC user groups and IAM-authenticated users collapse to one shared credential that every client presents. * **Snapshots only, on a 1 to 24 hour schedule:** persistence is RDB snapshots at a 1, 6, 12 or 24 hour interval; there is no AOF and no analog of the Valkey 9.0 Multi-AZ durability log, so a write acknowledged as durable on ElastiCache 9.0 is at risk here until the next snapshot lands. #### Other considerations What remains is operational: how the replication group's sizing, failover, configuration and data translate to an instance Google runs. * **Sizing:** a node type per node becomes a tier plus a memory size: Standard Tier for anything that had replicas or Multi-AZ, Basic Tier only for a cache you can afford to lose, and a memory size up to 300 GB. Read replicas (1 to 5) need a 5 GB or larger instance and serve reads through a separate read endpoint, the same split as ElastiCache's reader endpoint. * **Failover.** Standard Tier fails over to its cross-zone replica automatically under a 99.9% SLA, where ElastiCache's Multi-AZ replication group is backed by 99.99%; clients reconnect to the same endpoint after either failover. * **Eviction and configuration:** the eviction policy and the other supported parameters move from the parameter group to the instance's configuration flags; the default is volatile-lru on both sides, and a runtime `CONFIG SET` is refused. * **Encryption:** in-transit TLS is a per-instance setting that follows the replication group's; a customer-managed key binds at create and covers snapshots and backups, while the working set in memory is not encrypted on either side. * **Data migration:** the instance starts empty. Most caches re-warm; a replication group that holds durable data exports an RDB to S3 and imports it from Cloud Storage before cutover. ## On Scaleway ### Scaleway Managed Database for Redis | Operation | Area | Support | Depth | Notes | | --------------------------------------------------------------------------------------- | ------------------- | ------------ | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BITCOUNT | Bitmaps | Supported | Full surface | - | | BITFIELD | Bitmaps | Supported | Full surface | arbitrary-width integer ops | | BITFIELD\_RO | Bitmaps | Supported | Full surface | read-only BITFIELD | | BITOP | Bitmaps | Supported | Full surface | bitwise AND/OR/XOR/NOT | | BITPOS | Bitmaps | Supported | Full surface | first set/clear bit | | GETBIT | Bitmaps | Supported | Full surface | - | | SETBIT | Bitmaps | Supported | Full surface | - | | Backup / snapshot / restore | Durability | Partial | Most usage | not configurable through this mapping -- the resource exposes no backup schedule or retention, so Scaleway's own behaviour applies and the window you declared does not carry. | | Persistence (RDB / AOF) | Durability | Partial | Most usage | not configurable through this mapping -- the resource exposes no persistence control, so Scaleway's own behaviour for Managed Redis applies rather than the policy you declared. | | Search / JSON / modules (FT.\* / JSON.\*) | Extensions | Partial | Full surface | not configurable through this mapping. The engine version is PINNED at the single version Scaleway offers, so whatever that build includes is what you get; there is nothing to select between. | | GEOADD | Geo | Supported | Full surface | - | | GEODIST | Geo | Supported | Full surface | - | | GEOHASH | Geo | Supported | Full surface | geohash strings | | GEOPOS | Geo | Supported | Full surface | member coordinates | | GEORADIUS | Geo | Supported | Full surface | deprecated radius query (use GEOSEARCH) | | GEORADIUSBYMEMBER | Geo | Supported | Full surface | deprecated radius-by-member (use GEOSEARCH) | | GEORADIUSBYMEMBER\_RO | Geo | Supported | Full surface | read-only deprecated radius-by-member | | GEORADIUS\_RO | Geo | Supported | Full surface | read-only deprecated radius query | | GEOSEARCH | Geo | Supported | Full surface | - | | GEOSEARCHSTORE | Geo | Supported | Full surface | search + store result | | HDEL | Hashes | Supported | Common | - | | HEXISTS | Hashes | Supported | Most usage | - | | HGET | Hashes | Supported | Common | - | | HGETALL | Hashes | Supported | Common | - | | HINCRBY | Hashes | Supported | Most usage | - | | HINCRBYFLOAT | Hashes | Supported | Most usage | - | | HKEYS | Hashes | Supported | Most usage | - | | HLEN | Hashes | Supported | Most usage | - | | HMGET | Hashes | Supported | Common | - | | HMSET | Hashes | Supported | Full surface | deprecated alias of HSET | | HRANDFIELD | Hashes | Supported | Full surface | - | | HSET | Hashes | Supported | Common | - | | HSETNX | Hashes | Supported | Most usage | set field if not exists | | HSTRLEN | Hashes | Supported | Full surface | - | | HVALS | Hashes | Supported | Most usage | - | | PFADD | HyperLogLog | Supported | Full surface | - | | PFCOUNT | HyperLogLog | Supported | Full surface | - | | PFMERGE | HyperLogLog | Supported | Full surface | - | | COPY | Keys & TTL | Supported | Full surface | copy key | | DEL | Keys & TTL | Supported | Common | - | | DUMP | Keys & TTL | Supported | Full surface | - | | EXISTS | Keys & TTL | Supported | Common | - | | EXPIRE | Keys & TTL | Supported | Common | - | | EXPIREAT | Keys & TTL | Supported | Most usage | expire at unix time | | EXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (s) | | HSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | KEYS | Keys & TTL | Supported | Common | - | | PERSIST | Keys & TTL | Supported | Common | - | | PEXPIRE | Keys & TTL | Supported | Common | - | | PEXPIREAT | Keys & TTL | Supported | Most usage | expire at ms unix time | | PEXPIRETIME | Keys & TTL | Supported | Most usage | absolute expiry time (ms) | | PTTL | Keys & TTL | Supported | Most usage | ms TTL | | RANDOMKEY | Keys & TTL | Supported | Full surface | - | | RENAME | Keys & TTL | Supported | Common | - | | RENAMENX | Keys & TTL | Supported | Most usage | rename if target absent | | RESTORE | Keys & TTL | Supported | Full surface | - | | SCAN | Keys & TTL | Supported | Most usage | cursor iteration | | SORT | Keys & TTL | Supported | Full surface | sort list/set/zset | | SORT\_RO | Keys & TTL | Supported | Full surface | read-only SORT (replica-safe) | | SSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | TOUCH | Keys & TTL | Supported | Full surface | bump last-access | | TTL | Keys & TTL | Supported | Common | - | | TYPE | Keys & TTL | Supported | Common | - | | UNLINK | Keys & TTL | Supported | Most usage | async delete | | ZSCAN | Keys & TTL | Supported | Most usage | cursor iteration | | BLMOVE | Lists | Supported | Full surface | blocking move | | BLMPOP | Lists | Supported | Full surface | blocking multi-list pop | | BLPOP | Lists | Supported | Most usage | blocking pop | | BRPOP | Lists | Supported | Most usage | blocking pop | | BRPOPLPUSH | Lists | Supported | Full surface | blocking legacy move | | LINDEX | Lists | Supported | Most usage | - | | LINSERT | Lists | Supported | Most usage | insert before/after pivot | | LLEN | Lists | Supported | Most usage | - | | LMOVE | Lists | Supported | Full surface | atomic move between lists | | LMPOP | Lists | Supported | Full surface | multi-list pop | | LPOP | Lists | Supported | Common | - | | LPOS | Lists | Supported | Full surface | index of matching element | | LPUSH | Lists | Supported | Common | - | | LPUSHX | Lists | Supported | Full surface | push only if list exists | | LRANGE | Lists | Supported | Most usage | - | | LREM | Lists | Supported | Most usage | - | | LSET | Lists | Supported | Most usage | set by index | | LTRIM | Lists | Supported | Most usage | - | | RPOP | Lists | Supported | Common | - | | RPOPLPUSH | Lists | Supported | Most usage | legacy atomic move | | RPUSH | Lists | Supported | Common | - | | RPUSHX | Lists | Supported | Full surface | push only if list exists | | Eviction (maxmemory-policy) | Memory | Partial | Most usage | reachable through the cluster's engine settings map rather than as a dedicated field, so an eviction policy is expressible but is not carried across automatically -- set it deliberately. | | Replication / HA / failover | Operations | Out of scope | Most usage | replica configuration on the origin is reported rather than mapped, for the same reason as cluster mode. You get a standalone cache, and the build says so. | | PSUBSCRIBE | Pub/Sub | Supported | Most usage | - | | PUBLISH | Pub/Sub | Supported | Most usage | - | | PUBSUB | Pub/Sub | Supported | Most usage | introspect pub/sub state | | PUNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from patterns | | SUBSCRIBE | Pub/Sub | Supported | Most usage | - | | UNSUBSCRIBE | Pub/Sub | Supported | Most usage | unsubscribe from channels | | Admin / config / replication commands (CONFIG / DEBUG / SAVE / SLAVEOF / CLUSTER admin) | Restricted admin | Out of scope | Full surface | administrative access is the cluster's own user and password rather than the origin's; the emitted credentials are what your application must use. | | EVAL | Scripting | Supported | Most usage | server-side Lua | | EVALSHA | Scripting | Supported | Most usage | - | | EVALSHA\_RO | Scripting | Supported | Most usage | read-only EVALSHA | | EVAL\_RO | Scripting | Supported | Most usage | read-only EVAL (replica-safe) | | SCRIPT | Scripting | Supported | Most usage | - | | AUTH / ACL / RBAC | Security | Supported | Most usage | the cluster requires a user name and takes a password, so authenticated access carries. As with the managed databases, the emitted credentials are the cluster's own rather than the origin's. | | Encryption at rest | Security | Partial | Most usage | not configurable through this mapping -- the resource exposes no at-rest encryption control, so Scaleway's own behaviour applies and a declared key or toggle does not carry. | | Encryption in transit (TLS) | Security | Supported | Common | TLS in transit is a direct setting on the emitted cluster. | | AUTH | Server & connection | Supported | Common | authenticate the connection | | ECHO | Server & connection | Supported | Common | - | | HELLO | Server & connection | Supported | Common | RESP3 handshake + AUTH/SETNAME | | INFO | Server & connection | Supported | Common | - | | PING | Server & connection | Supported | Common | - | | QUIT | Server & connection | Supported | Full surface | close the connection (deprecated) | | SADD | Sets | Supported | Common | - | | SCARD | Sets | Supported | Common | - | | SDIFF | Sets | Supported | Most usage | + SDIFFSTORE | | SDIFFSTORE | Sets | Supported | Most usage | store difference | | SINTER | Sets | Supported | Most usage | + SINTERSTORE | | SINTERCARD | Sets | Supported | Full surface | intersection cardinality | | SINTERSTORE | Sets | Supported | Most usage | store intersection | | SISMEMBER | Sets | Supported | Common | - | | SMEMBERS | Sets | Supported | Common | - | | SMISMEMBER | Sets | Supported | Full surface | multi-membership test | | SMOVE | Sets | Supported | Full surface | atomic move between sets | | SPOP | Sets | Supported | Most usage | pop random member(s) | | SRANDMEMBER | Sets | Supported | Most usage | random member(s) | | SREM | Sets | Supported | Common | - | | SUNION | Sets | Supported | Most usage | + SUNIONSTORE | | SUNIONSTORE | Sets | Supported | Most usage | store union | | Serverless / auto-scaling | Sizing | Out of scope | Most usage | this is the provisioned origin, so there is no serverless surface to carry. | | BZMPOP | Sorted sets | Supported | Full surface | blocking multi-key pop | | BZPOPMAX | Sorted sets | Supported | Full surface | blocking pop highest | | BZPOPMIN | Sorted sets | Supported | Full surface | blocking pop lowest | | ZADD | Sorted sets | Supported | Common | - | | ZCARD | Sorted sets | Supported | Common | - | | ZCOUNT | Sorted sets | Supported | Most usage | count in score range | | ZDIFF | Sorted sets | Supported | Full surface | + ZDIFFSTORE | | ZDIFFSTORE | Sorted sets | Supported | Most usage | store difference | | ZINCRBY | Sorted sets | Supported | Most usage | - | | ZINTER | Sorted sets | Supported | Full surface | + ZINTERSTORE / ZINTERCARD | | ZINTERCARD | Sorted sets | Supported | Full surface | intersection cardinality | | ZINTERSTORE | Sorted sets | Supported | Most usage | store intersection | | ZLEXCOUNT | Sorted sets | Supported | Full surface | count in lex range | | ZMPOP | Sorted sets | Supported | Full surface | multi-key pop | | ZMSCORE | Sorted sets | Supported | Full surface | multi-member scores | | ZPOPMAX | Sorted sets | Supported | Most usage | pop highest score | | ZPOPMIN | Sorted sets | Supported | Most usage | pop lowest score | | ZRANDMEMBER | Sorted sets | Supported | Full surface | random member(s) | | ZRANGE | Sorted sets | Supported | Most usage | - | | ZRANGEBYLEX | Sorted sets | Supported | Full surface | lexicographic range | | ZRANGEBYSCORE | Sorted sets | Supported | Most usage | - | | ZRANGESTORE | Sorted sets | Supported | Full surface | store a range result | | ZRANK | Sorted sets | Supported | Most usage | - | | ZREM | Sorted sets | Supported | Common | - | | ZREMRANGEBYLEX | Sorted sets | Supported | Full surface | remove by lex range | | ZREMRANGEBYRANK | Sorted sets | Supported | Full surface | remove by rank range | | ZREMRANGEBYSCORE | Sorted sets | Supported | Full surface | remove by score range | | ZREVRANGE | Sorted sets | Supported | Most usage | descending range | | ZREVRANGEBYLEX | Sorted sets | Supported | Full surface | descending lex range | | ZREVRANGEBYSCORE | Sorted sets | Supported | Most usage | descending range by score | | ZREVRANK | Sorted sets | Supported | Most usage | descending rank | | ZSCORE | Sorted sets | Supported | Common | - | | ZUNION | Sorted sets | Supported | Full surface | + ZUNIONSTORE | | ZUNIONSTORE | Sorted sets | Supported | Most usage | store union | | XACK | Streams | Supported | Full surface | - | | XADD | Streams | Supported | Full surface | - | | XAUTOCLAIM | Streams | Supported | Full surface | auto-claim idle pending | | XCLAIM | Streams | Supported | Full surface | claim pending messages | | XDEL | Streams | Supported | Full surface | delete entries | | XGROUP | Streams | Supported | Full surface | consumer-group create/destroy/setid | | XINFO | Streams | Supported | Full surface | stream/groups/consumers introspection | | XLEN | Streams | Supported | Full surface | - | | XPENDING | Streams | Supported | Full surface | pending-entries summary | | XRANGE | Streams | Supported | Full surface | - | | XREAD | Streams | Supported | Full surface | - | | XREADGROUP | Streams | Supported | Full surface | consumer-group read | | XREVRANGE | Streams | Supported | Full surface | reverse range | | XSETID | Streams | Supported | Full surface | set last-id | | XTRIM | Streams | Supported | Full surface | trim to maxlen/minid | | APPEND | Strings | Supported | Most usage | - | | DECR | Strings | Supported | Common | - | | DECRBY | Strings | Supported | Most usage | - | | GET | Strings | Supported | Common | - | | GETDEL | Strings | Supported | Most usage | get and delete | | GETEX | Strings | Supported | Most usage | get and set expiry | | GETRANGE | Strings | Supported | Most usage | - | | GETSET | Strings | Supported | Common | - | | INCR | Strings | Supported | Common | - | | INCRBY | Strings | Supported | Common | - | | INCRBYFLOAT | Strings | Supported | Most usage | - | | MGET | Strings | Supported | Common | - | | MSET | Strings | Supported | Common | - | | MSETNX | Strings | Supported | Most usage | multi-set if none exist | | PSETEX | Strings | Supported | Most usage | set with ms expiry | | SET | Strings | Supported | Common | - | | SETEX | Strings | Supported | Common | set with expiry | | SETNX | Strings | Supported | Common | set if not exists | | SETRANGE | Strings | Supported | Most usage | - | | STRLEN | Strings | Supported | Most usage | - | | SUBSTR | Strings | Supported | Full surface | deprecated alias of GETRANGE | | Cluster mode (slot topology) | Topology | Out of scope | Most usage | a standalone instance is emitted -- cluster\_size is 1. Scaleway's accepted values for a sharded cluster were deliberately not guessed: this mapping transcribes a value that constrains an apply from a live read or does not emit it at all, and measuring sharded sizes means provisioning one. | | DISCARD | Transactions | Supported | Most usage | - | | EXEC | Transactions | Supported | Most usage | - | | MULTI | Transactions | Supported | Most usage | - | | UNWATCH | Transactions | Supported | Most usage | forget all WATCHed keys | | WATCH | Transactions | Supported | Most usage | optimistic lock | ## Existing data and credentials Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application's endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target. ## Configure, tune and debug Start with [setup](/cloud-adapter/getting-started/overview) and [configuration](/cloud-adapter/configuration/overview). Use [tuning](/cloud-adapter/tuning/overview) to understand supported request tags, [debugging](/cloud-adapter/debugging/overview) to investigate a request, and [High Fidelity Cloud Emulators](/cloud-adapter/local-testing/overview) to validate a bounded reproduction.