> ## 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.

# Memorystore for Redis

> Memorystore for Redis APIs with Cloud Adapter.

This page describes how Memorystore for 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 |
| ----------- | ------- |
| AWS         | API     |
| Azure       | API     |

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 Memorystore for Redis with its adaptation on each target.
A dash means this profile does not state the capability for that target.

### Cloud Adapter

| Capability   | Memorystore for Redis | AWS  | Azure |
| ------------ | --------------------- | ---- | ----- |
| API coverage | full                  | high | high  |

## On AWS

### ElastiCache

| Operation                           | Area    | Support      | Depth        | Notes                                                                                                                                               |
| ----------------------------------- | ------- | ------------ | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Token-based authentication provider | Connect | Out of scope | Full surface | The two clouds issue authentication tokens differently. The client must use the target's credential provider, and the build identifies that change. |
| Engine name and version             | Control | Partial      | Common       | The target runs Valkey. Protocol compatibility is preserved, but engine names and versions change; the build identifies the target version.         |
| Transport encryption                | Control | Supported    | Most usage   | Connections use the target's transport encryption.                                                                                                  |
| instances.create / delete / update  | Control | Supported    | Common       | The instance becomes an ElastiCache cluster with mapped capacity and a selected Valkey version; source engine and version names change.             |
| Cache wire protocol                 | Data    | Supported    | Common       | The client keeps the same cache protocol and commands when connecting to Valkey.                                                                    |

A Memorystore instance becomes an ElastiCache cluster running Valkey. The client protocol and commands remain the same, while engine names and version strings change. The build identifies how a specified source version maps to the target.

### Client and engine behavior

The adapter applies cache-management settings while the target engine answers cache commands. Keep the client's expectations about topology, numbered databases, TLS, and authentication aligned with the selected target. Engine compatibility does not make source token providers interchangeable.

### Cache cutover

Prepare the target endpoint and credentials before switching clients. Rebuild disposable entries from the application's source of truth, or arrange an explicit data transfer when keys and expiry times must survive. Test reconnects and retried commands after failover.

### Compatibility differences

Token-based authentication also requires a client change because the two clouds issue credentials differently; the build identifies that requirement.

## On Azure

### Azure Managed Redis

| Operation                           | Area    | Support      | Depth        | Notes                                                                                                                                                                                                   |
| ----------------------------------- | ------- | ------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customer-managed encryption at rest | Control | Partial      | Full surface | The build shows the target's encryption-key configuration because key management differs between the clouds.                                                                                            |
| Transport encryption                | Control | Supported    | Most usage   | Connections use the target's transport encryption.                                                                                                                                                      |
| instances.create / delete / update  | Control | Supported    | Common       | The instance becomes a managed cache with mapped capacity and a target-compatible engine version. The build identifies unsupported size or version selections.                                          |
| Cache wire protocol                 | Data    | Supported    | Common       | The application keeps its cache protocol when connecting to the managed target.                                                                                                                         |
| SELECT and numbered databases       | Data    | Out of scope | Common       | Rejected at build time if the configuration uses multiple numbered databases. SELECT does not switch databases on this target, so their keys would share database zero and could overwrite one another. |

A Memorystore instance becomes an Azure managed cache using the same client protocol.

### Client and engine behavior

The adapter applies cache-management settings while the target engine answers cache commands. Keep the client's expectations about topology, numbered databases, TLS, and authentication aligned with the selected target. Engine compatibility does not make source token providers interchangeable.

### Cache cutover

Prepare the target endpoint and credentials before switching clients. Rebuild disposable entries from the application's source of truth, or arrange an explicit data transfer when keys and expiry times must survive. Test reconnects and retried commands after failover.

### Compatibility differences

The build rejects configurations using more than one numbered database. On this target, SELECT does not switch databases: all keys remain in database zero. Deploying such a configuration could make previously separate keys overwrite each other.

## 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.