Amazon MemoryDB
Amazon MemoryDB for Redis is a durable, in-memory database service that delivers ultra-fast performance. It is Redis-compatible and provides microsecond reads, low single-digit millisecond writes, and enterprise-grade security.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon MemoryDB the way a machine reads it — 87 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon MemoryDB scores 43.6/100 (developing), with a separate agent-readiness read of 25/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Amazon MemoryDB's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-memorydb/"
title="Amazon MemoryDB on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-memorydb.svg"
alt="Amazon MemoryDB Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/amazon-memorydb/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-memorydb/"
title="Amazon MemoryDB on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-memorydb/card.svg"
alt="Amazon MemoryDB Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Amazon MemoryDB
Each block below is one kind of artifact we hold for Amazon MemoryDB. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon MemoryDB ACLs API
The ACLs API from Amazon MemoryDB — 1 operation(s) for acls.
Amazon MemoryDB Clusters API
The Clusters API from Amazon MemoryDB — 1 operation(s) for clusters.
Amazon MemoryDB EngineVersions API
The EngineVersions API from Amazon MemoryDB — 1 operation(s) for engineversions.
Amazon MemoryDB Events API
The Events API from Amazon MemoryDB — 1 operation(s) for events.
Amazon MemoryDB NodeTypes API
The NodeTypes API from Amazon MemoryDB — 1 operation(s) for nodetypes.
Amazon MemoryDB ParameterGroups API
The ParameterGroups API from Amazon MemoryDB — 1 operation(s) for parametergroups.
Amazon MemoryDB ReservedNodes API
The ReservedNodes API from Amazon MemoryDB — 2 operation(s) for reservednodes.
Amazon MemoryDB Shards API
The Shards API from Amazon MemoryDB — 1 operation(s) for shards.
Amazon MemoryDB Snapshots API
The Snapshots API from Amazon MemoryDB — 2 operation(s) for snapshots.
Amazon MemoryDB SubnetGroups API
The SubnetGroups API from Amazon MemoryDB — 1 operation(s) for subnetgroups.
Amazon MemoryDB Tags API
The Tags API from Amazon MemoryDB — 1 operation(s) for tags.
Amazon MemoryDB Users API
The Users API from Amazon MemoryDB — 1 operation(s) for users.
Scroll within the panel for all 12 ·
Postman Collections 12
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Amazon MemoryDB ACLs API
POSTMANScroll within the panel for all 12 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAmazon MemoryDB ACLs API
OPEN COLLECTIONAmazon MemoryDB ACLs Clusters API
OPEN COLLECTIONAmazon MemoryDB ACLs EngineVersions API
OPEN COLLECTIONAmazon MemoryDB ACLs Events API
OPEN COLLECTIONAmazon MemoryDB ACLs NodeTypes API
OPEN COLLECTIONAmazon MemoryDB ACLs ParameterGroups API
OPEN COLLECTIONAmazon MemoryDB ACLs ReservedNodes API
OPEN COLLECTIONAmazon MemoryDB ACLs Shards API
OPEN COLLECTIONAmazon MemoryDB ACLs Snapshots API
OPEN COLLECTIONAmazon MemoryDB ACLs SubnetGroups API
OPEN COLLECTIONAmazon MemoryDB ACLs Tags API
OPEN COLLECTIONAmazon MemoryDB ACLs Users API
OPEN COLLECTIONAmazon MemoryDB API
OPEN COLLECTIONScroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Memorydb Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Memorydb Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Redis Compatibility
Fully compatible with Redis and Memcached data structures, APIs, and commands.
Durable In-Memory Storage
Multi-AZ transactional log ensures data durability without sacrificing performance.
Ultra-Fast Performance
Microsecond read and low single-digit millisecond write latency at scale.
Cluster Management
Create and manage MemoryDB clusters, shards, and replicas with ease.
Snapshot and Restore
Create point-in-time snapshots for backup and restore operations.
Access Control Lists
Fine-grained access control with user-based ACLs for security.
Multi-Region Clusters
Deploy clusters across multiple AWS regions for global low-latency access.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon MemoryDB API Rules
SPECTRALAmazon MemoryDB API Rules
SPECTRALJSON Schema 9
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ACL
JSON SCHEMACluster
JSON SCHEMACreateClusterRequest
JSON SCHEMADescribeClustersResponse
JSON SCHEMAParameterGroup
JSON SCHEMASnapshot
JSON SCHEMASubnetGroup
JSON SCHEMATag
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 9 ·
JSON Structure 9
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Memorydb Api Acl Structure
JSON STRUCTUREMemorydb Api Cluster Structure
JSON STRUCTUREMemorydb Api Create Cluster Request Structure
JSON STRUCTUREMemorydb Api Describe Clusters Response Structure
JSON STRUCTUREMemorydb Api Parameter Group Structure
JSON STRUCTUREMemorydb Api Snapshot Structure
JSON STRUCTUREMemorydb Api Subnet Group Structure
JSON STRUCTUREMemorydb Api Tag Structure
JSON STRUCTUREMemorydb Api User Structure
JSON STRUCTUREScroll within the panel for all 9 ·
Examples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Memorydb Api Acl Example
EXAMPLEMemorydb Api Cluster Example
EXAMPLEMemorydb Api Tag Example
EXAMPLEMemorydb Api User Example
EXAMPLEScroll within the panel for all 9 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservices Session Management
Store session data with ultra-low latency for modern microservices applications.
Real-Time Leaderboards
Maintain sorted sets for gaming leaderboards and ranking systems.
Caching Layer
Use as a durable caching layer to reduce database load and improve response times.
Pub/Sub Messaging
Build real-time messaging and event streaming with Redis pub/sub patterns.
Resources
Every other property we hold for Amazon MemoryDB — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-memorydb · machine-readable index on apis.io
This is an independent, third-party profile of Amazon MemoryDB, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.