In a perfect world, this makes sense. For us, we had an ElastiCache redis multi-AZ replication group whose primary was in the affected AZ. It refused to fail ov

In a perfect world, this makes sense. For us, we had an ElastiCache redis multi-AZ replication group whose primary was in the affected AZ. It refused to fail over, even though automatic failover was configured. Apparently there is no way to force this failover, even though people have been asking for such a feature for years. I'm curious what you would do in this situation, besides not using ElastiCache?