Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
158 results found
-
more information in AWS IAM audit logs
We are using MongoDB-AWS for authentication, and have set up the audit log to log events taken by AWS roles. However, there is insufficient information in the logs to identify who is doing those actions, as roles can be assumed by multiple people.
An example log line in the current audit log:
{ "atype" : "authenticate", "ts" : { "$date" : "2021-01-05T00:21:52.628+00:00" }, "local" : { "ip" : "192.168.248.203", "port" : 27017 }, "remote" : { "ip" : "172.31.0.5", "port" : 54195 }, "users" : [ { "user" : "arn:aws:sts::555555555555:assumed-role/developer-role/", "db" : "$external" } ], "roles" : [ {…4 votesThe full ARN including the user information is now captured in audit logs when AWS IAM authentication is used with assumed roles. This is a delayed update; the change was made in 2021. Thank you for your feedback to make MongoDB better.
-
Add option to create project without alerts
Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation
17 votesJust added in the latest version 1.1.1: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#with_default_alerts_settings
-
Vault Lock to protect Atlas Cloud Backups
We are currently looking for a solution to secure our Atlas backups.
Something similar to AWS Glacier Vault Lock [1] or a simple grace period before backups are deleted once and for all would be nice.
It would be amazing to protect the Atlas backups from being deleted.
Currently, if one of our Atlas admins was compromised, the damage for the company would be enormously high. So we need to implement measures against the final deletion of our most mission critical data.also mentioned in: [2]
[1] https://aws.amazon.com/de/blogs/security/amazon-glacier-introduces-vault-lock/
[2] https://developer.mongodb.com/community/forums/t/is-there-a-vault-lock-for-atlas-backups/1104110 votesHello,
I am pleased to announce that we have released our backup feature called 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.
-
AWS EBS gp3 Volumes
Please add support for the newly announced and already generally available AWS EBS feature. [1]
The top capability is: "The new gp3 volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. Customers looking for higher performance can scale up to 16,000 IOPS and 1,000 MB/s for an additional fee." [2]
That basically means decoupling storage performance from storage size.
It would eliminate all our IOPS pain as 3000k is more than enough for our usecase. Currently, we are slightly overprovisioning storage size in order to guarantee minimal IOPS performance.[1] https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/
[2] https://aws.amazon.com/ebs/general-purpose/17 votes -
Add Switzerland Regions
Hello, our product heavily relies on mongo atlas and we're very happy with it. However, several of our (corporate) clients would like their application data to be hosted in Switzerland (for compliance/data protection reasons). I would love the ability to setup a Swiss only Atlas cluster for those clients, but the closes options we have in Germany only. Either cloud provider will be fine (ideally Azure). Many of your (future) clients would certainly welcome this too (banks! luxury! healthcare! pharma! transportation! public services!) - thanks for listening :)
1 vote -
Allow modifying federation role mappings via API
We would like to use the new role mapping feature for federated authentication to assign Atlas roles based on LDAP groups assigned to our users.
However, we frequently create new projects programmatically and would need to manage the permissions to these new projects using role mapping. However, there is no public API available to manage role mappings programmatically. In addition, enabling role mapping disables the ability to manage roles for federated users with the API. So, at present, role mappings and permissions can only be managed manually through the UI.
We would like to request the ability to modify role…
26 votesWe are happy to announce that Federated Authentication Configuration can be now managed through Atlas Administration API. Please refer to API documentation for more information: https://docs.atlas.mongodb.com/reference/api/federation-configuration/
Please let us know if you have any feedbacks.
-
Atlas API Enhancements
Since we want to automate the user (de)provisioning for organizations and projects, we would like to see the following API enhancements:
Please enhance the Mongo Atlas API for the following functionalities:
- invite (existing mongo) user to organization (currently not possible)
- remove user from organization
- get invitation status from user
- cancel invitation for userThank you
8 votesThe work for invite management has been completed and added as endpoints to organizations and projects: https://docs.atlas.mongodb.com/reference/api/projects/ and https://docs.atlas.mongodb.com/reference/api/organizations/
-
Authentification on Azure (IAM)
Hello,
We absolutely need a more modern authentication method than using LDAPS to authenticate users against the MongoDB databases that we deploy with Atlas. When will we see a modern authentication service at this level? Ideally, we want cloud functionality equivalent to AWS IAM but on Azure.
15 votesYou can now access Atlas Clusters through Microsoft Entra ID using MongoDB Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).
Thank you for your feedback.
-
efficient backup restore between MongoAtlas Projects
Hello,
currently, when we restore a SNAPSHOT from one cluster to another cluster in the same MongoAtas Project (example from "production" project to "production" project), this is very efficient (several minutes).
On the other hand, if we execute the same backup restore from one cluster to another cluster on another MongoAtlas project (example : from "production" project to "staging" project), this is much less efficient and it will take several hours (instead of several minutes above).
This is very efficient in the same MongoAtlas project because it will use cloud provider system using hard disk management.
Could you improve efficiency…
11 votesWe have released the ability to enable faster restores across projects in AWS for Atlas Backups! You can enable faster cross-project restores by clicking the “Faster Restore” button in the cluster Backup page.
Learn more here
-
Enable AWS EBS Fast Snapshot Restore (FSR) on Atlas
To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore
https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/
This would allow the disk to have full performance as soon as available.
3 votesWe have released the ability to enable faster restores across projects in AWS for Atlas Backups! You can enable faster cross-project restores by clicking the “Faster Restore” button in the cluster Backup page.
-
hide index
Add a button/toggle to Hide and Unhide an Index from the Data Explorer/Indexes display for a 4.4+ deployment.
16 votes -
Update all clusters to have MongoDB 4.4
I hope that all clusters will be able to use MongoDB 4.4 - including shared ones like M0
1 vote -
Support GCP IAM for Cluster Authentication
Achieve feature parity with AWS IAM cluster authentication support.
85 votesYour applications can now access Atlas Clusters with Google Service Accounts using MongoDB Workload Identity Federation (https://www.mongodb.com/docs/atlas/workload-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).
For your workforce access, we recommend to use Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/) with your corporate identity provider.
Thank you for your feedback.
-
Tag/label project
Give the ability to tag/label a project
8 votes -
Expose minRetentionHours oplog option
MongoDB 4.4 introduces the new minRetentionHours for the oplog.
Currently this option is not exposed in the Atlas UI and the command replSetResizeOplog is not allowed.
Would be nice to have this option available in Atlas (and be accessible via Terraform too)8 votes -
Azure storage support
Can you add support for storing the archive data in Azure Storage (instead of AWS S3 only), in a chosen by customer region (e.g. same region where the MongoDB cluster is running)?
18 votes -
Change M10+ cloud providers
I would like to be able to change the cloud provider and region of a M10+ cluster.
It would be nice also to have a per-cluster connection string that does not depend on the cloud provider. So we can change the provider and region without changing the application settings.3 votesWe have recently released multi-cloud clusters on Atlas: https://www.mongodb.com/blog/post/introducing-multicloud-clusters-on-mongodb-atlas
This unlocks the ability for you to seamlessly migrate workloads across cloud providers!
Give it a try and let us know what you think!
-
Allow Realm to stream application logs to Splunk (or other third party services)
It would be ideal if there was some native way to send Realm application logs to Splunk (and other third-party log aggregation services), instead of having to build an application in a separate environment to poll this API endpoint (https://docs.mongodb.com/realm/admin/api/v3/#logging-apis) and push logs to Splunk from there.
7 votes -
Allow custom date range to be submitted in Query Profiler
Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.
It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.
16 votesThe Query Profiler in Atlas now supports custom date ranges going back up to 7 days. I will now be closing this feature as complete. Thank you!
-
Ability to delete account
I really need to delete my account as this is not what I am looking for.
5 votesHello,
I just want to update this ticket that self-serve account deletion is supported since August 2021. Please note that once you delete your Atlas account, you cannot use the same email to create a new Atlas account.
- Don't see your idea?