There probably isn't a lot of fear with using RDS. They just do management for you, it isn't any fundamentally different technology that would cause heartache during a migration. Just stay away from Aurora if you care about this.

SQS: There's AWS MQ, which is based on ActiveMQ and supports AMQP. If you're going with a more CNCF-focused stack and want to use NATS, I'm not aware of any hosted options.

You don't even need to stay away from Aurora ince it's MySql/Postgres SQL API compatible.

You would just want to stay away from Aurora specific features like the one in OP.

Features like database rewind aren’t something that would be bound to your core app structure either. While you could structure business process’s around it, it’s more of a shit hits the fan restore scenario, not a daily or weekly action.

Replicating it on a different platform could also be fine with a combination of logical and physical backups.

Point-in-time database restores are a best practice that is provided by maintaining database write logs for the timeframe that you expect to have point-in-time restoration for. You don't have to use Aurora to get them, Aurora just has the clicky buttons to make it a clicky-button matter. Any serious DBA should know how to do this without Amazon's platform wrapping it up in a GUI.

We've had point in time restore for quite some time. Backtrack is different. It moves you to a different point using the same instance. Since we don't do destructive writes to blocks (it is log-structured storage), we can simply mark a portion of the log as "ignored". It is a server feature, not a UI enhancement.

For Aurora/RDS Postgres there's https://www.citusdata.com/ or https://www.heroku.com/postgres

There's Comcast Message Bus which is self-hosted API-compatible SQS, but I don't yet know how good it is:

https://github.com/Comcast/cmb