Skip to main content
Springwinter provisions a Valkey cache directly in your AWS account using AWS ElastiCache. Valkey is an open-source, Redis-compatible key-value store, but ElastiCache Serverless requires a client with cluster-protocol support and TLS. A standalone-only Redis integration cannot connect unchanged. Your web servers and workers connect to it over TLS from within the same project’s network — no public exposure, no password required.

What Is Valkey?

Valkey is an open-source, community-maintained fork of Redis, licensed under BSD. It is wire-compatible with Redis clients and supports the same data structures: strings, hashes, lists, sets, sorted sets, and more. Springwinter provisions Valkey through AWS ElastiCache, so you get managed patching, automated failover, and CloudWatch metrics without running the infrastructure yourself.

Create a Cache

1

Open your project

Navigate to your project in the Springwinter dashboard and click Add resource.
2

Select Cache

Choose Cache from the resource type list. You will be taken to the cache configuration form.
3

Choose a storage limit

Select a data storage cap from 1 to 8 GB. This configures ElastiCache Serverless, not a node size. The cap is neither billed average usage nor a spending limit; request processing is charged separately.
4

Create

Click Create. Springwinter provisions the ElastiCache cluster in your AWS account. The cache status changes to Available once provisioning is complete, typically within a few minutes.

Connecting to the Cache

Once the cache is available, the connection endpoint appears in the Connection tab of the cache resource in your dashboard. The connection uses TLS on port 6379. No password is required — access is controlled at the network level, and only resources within the same project can reach the endpoint. Use the connection string as an environment variable so your application code stays portable:
The rediss:// scheme (double s) tells your Redis client to connect over TLS. No username or password is needed in the URL.
Use the primary cache endpoint with a cluster-aware client. These examples use the TLS URL above.
Use database 0. Multi-key commands, transactions and scripts can require keys in the same hash slot; use a shared hash tag such as {cart:123}:items and {cart:123}:total when appropriate. Cluster support in a library does not prove that an application or queue adapter supports it. Check the adapter before deploying. See AWS connection and cluster requirements, ioredis cluster configuration and redis-py clustering.
The cache is private to your AWS account’s network. It is not reachable from the public internet — only resources within the same project can connect.

API Reference

Create a Cache

Get a Cache

Update the Storage Limit

Change the memory allocation of an existing cache by sending a PATCH request:
Springwinter submits the new serverless data storage cap to AWS and saves the requested value. This PATCH does not return a new deployment workflow. AWS can still be applying the modification after the request returns; verify the cache in AWS before treating the new limit as active.

Metrics

CloudWatch metrics for your cache — including memory usage, connection count, and cache hit rate — are available from the Metrics tab in the dashboard or via the API:

Cost Estimate

Retrieve the current ElastiCache cost estimate and monthly run rate:

Delete a Cache

To remove the ElastiCache cluster from your AWS account:
Deleting a cache is permanent. All data stored in the cache is lost immediately. Update any environment variables that reference the cache endpoint before deleting, to avoid errors in your running services.