ARNscopeDocs

Valkey on Amazon ElastiCache

Last updated 16 October 2026

ARNscope shows an ElastiCache cache from the outside (its endpoints, nodes, security and users) and, through a tunnel, from the inside: every key and its value, any Pub/Sub channel or pattern, and new entries on any stream. It reads by default. For operational work, such as publishing an event during disaster recovery so other servers refresh or run a job, you can turn on writes for one connection; see Writing (danger zone). ARNscope never configures a cache, runs scripts or flushes data.

A two-minute narrated tour, with captions: the Overview, connecting through a tunnel, keys, Pub/Sub, streams and writes. Sample data.

Two kinds of tabs

Open Valkey in ARNscope, choose the profile and region, and select a cache. The list shows Valkey and Redis OSS caches: node-based replication groups and serverless caches.

Tab Where the data comes from Needs a tunnel
Overview The ElastiCache API (DescribeReplicationGroups, DescribeCacheClusters, DescribeServerlessCaches, DescribeUserGroups, DescribeUsers) No
Keys The cache Yes
Pub/Sub The cache Yes
Streams The cache Yes
The Overview: endpoints and nodes, then every user, marked Read-only or Can write.

ElastiCache is only reachable inside its VPC, so the last three tabs need an ARNscope Valkey tunnel: a saved tunnel on the Tunnels page that opens one SSM session to the cache’s primary endpoint through an instance in your network. See SSM tunnels.

Start the tunnel, choose a user and connect: the bar shows who you are connected as and how many keys the cache holds.

Requirements

A read-only ElastiCache user

For browsing, a user that can only read is the safest choice. For example:

on ~* &* -@all +@read +subscribe +psubscribe +ssubscribe +unsubscribe +punsubscribe +sunsubscribe +ping +acl|whoami +client|setname

Optionally add +pubsub|channels +pubsub|shardchannels (for Active channels) and +info (to show the server version). Narrow ~* and &* to the keys and channels the user may read, for example ~chart:* &chart:*.

ARNscope lists every IAM and password user in the cache’s user groups. It suggests a read-only one and labels users that may write with Can write; writes stay off as them until you turn them on. Password users ask where the password comes from before connecting, and suggest Secrets Manager secrets whose name, description or tags mention the cache or the user. Users with no password cannot be used.

Read by default

Every read passes an allowlist before a single byte is sent: SCAN, TYPE, PTTL, OBJECT ENCODING, MEMORY USAGE, the length and range reads of each type, XINFO, plain XREAD, the subscribe commands, PUBSUB CHANNELS, INFO, JSON.GET and connection housekeeping (AUTH, PING, ACL WHOAMI, CLIENT SETNAME). KEYS, consumer groups (XREADGROUP, XACK), MONITOR, CONFIG and scripts are always refused. Writes never go through this path; they have their own, below.

Writing (danger zone)

Every write is a danger-zone operation.

Allow writes asks first, then shows the red Writes on chip with the minutes left. Turning it off makes the connection read-only again.

What you can do:

Where Writes
Pub/Sub → Publish Publish a message to a channel (or a sharded channel). The result counts subscribers on the primary only; subscribers on replicas are not counted, so 0 does not mean nobody received it.
Streams → Add entry Add an entry with fields and values to an existing stream; the result shows the new id.
Keys → New key Create a string (SET … NX, never replacing a key), hash, list, set, sorted set or stream.
Keys → selected key Edit a string (only after its full value is loaded, up to 1 MiB; binary values as base64, written back exactly), set or delete hash fields, push to a list, add or remove set and sorted-set members, add a stream entry, set or remove the TTL, delete the key (UNLINK). Elements shown truncated can’t be removed, since ARNscope can’t name them exactly.

A user that may publish to one channel, for example, needs an access string like on resetkeys resetchannels &jobs:refresh -@all +publish.

Publish: the red confirmation names the command, cache, user and size; the result counts subscribers on the primary.
New key, edit a loaded value and delete the key. Each write asks first and says when it can't be undone.

Keys

Keys are read a page at a time with SCAN (never KEYS), filtered by pattern and type. The pattern starts from the user’s key rule. Each page reads the type and TTL of its keys; memory is read only for the key you open. Keys the user may not read are listed as No access. Binary key names are shown in base64 and round-trip exactly.

Opening a key shows its type, TTL, encoding, memory and length, and its value: strings as text or JSON (binary values in the bytes viewer, with image and hex views), hashes, lists, sets and sorted sets as tables, streams with their entries, consumer groups and consumers, and JSON documents (ReJSON-RL). Collections load a page at a time, sized to about 4 MiB. Strings show their first 64 KiB; Load full value reads up to 10 MiB.

The list holds at most 20,000 keys; Clear list empties it. Only database 0 is browsed.

Load more keys, filter by pattern and type, then open a hash and a stream with its consumer group.

Pub/Sub

Add channels (SUBSCRIBE), patterns (PSUBSCRIBE) or sharded channels (SSUBSCRIBE) and press Subscribe. Nothing starts on its own. The user’s channel rules are offered as one-click patterns.

Sharded or classic

Valkey has two Pub/Sub systems that never cross over: a message sent with SPUBLISH reaches only SSUBSCRIBE listeners, and one sent with PUBLISH reaches only SUBSCRIBE and PSUBSCRIBE listeners. Sharded channels take exact names; there is no pattern form, so PSUBSCRIBE * hears nothing from services that use SPUBLISH.

ARNscope reads the cache’s users to tell which kind its services use. Users allowed to publish only one way decide it (+spublish without +publish means sharded); when no user publishes, users allowed to subscribe only one way do. Users allowed both, such as an admin with +@all, say nothing. If the users point one way, the tab starts on that kind and names the users it went by; if they disagree or say nothing, it says so. Either way the choice stays yours, and picking the other kind shows a warning.

ElastiCache checks channel names against the user’s & rules as globs, but compares PSUBSCRIBE patterns with them literally: with &chart:*, the pattern chart:* works but chart:AAPL:* does not. ARNscope checks typed patterns before subscribing and explains a refusal.

Subscribing to * on a busy cache can slow the tunnel for browsing too, so ARNscope asks first. Pub/Sub keeps no history: you see what is published from the moment you subscribe.

One click adds the user's pattern; Subscribe starts the live view and Pause keeps counting what arrives.

Channels, patterns, stream keys and key patterns you use are remembered per cache (names only, the 20 most recent of each kind) and offered as one-click chips; × forgets one.

Recent names come back on every tab; × forgets one, a click uses one again.

Finding channels

Find channels merges four sources, each tagged:

Click a channel to add it, or a pattern to add it as a pattern. On the Streams tab, literal key rules of users that may XADD or XREADGROUP are suggested as stream keys.

Find channels: names from access rules, then a five-second listen with message counts. Click one to add it.

Streams

Add stream keys (or use Find streams, a SCAN for streams), then Load latest reads the newest entries of each, or Live tail follows new entries. The tail starts from each stream’s newest entry and never joins a consumer group, so it does not affect your consumers. Pausing stops reading; the tail resumes where it paused without missing entries.

Find streams, Load latest, then Live tail, paused to read.

Memory limits

Busy channels never grow ARNscope’s memory without bound, and nothing received is written to disk or to logs.

Permissions

What Actions
List caches elasticache:DescribeReplicationGroups, elasticache:DescribeServerlessCaches, elasticache:DescribeCacheClusters, elasticache:DescribeUserGroups, elasticache:DescribeUsers
Overview The same
Keys, Pub/Sub and Streams elasticache:Connect (on the cache and the user) for IAM users, or secretsmanager:ListSecrets and secretsmanager:GetSecretValue for passwords from Secrets Manager; plus the tunnel’s SSM permissions
Writes elasticache:Connect; what succeeds is decided by the ElastiCache user’s access string

Limitations