# Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey

DevFeed: [Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/topstep-s-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey-123996.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/topsteps-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey/>)

Author: Gbeminiyi Abolarin

Published: 2026-11-09T16:59:06Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [cname](<https://devfeed.tech/tags/cname.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [migration](<https://devfeed.tech/tags/migration.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [tls](<https://devfeed.tech/tags/tls.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

## AI overview

Topstep moved about 53 million keys from a single-node Redis OSS 7.4 instance to a Multi-AZ Amazon ElastiCache for Valkey 7.2.6 cluster using RedisShake in PSYNC mode. Since its source version fell outside the managed migration's supported range and the team required a blue/green rollback path, it replicated commands across peered VPCs, validated key counts and application behavior, then cut over by changing a Route 53 record. The change took seconds; the source remained available during a soak period. Valkey's protocol compatibility avoided code changes apart from TLS configuration. Because the custom DNS name did not match the cluster certificate, Topstep kept CA verification enabled while validating against an allowlist of AWS endpoint names. The team reports automatic Multi-AZ failover, managed patching and backups, read P99 latency around 1.25 ms and write P99 around 0.5 ms, and 1-2 engineer-days per month freed from maintenance.

## Source excerpt

Topstep migrated roughly 53 million keys from self-managed Redis OSS to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster. Using RedisShake and a single Amazon Route 53 DNS change, the team completed a blue/green cutover in seconds with no application code changes beyond a small TLS configuration update.