AdminBenjamin Cefalo
(Director, Product Management, MongoDB)
My feedback
-
5 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Hi, You can accomplish this today, there is a setting in the organization. See https://docs.atlas.mongodb.com/tutorial/manage-organization-settings/#require-two-factor-authentication
If you however are using Federated Identity or Google Auth, this setting doesn't apply.
-
2 votes
An error occurred while saving the comment During the restore process, we have the metadata of which CMK was used during the time the backup was taken. So even if the CMK used is not the active one, as long as the IAM User you have provided still has access to the key, i.e. you haven't deleted the key from KMS, we will be able to restore the snapshot.
-
1 vote
An error occurred while saving the comment Hi Josh, this is available today. You can restore a snapshot from one cluster in a project to a cluster in another project.
https://docs.atlas.mongodb.com/reference/api/cloud-provider-snapshot-restore-jobs-create-one/
-
2 votes
An error occurred while saving the comment Today you can achieve this from the IDP side by not giving everyone access to the application
Hello,
We are planning on building a new version of queryable for Cloud Backup but not with a tunnel. In the meantime, I would suggest provisioning a new cluster, restoring the backup, do what you need, and then tear it down. Cloud Backup restores are extremely fast. This would be the best way for the time being.