I have clients who have had point in time recovery requirements not easily met by individual object versions. If versioning meets your requirements then you don't need AWS Backup. In a Reddit thread, user zilch321 compares AWS Backup with S3 versioning: This will help provide a mechanism to protect data in your data lake against accidental deletions and malicious re-encryption. Using AWS Backup for Amazon S3 and its Backup Vault Lock feature, you can define data protection policies to create independent immutable backup copies of your data stored in an S3 data lake. Explaining how to automate and centrally manage data protection for S3, Sabith Venkitachalapathy, enterprise solutions architect at AWS, and Wali Akbari, principal solutions architect at AWS, write: The new option helps meet business continuity goals and targets three main use cases: applications that need point-in-time recovery of multiple objects, recovery of S3 content after an accidental deletion and backup and recovery solutions for enterprise data lakes. Continuous backups allow restore to any point in time within the last 35 days, periodic backups can be stored indefinitely and support frequencies of 1 hour, 12 hours, 1 day, 1 week and 1 month.

AWS Backup creates encrypted backup vaults that can be restored with an API request. To enable AWS Backup for S3, developers must create a centralized data protection policy, choosing between continuous and periodic backups, and assign it to the S3 bucket using tags or resource IDs. The new feature automates the backup and restore of application data on S3 and combines it with the backup of other services, including instances and databases.

Amazon recently announced the general availability of AWS Backup for Amazon S3, a managed option to centralize data protection for applications storing data on S3.

Amazon s3 for personal backup