MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Completed
Categories Atlas
Created by Guest
Created on Oct 11, 2022

RELATED FEEDBACK

immutable backups

currently Atlas - MongoDB backup are stated to be immutable, however, that is not true because there is no object lock on the s3 bucket. We would like to request adding the option to have an object lock on the s3 bucket that our snapshots are located on which will make sure that the snapshots can only be deleted by retention and not modified or deleted by anyone else. This is to line up with WORM compliance while dealing with financial data. https://www.telemessage.com/what-is-worm-compliance-and-when-is-it-needed/ https://aws.amazon.com/blogs/storage/protecting-data-with-amazon-s3-object-lock/
  • ADMIN RESPONSE
    Aug 1, 2025
    Hello, I am pleased to announce that we have released our backup feature called Backup Compliance Policy ( https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/ ) , that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas. Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more. With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes. Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.
  • Attach files