ok so from the docs I can read that:
When data is written to the primary DB instance, Aurora synchronously replicates the data across Availability Zones to six storage nodes associated with your cluster volume. Doing so provides data redundancy, eliminates I/O freezes, and minimizes latency spikes during system backups.
Which seems to be what you are suggesting.
But the problem is that when failover occurs, the former master becomes a read only node. In this state, the temporal history service (and other ones) cannot write anything to the node but they are still connected to the node …
What you are suggesting is that the only way to be able to work with mysql is to have some kind of synchronous master-master setup? Am I understanding it correctly?