← BLOG
[ MEMORA ] · · 4 MIN READ

Memora: one console for Amazon ElastiCache, in your own AWS account

Cloud Certainty Memora is a console for Amazon ElastiCache that runs in your AWS account: every cache across accounts and Regions with its cost and findings, full control of each one, and a key browser, workbench and memory analysis your whole team can use safely.

The Memora banner: the console for Amazon ElastiCache, with the memory cell mark and its four benefits

Amazon ElastiCache is easy to start with and hard to see across. The console shows one Region at a time, says little about what each cache costs or what is wrong with it, and has no way to look inside a cache at all. So teams end up with a desktop data browser on a few laptops, a shared password in a password manager, and a bastion host or a VPN to reach private endpoints.

Cloud Certainty Memora is the console we wanted instead. It runs as one CloudFormation stack in your own AWS account, and it covers both halves of the job: running the caches, and working with the data in them.

Every cache, with its cost and what to fix

Memora lists every cache you can see, in every connected account and Region, in one table: Valkey, Redis OSS and Memcached, node-based and serverless. For each one you see the engine and version, nodes, memory, engine CPU, hit rate, operations per second and an estimated monthly cost from the AWS Price List.

Findings sit next to each cache and add up across the fleet:

  • Redis OSS 4 and 5 caches paying for Extended Support since 1 February 2026, and what that surcharge costs a month.
  • What the same nodes would cost on Valkey (20% less node-based, 33% less serverless).
  • Caches without encryption in transit or at rest, without authentication, without failover or without backups.
  • Previous-generation and underused nodes, memory pressure, swap, throttled serverless caches and pending service updates.

The findings view groups them by severity with the monthly saving of each, so the first page you open is also a to-do list.

Full control of each cache

A cache's page has its topology, metrics, events and settings in one place. People with the right permission can take, copy and restore backups, change the node type, replicas, shards or serverless limits, test failover, reboot nodes, apply service updates, edit parameter groups, windows and tags, and upgrade the engine, including Redis OSS to Valkey in place. Administrators manage ElastiCache users and user groups, and can create and delete caches.

Inside the cache

This is the part the ElastiCache console has never had.

  • A key browser that uses SCAN, never KEYS, with a tree by key prefix, type and pattern filters, TTLs and sizes, and editors for strings, JSON documents, hashes, lists, sets, sorted sets and streams with their consumer groups.
  • A command workbench with redis-cli syntax, autocomplete and help for every Valkey and Redis OSS command, results as text, a table or JSON, and saved scripts with versions that can be shared with the team.
  • Memory analysis that samples the keyspace safely and breaks it down by type, TTL and key prefix, with the biggest keys and advice.
  • A monitor for INFO, the slow log, connected clients and Pub/Sub messages.
  • Bulk jobs that delete, expire or persist keys by pattern, paced so production stays healthy, and run by a Step Functions workflow in your account.

Access per person, enforced three times

Administrators grant users and groups view, read, write, operate or manage on cache name patterns, per account and Region. On the Business plan a grant can also carry key patterns, so a support team can fix cart:* and order:* keys without seeing anything else in the same cache.

Every write is checked three times. Memora refuses it if the person lacks the permission or the key pattern. AWS refuses it too, because each request runs with a short session policy built from that person's grants. And the cache refuses it, because people without write reach the data through a read-only ElastiCache user. Every AWS call carries the person's email in CloudTrail, and Memora keeps a command history and an audit log.

It runs in your account

One stack deploys a serverless API, a web portal on AWS Amplify Hosting, Amazon Cognito sign-in through IAM Identity Center, SAML or OIDC, and a small connector function in the VPC of your caches. Other accounts and VPCs join with a role stack and a connector stack. Cache values are never stored, nothing phones home, and the licence is read from AWS License Manager. Plans are priced per team, not per user, cache or node.

Memora is in early access. See the product page at cloudcertainty.com/memora (opens in a new tab) for the demo video, plans and documentation, or get in touch at [email protected].

More in Memora → All posts →

Tell us what you have. We'll make it better and cheaper.

Send a short description of your current setup. We will tell you what we would improve, what it would cost, and where the savings are. A considered reply from an engineer, not a sales sequence.

TELL US ABOUT YOUR SETUP →