Hmmm, I think you have to figure out how to do your database backups anyway as trying to get a restorable backup out of RDS to use on another provider seems to be a difficult task.

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.")

▲ bdangubic 2 days ago | parent [-]

aws would never do that :) plus you can also do it in aws with like 75 clicks around UI which makes no sense even when you are tripping on acid

▲ happymellon a day ago | parent [-]

> 75 clicks

Well 2 commands...

  aws rds export-task create \
    --source-arn <SnapshotArn> \
    --s3-bucket-name <Bucket> \
    --iam-role-arn <Role>

Then copy it down

  aws s3 cp \
    <S3 Location> \
    <Local Dir> --recursive

The biggest effort would be then running the Apache Parquet to CSV tool on it.

▲

prmoustache a day ago | parent | next [-]

Those buckets and IAM policies and roles also have to be managed.

There are also turnkeys solutions that allow one to spin up a DB, setup replication and backups inside or outside of big cñoud vendors. That is the point of db kubernetes operators for instance.

▲

darkwater a day ago | parent | prev [-]

Plus the s3 bucket creation and definition commands, and the IAM role and attached policy commands. If you do all in the webUI it's not going to be 75 clicks either but 30 for sure.

	▲	happymellon a day ago \| parent [-]
		It could easily be 30 clicks. But creating an S3 bucket, an IAM role and attaching policies isn't 30 commands.