No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I think in Aurora, you use a readerEndpoint for read-only access to a non-read replica cluster.

You can create a whole new cluster that is a read replica of another cluster...

But (as I understand it) Aurora manages the instances within a cluster, you don't choose some to be read replicas.

okay, so If I wanted 5 read replicas, would I need to create 5 reader endpoints?

As I understand it, you don't worry about replicas within the cluster. Give (e.g.) 10 instances to Aurora, and it sorts the read-instances itself, if it needs them. You just connect your readonly applications to the (one) readerEndpoint, and your write applications to other endpoints. Then let Aurora work its ML-type analysis and it figures it all out for you.

Note that this is based on a few posts I've read, I've never used Aurora.. can't wait to try though...

thanks for the info -- I need to do some research it sounds like.  :slightly_smiling_face:

Thanks Tenwit -- adding multiple ClusterInstances  was what I needed.  Thanks for the heads up.