Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
494 results found
-
Determine programmatically if maintenance includes server version upgrade
Recently, Atlas introduced a feature that shows a cluster will have its MongoDB server version upgraded to the next dot version. This is displayed on the cluster card in the UI. However, this information is not surfaced in the Activity Feed or through any maintenance endpoints in the API. We would like to be able to identify when maintenance includes a MongoDB server version upgrade and do so programmatically.
3 votes -
Need static private ip for cluster nodes
Please see details in https://support.mongodb.com/case/00682480
3 votes -
Create alarms base on events + Add control policies
Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.
The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...
For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal3 votes -
Expose Collection TTL in the UI
It is very difficult to discover the TTL of a given collection. It would be great if the TTLs for each collection was visible in the collection UI.
3 votes -
Option to configure an on-prem hidden replica set member for an Atlas replica set
As described in https://docs.mongodb.com/manual/tutorial/configure-a-hidden-replica-set-member/, on-prem mongodb deployments allow to configure a hidden replica set members which are good for workloads with different usage patterns from the other members in the replica set. It would be useful to have similar functionality for Atlas replica sets.
In fact, to elaborate, being able to configure an on-prem hidden replica set member for an Atlas replicaset will help in meeting regulatory requirements where organisations are required to host a near real time mirror of data on on-premises.3 votes -
export list of database users
For audit purposes, I would like to have an export function to create a list of database users. The current view of database access contains the name and the associated roles. Having this information as a csv or pdf file would make it easier to deliver this access information to compliance teams.
3 votes -
Have the ability to configure cache_size
I'd like to see the ability to modify the cache size setting for a given cluster. MongoDB has a straight forward pattern of using 50% of the memory for cache size. However, Atlas has scaled that down to (RAM - 1 GB) / 2. Apparently that was done to allow for extra memory for other Atlas features like BI Connector and Atlas Search. However, we currently aren't using those features, so we're stuck with the lower cache size.
It would be great to have the ability to get the most of our servers instead of being limited based on logic…
3 votes -
Allow triggers to be tested locally
Our team uses and loves Stitch/Realm triggers. We've got them wired up so that we can update them from a bash script. They work well, but they are hard to debug -- it'd be nice if there was a CLI option to test them against a local mongodb instance.
3 votes -
Allow 'Download Logs' for user that is not a Project Owner but Project Data Access Read Only or Project ReadOnly
Currently in order to allow a user to download logs, it is necessary to make that user Project Owner. In a situation when a user outside the company is invited to review the project, it is not possible to grant such high level role when the access needed is only to look at logs. Project ReadOnly or Project Data Access ReadOnly should be sufficient to access logs, if the user is also granted atlasAdmin@admin access to Database
3 votes -
It would be great to have a tool with historical data about database and collection.
It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.
3 votes -
Live Migration Should Include Database User, Password and Role Information
Please provide the option to include database username, password and role information during a Live Migration. DBAs often do not have direct access to database credentials and have to collect them from the various development teams.
3 votes -
Add SHA-256 as Digest Authentication Algorithm for API
For compliance with NIST and other standards, it would be preferred to use SHA-256 as the algorithm for digest authentication for the public API as opposed to the currently implemented MD5.
3 votes -
Support for AWS KMS CMK per cluster (instead of on a project level)
Hi Team,
Currently, we have KMS CMK configuration available on the project level.
We are hoping to see if that can be changed on cluster level.Reason: Once we update the key, all the clusters will get re-encrypted with new key, but snapshots will not be re-encrypted with the new key.
For any reason, if we need to restore snapshot of one particular cluster, we will need to update KMS key with the old one, which impacts all clusters to get re-encrypted and then only can restore.Hence we believe cluster level KMS setting would be beneficial in such a…
3 votes -
Misleading error message when connecting to MongoDB Atlas with wrong password
When you connect to MongoDB Atlas from your application with wrong password using Mongoose, you get error message:
"Could not connect to any servers in your MongoDB Atlas cluster. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://docs.atlas.mongodb.com/security-whitelist "
even though your IP address is whitelisted.
Very frustrating and misleading error message, please fix this!!
3 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.
3 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 -
Add Category for Stitch
No category for Stitch in the ideas portal.
3 votes -
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 -
Requesting database wise billing data in a shared cluster
Currently we developing a portal to provide cost details to each customer who are using our platform. We have shared clusters in out pre environment and need to calculate cost for each customer for lower environment.
Better if you can provide an API call to get this database wise cost details.
3 votes
- Don't see your idea?