Replace Redis with AWS Valkey

[jimleroyer]

⚠Attention
Before switching to Valkey, ensure that Terraform support is integrated.

Description

As a system op,
I want to replace Redis with Valkey,
So that I get less cost for using it,
and aligning with the best AWS supported Redis fork.

WHY are we building?

Redis changed their license 6 months ago and the OSS community started to build forks out of it. The new license cost more for AWS (and their users indirectly), hence AWS built their own fork. Replacing Redis with AWS Valkey should be a drop in replacement.

WHAT are we building?

Changing Redis caching implementation.

VALUE created by our solution

Less cost and aligned with AWS solutions.

Acceptance Criteria

• No downtime (ideally) between the switch.
• Users have no perception of the change
• Valkey is used instead of Redis.
• Same features are retained and tested.
• Redis keys are migrated to Valkey during transition.
• Valkey should be distributed with at least 2 instances.

QA Steps

• Check the AWS Elasticache dashboard to verify Valkey is used.
• Connect to Valkey and try out the same Redis commands to check features.
• Monitory newly created keys in the new Valkey instance(s).

Additional information

• Valkey announcement

[ben851]

TF:
This functionality has been released in v5.73.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!