Check the intended engine and the engine actually provisioned by PD AWS ElastiCache before describing a cache offering to customers. Redis OSS and Valkey are distinct engine selections; a familiar protocol or working client connection does not identify which one is running.

Review the saved configuration

1. Open the package’s Module settings and record Engine.
2. Review Engine version against that engine, not an example for a different engine.
3. Save and reopen the form to check the stored selection.
4. Review any accepted customer version choice as well as the default.
5. Have the AWS administrator confirm the actual engine and version on the resulting replication group before offering that configuration broadly.

Some installations can show a version list that is not appropriate for the selected engine. Do not select a Redis OSS version merely because it appears on a Valkey offering. If the form offers an AWS-default choice, use it only when you intend the provider default; if no suitable choice is available, keep the offering unadvertised before creating a service for that configuration.

Verify the result

For an existing controlled service, compare the actual AWS engine and version with the intended offering. A passing module connection test only lists replication groups. A ready billing service or a selected Valkey label does not by itself prove that the cache was created as Valkey.

Resolve a mismatch safely

Keep the original service, requested configuration and redacted Activity result. Compare the saved choices, accepted request and actual AWS engine/version. Changing an Engine default is not a migration of a live cache. Preserve the working application and data while planning any required replacement or migration; do not repeatedly press Create to make the existing resource match a dropdown.

See the PD AWS ElastiCache Blesta guide for related tasks, or explore PD AWS ElastiCache.