Cross-region replication support for aws-aurora-postgres

[Juan A. (jaguer0)]

We're setting up Aurora PostgreSQL using the cloudposse component with a primary in us-east-2 and a secondary in us-west-2 for DR (Cross-region replication).

The aws-aurora-mysql component already supports this pattern with is_read_replica, primary_cluster_component, and primary_cluster_region, but aws-aurora-postgres doesn't expose any of the cross-region functionality

Is there a plan to bring aws-aurora-postgres to parity with the MySQL component on this & support static account map?

[Erik Osterman (Cloud Posse) (osterman)]

Great question — you’re not missing anything.

Today, aws-aurora-postgres doesn’t yet expose the same cross-region read replica pattern that exists in aws-aurora-mysql.

This is primarily a component gap rather than a limitation in the underlying modules, and bringing it to parity is very doable.

In general, updates to our components are driven by a combination of community contributions and customer demand. This isn’t something we have actively scheduled right now.

If you need this, the fastest path would be to extend the component following the same pattern as MySQL. We’re very open to contributions here and happy to review and merge a PR.

Drop PRs in #pr-reviews on SweetOps (cloudposse.com/slack)

[Juan A. (jaguer0)]

Thanks for the breakdown. We've got a few things ahead of it, but as we ramp into our Aurora setup we'll get a PR out to contribute back. Will drop it in #pr-reviews 🚀