Topstep’s migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey
Database Blog
This article describes how Topstep migrated 53 million cache keys from a single self-managed Redis OSS instance to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster using RedisShake and a DNS cutover strategy.
- Migrated from single-node Redis OSS 7.4 to Multi-AZ Valkey 7.2.6 with automatic failover and TLS encryption
- Used RedisShake in PSYNC mode for blue/green replication across AWS accounts via VPC peering
- Completed cutover with single Route 53 DNS change from A record to CNAME, requiring no application code changes
- Achieved read P99 latency of ~1.25ms and write P99 of ~0.5ms, down from 250ms P90 spikes
- Eliminated manual patching, backups, and failover recovery, freeing 1-2 engineer-days per month
- Implemented custom TLS certificate verification to support custom DNS hostname with ElastiCache endpoint
The migration removed Topstep's single point of failure, improved performance during nightly batch jobs, and shifted operational burden to AWS managed services while maintaining full rollback capability.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.