Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
471 results found
-
Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
11 votes -
Ability to create and update database triggers via API
It would be really usefule to have the ability to create and update database triggers via the API. Currently, updates to triggers cannot be integrated into our testing and deployment process because the only way to update them is manually through the interface.
4 votes -
M30 Cluster Tier option with 4 CPUs
There is a gap in the Cluster Tiers for clients that have high CPU requirements but lower disk space requirements. We run on a M30 Cluster where we max out the CPU when running aggregations, we use little of the available disk and do not want to move to a M40.
6 votes -
Alerts "Users do not have two-factor authentication enabled" should name violators
In the email for alerts of type "Users do not have two-factor authentication enabled" it would be helpful to see the user id of the “violator” (user which does not have two-factor authentication enabled), so that I don’t even have to click and log in to Atlas.
Maybe this could be make optional, if there are privacy/security concerns about sending around the user ID in cleartext.
1 vote -
Increase the Contrast of the Delete Document Button
The delete button with low contrast is the one that appears after you click the delete icon on for a document on the collections screen.
The button text is white on a pink background.
See attached file.
It is hard to see the button.1 vote -
Creating cluster specific network Access rules
I am running several clusters while one of them is for the main product we run extras to have consistent data between our test deployments issue is while we are running we change or deploy multiple servers and adding all these servers one by one for testing is not convenient not to mention we use our personal computers as well so we are opening a connection from all IP addresses. When we do that our main server also opens for every IP address which is not good.
2 votes -
Expose oauth apps to let other services integrate with Atlas
Expose oauth apps to let other services integrate with Atlas, this way other platform can integrate with atlas for provisioning a mongodb instance.
It would allow for a lot of opportunities for developers like automatic mongodb provisioning for a deployment platform
Right now if you deploy with platforms like Zeit or Heroku you have to create a mongodb database and whitelist the right iP manually
1 vote -
Include cluster node list in getOneCluster
Include cluster node information for all nodes in the cluster in the response JSON for the getOneCluster API call. As hostnames are needed for other API calls, there ought to be a better way to get cluster node names.
5 votes -
Integrate Netework Access IP Whitelist with GitHub Actions
I'm trying to setup CI for my project using GitHub actions, while restricting Network Access. The problem is that GitHub's machines have weekly changing IPs: https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#ip-addresses-of-runners-on-github-hosted-machines
Is there any way to automatically integrate that list of IPs in the Network Access IP Whitelist? This feature would benefit all users of GitHub Actions.
2 votes -
There should be a way to try MongoDB beta versions in Atlas
As we move into a more stable version of testing the 4.4 beta it would be useful to allow beta-testers to spin up a cluster with the beta version of MongoDB. Right now beta testers have to download MongoDB which means for some of the more exotic server features in 4.4 they have to build a sharded cluster or replica set. This would be much easier to do in Atlas.
1 vote -
Make a more realist design, with hack themes, and fancy UI
Please look at the images, try to make similar UI, it would improve a lot the productivity
1 vote -
Administrate user rights for the Billing area
Hi.
We would like to have the possibility to administrate user rights also for the Billing area. In order to restrict all users seeing the invoices and to give this right only to particular people who are directly responsible for it. Please consider such feature for the next releases.84 votes -
Enable live migration tool to work with Global cluster configuration enabled
Currently, there is no Live migration tool option while enabling Global Cluster Configuration in Atlas. Please treat this ticket as a FEATURE ENHANCEMENT REQUEST to make this happen.
3 votes -
Atlas maintenance Notification should include description of maintenance
Whenever Atlas wants to do maintenance, it is sending email alert about the timing of maintenance. In addition to that we are requesting information about the nature of maintenance also like Mongo patching , BI connector upgrade or increasing no of connections etc. This will give us the information about the work and we can broadcast the same to our counterparts so that they can also use the product efficiently.
29 votes -
Add Category for Stitch
No category for Stitch in the ideas portal.
3 votes -
Stitch CLI error messages - account/publicApi redirect fails
Stitch CLI error messages are obsolete.
I'm having difficult with connecting to a Stitch app and the 403 forbidden returns a message to check https://cloud.mongodb.com/v2#/account/publicApi but it redirects to /overview.
1 vote -
Show billing amount on top all the time
Would be nice if I can see my current billing on top all the time, even in Atlas, like it used to be before UI change. Thanks.
1 vote -
Support multiple LDAP servers and TLS connection options
When integrating my Atlas project with an LDAP service, we want to specify multiple LDAP servers rather than just one, and to specify options for the TLS connection such as allowing invalid hostnames. Both of these can be done in self-managed MongoDB Enterprise.
1 vote -
Vanity URLs for projects and clusters
Right now URLs for mongodb clusters are generatd by MongopDB. For the clusters I create it would be much easier to remember and distribute if I could create a canonical name per project and have each cluster member have its named assigned by the cluster.
So instead of demodata.rgl39.mongodb.net I could use demodata.joedrumgoole.com.
3 votes -
Terraform for LDAP user/groups
We'd love to be able to create LDAP user and group accounts in Atlas via terraform. The existing mongodbatlasdatabaseuser resource doesn't support LDAP, so we are forced to use the API to create those users and groups.
3 votes
- Don't see your idea?