This message was deleted.

IMO TF isn't a great tool for database administration. We looked at this and we're going with a script-based solution. I don't know your use case but I'd be more concerned about not having a human in the loop for a PITR.

Restoring is a simpler activity and can be done with terraform, the problem I see with custom scripts is maintainability and tribal knowledge. If the team is really good at documenting, script is probably a better choice. But you don't want to end up with a bunch of scripts that future team members are not able to figure out. That being said, maintaining terraform states is also a mess that will come up after you have a bunch of automation in place. Just make sure you account for that, and either of these will work fine.

Thanks @Mark Cheshier and @Vivek Dwivedi. I ended up going the route with AWS SDK/node route and I think it will be a much better choice as all of our developers know node as compared to only a handful of devs understanding Terraform.