Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
138 results found
-
9 votes
-
Terraform resource to add users to an existing team
You can automate this :) https://docs.atlas.mongodb.com/reference/api/teams-add-user/
1 vote -
1 vote
Version 0.9.0 of the provider now supports arm64.
-
Allow creation of a free cluster (M0) through the API
Through the API it is possible to create several projects within an organization, and as far as I understand you offer 1 free cluster per project....
So, why not create the M0 cluster also through the API? (considering the limitation of only 1 for the project, of course)
This would be of great help for integrations that automatically generate small test environments for certain applications that plan to use atlas as a database server.
4 votesHi Bruno,
Thank you for taking the time and raising this feedback. We believe it’s crucial to support you and development teams in integrating MongoDB with your CI / CD pipeline. For example by enabling generation of small test environments using M0 clusters.
With that in mind, we’re happy to share that this capability has been recently added to our Public APIs as well as MongoCLI. To learn more and read about other new capabilities we’ve added, visit https://docs.mongodb.com/mongocli/stable/release-notes/Thank you again for sharing your idea and keep it coming.
All the best,
Jakub -
Security Key (FIDO2) MFA option
Please enable security key (e.g. https://www.yubico.com/gb/product/yubikey-5c-nfc/) option for MFA. Ideally using FIDO2 protocol
9 votesMongoDB added webAuthn support as an MFA method. Please use "Security Key/Biometric" MFA. option to use it with your FIDO2 keys.
https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/
-
Support for tagging clusters in Atlas
Please allow tagging at a cluster level. This will help in storing related metadata if required.
4 votes -
Support the regions parameter of a network peering container
In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).
See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters
2 votesThis work is completed and in v0.9.0 of the provider.
-
Need access to the REST API for IdP Federation
Currently all IdP federation set up must be done in the Atlas GUI. This prohibits scripting the setup of IdP organization and role mapping for new projects.
Customers can prefer setting this up via a scriptable Rest API interface for a new project. Everything else about the project has an API that is currently used to create projects and deploy clusters. Authentication is important part of the process and currently requires manual set up through the GUI.
3 votes -
Add resource to allow attachment of roles to mongodbatlas_cloud_provider_access
The need to do two applies to completely configure the
mongodbatlas_cloud_provider_accessresource should have never seen the light of day. I would like to see an additional resource that could attach a role to amongodbatlas_cloud_provider_accessafter it has been created. Then you could use the attributes in themongodbatlas_cloud_provider_accessresource to create the role, then attach the role to it using theaccess_role_attachmentresource.9 votesCloud Provider Access in v0.9.0 now has a single apply method and the original two apply method.
-
Add Test Failover permissions to the Project Cluster Manager role
Add Test Failover permissions to the Project Cluster Manager role.
Use Case:
We'd like to have folks with this permission without also allowing them to modify Project membership and all the other permissions that come with being an Owner.4 votes -
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/
-
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 -
Tag/label project
Give the ability to tag/label a project
8 votes
- Don't see your idea?