v2.1.0 Sequence for extra reliability

All v2 users should upgrade.

I'm a perfectionist but I hate needless complexity. Without giving up my stateless events, I've eliminated the small risk that the original backup's retention period might be shortened before the second copy starts.

Instead of starting both copies to the backup account and letting AWS decide the order, v2.1.0 sequences them: copy to backup region → copy within resource region → schedule original backup for deletion. Steps are contingent and failure stops the rest.

More troubleshooting and security tips have been added to the ReadMe.

---

v1 users should review February, 2026 News, update backup plans, and decide whether to upgrade or retire Backup Events.

AWS Backup, RDS and Aurora now support copying a backup to a different account and region in one step! Now that you can achieve an other-account, other-region backup with a copy step in a backup plan, Backup Events is exclusively for on-demand backups, which don't allow a built-in copy step.

A new Terraform module is provided for deployment at scale. It creates a CloudFormation StackSet.

The LogsRetainDays parameter has been renamed to LogRetentionInDays and the two AWS Lambda functions now share one log group. OnlyResourceAccountId has been removed. OrgId has been removed because it is now obtained through an IAM policy variable. Both Lambda functions are now housed in the resource account(s) and region(s). Sample vaults are the only resources potentially installed in the backup account.

Failed on-demand backup and copy jobs are now tracked in the error queue.

v2.0.0 1-step copy & Terraform!

All users should review February, 2026 News in the ReadMe, update backup plans, and decide whether to upgrade or retire Backup Events.

AWS Backup, RDS and Aurora now support copying a backup to a different account and region in one step! Now that you can achieve an other-account, other-region backup with a copy step in a backup plan, Backup Events is exclusively for on-demand backups, which don't allow a built-in copy step.

A new Terraform module is provided for deployment at scale. It creates a CloudFormation StackSet.

The LogsRetainDays parameter has been renamed to LogRetentionInDays and the two AWS Lambda functions now share one log group. OnlyResourceAccountId has been removed. OrgId has been removed because it is now obtained through an IAM policy variable. Both Lambda functions are now in resource accounts. The only resources potentially installed in the backup account are the sample backup vaults.

Failed on-demand backup and copy jobs are now tracked in the error queue.

New, advanced optional parameters have been added.

v1.1.0 Python 3.14

Upgrade when time permits.

This release updates the Lambda runtime from Python 3.13 to Python 3.14 . AWS released the new runtime on 2025-11-18 and will mark both the old and new runtimes deprecated on 2029-06-30 . There are no relevant changes, but see the Python 3.14.0 release notes and the AWS Lambda Python 3.14 runtime release notes for general information.

The ReadMe reflects a 2025-10-30 improvement in AWS Backup, and in the underlying RDS and Aurora APIs, allowing one-step copying of a database backup to a different account and region. Backup Events remains useful for RDS and Aurora because it places copies in two regions, not just one, in the backup account. It also automates the copying of on-demand backups. Only backup plans (scheduled) support built-in CopyActions.

v1.0.0 Initial Release

Hope it's useful. Enjoy!