# Direct to S3 feature flags and backup-job path lifecycle > Source-anchored research for Direct to S3 feature flags and backup-job path lifecycle. Run status: COMPLETED. Parent: [MongoDB Backup and Restore](https://llms-explorer.com/tree/mongodb-backup-and-restore/) · 2 facets · 9 facts · page: https://llms-explorer.com/tree/direct-to-s3-feature-flags-and-backup-job-path-lifecycle/ ## How-to and procedures - Set mms.featureFlag.backup.d2s3 to enabled in the Ops Manager custom configuration to activate Direct to S3 Backup globally. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - Set mms.featureFlag.backup.d2s3 to controlled for project-level opt-in, then activate Settings > Beta Features > Backup D2s3 in the project. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) ## Facts and statements - After project activation, new eligible backup jobs use Direct to S3 from their first snapshot without per-job opt-in. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - Backup jobs that existed before feature activation keep their existing Direct to S3 setting; activation does not automatically change those jobs. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - An operator can enable or disable Direct S3 Backup for an individual job through Admin > Backup > Jobs, then save the change. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - The per-job Direct S3 Backup control appears only for jobs whose snapshot store is an S3 blockstore. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - For a sharded cluster, select Apply to all cluster members to enable Direct to S3 for every shard and the config server, then save. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - Ops Manager places uploadPath=AGENT_DIRECT_S3 in the backup cursor description, and the MongoDB Agent reads that value to select the job’s upload path. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md) - The MongoDB Agent freezes the upload path for a job. A snapshot already in progress completes on its original upload path; the documentation does not specify the effective boundary for every later manual toggle or flag revocation. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/ops-manager/current/core/backup-direct-to-s3.md)