Earlier quoted context omitted.
> A few clicks. Getting through AWS documentation can be fairly time consuming.
Figuring out how to do db backups _can_ also be fairly time consuming. There's a question of whether you want to spend time learning AWS or spend time learning your DB's hand-rolled backup options (on top of the question of whether learning AWS's thing even absolves you of understanding your DB's internals anyways!) I do think there's value in "just" doing a thing instead of relying on the wrapper. Whether that's eas…
Backups that are stored with the same provider are good, providing the provider is reliable as a whole.
(Currently going through the disaster recovery exercise of, "What if AWS decided they didn't like us and nuked our account from orbit.")