Hi Medplum team! Checking if there's been any movement on supporting [ElastiCache Serverless](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/WhatIs.html#WhatIs.Overview). I saw the [2024 thread](https://discord.com/channels/905144809105260605/1295366782089166939) where it wasn't on the roadmap and wanted to check in since it's been a couple years and things may have changed. For context, we're in the process of moving over to Serverless and would like to migrate Medplum as well to get auto-scaling and better multi-availability-zone support. From reading the source, the only real blocker seems to be the [BullMQ queue names](https://docs.bullmq.io/bull/patterns/redis-cluster). Serverless is internally cluster-mode, so all of a queue's internal keys need to land on the same shard, which requires wrapping the queue name in {}. Without that, the queue breaks because it touches keys spread across shards. Everything else looks compatible. Is this something you'd consider supporting?

@amandamcgivern I've filed an issue for this - https://github.com/medplum/medplum/issues/9412. We'll get this to the core eng team for prioritization. Just want to set expectations that there is no guarantee this will get prioritized any time soon.

Thanks @Ian Plunkett! Totally understand about the prioritization, I'll track the issue