Menu

1 / 4

Aurora PostgreSQL Backups at Scale, Part 1: Designing AWS Backup Across Multiple Accounts

DEV Community: terraform·Pranay Ravi·13 days ago
#yFxkAIBq
#devtoterraform#devto#dev#backup#policy
Reading 0:00
15s threshold

AWS Backup + AWS Organizations lets you define Aurora PostgreSQL backups once and stamp them into every account. But the org policy won't create your vaults or IAM roles, continuous backup quietly takes over RDS's native backups, Aurora silently ignores cold-storage settings, the default aws/rds key blocks cross-account and air-gapped copies, and your 5-6 year old snapshot will outlive its PostgreSQL version. Here's how we designed around all of it.

Every Aurora cluster has backups turned on from day one. That's the trap: "it's backed up" becomes a sentence nobody verifies.

When you run Aurora PostgreSQL across 80+ AWS accounts, multiple regions, and retention measured in years, the real questions are:

Who owns the backup configuration?

Where does the copy live if a region goes dark?

Can an admin (or an attacker with admin) delete it?

Will a seven-year-old snapshot actually restore?

This is part 1 of a series. Part 1 = design. Part 2 covers monitoring and reporting failures.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.