Configuring reads to read replicas, and writes to primary node

I’m examining the production deployment documentation. I have a backend that needs to scale to 1K workflows / s.

I am evaluating the usage of AWS Aurora as the backing store for temporal. However, it can only scale its reads horizontally, not its writes. Therefore, I was wondering if there’s an option for me to configure temporal to perform its reads from the replica node and writes to primary node.

Temporal is a fully consistent service. So reads from a replica that returns stale information are not acceptable.

Would AWS Aurora with multi-master work?