Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
435 results found
-
Control IP Access list for project-only API keys at the project-level exclusively
When setting up API keys as a project owner, you only get one opportunity to manage the access list without getting an Organization Owner to modify it thereafter.
This creates a bottleneck where users need to ask for their API key access list to get changed (or alternatively make a new keypair, and have the API Keys list cluttered).
If a key is only being used in one project, it should be allowed by the project owner to update the access list at any time since there is no risk of it affecting the organization.
3 votes -
Deploy Custom Role to specific clusters only.
You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.
Can you extend this functionality to "custom role" also %
3 votes -
Warm up cache automatically when there is any server/node restart events
Usually it takes hour or so for the cache to warm up depending on the data size when an server restart scenario occurs ( increasing the tier / storage etc). And there are alternatives like running cache warm up queries to bring the nodes up to speed .
However if this cache warm up should be inherent and automatic for the server restart scenarios .
3 votes -
Support Linode as a cloud service
Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.
3 votes -
Add a simple log filter in the Atlas log API call
In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.
So people don't have to download large quantity of log messages that they don't need.
For example the the NETWORK log message between replica-set members.
3 votes -
Improve handling of ROLLBACK state
Recently we had a member of a replica set in a sharded cluster enter
ROLLBACKstate. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members inROLLBACKstate.Fortunately for us the writes which had been reverted were not critical and we were fine with that. However, this could have resulted in serious data loss which could have gone unnoticed until a customer reached out to us.
The handling of a situation like this one should have been much better and more user friendly. We should have…
3 votes -
Access key expiration date
We would like to have option set expiration date time while creating API access keys and also ability to check expiration options through API.
3 votes -
Document Atlas Cluster Tier Performance Expectations
Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).
This information is currently available in the Atlas UI.
Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.
3 votes -
Improve Cluster Name Limits
Cluster names currently impose the following limits:
Cluster names shorter than 23 characters can't end with hyphen or dash (-)
Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.
Instead, we should either trim or replace the hyphen at the end of a 23 character name.
3 votes -
migration should check actual disk space used by source MongoDB
The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.
Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.
3 votes -
support external nodes
Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
- compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
- easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route3 votes -
geospatial
Could we please consider boosting MongoDB's geospatial capabilities by incorporating Turf.js into Atlas. I would hope this would be an integration similar to Lucene in that it exposes some functionality through the UI, and some through aggregation. It would allow us to gain a huge amount of functionality. https://turfjs.org/
3 votes -
Provide local ssd instances in GCP
In terms of throughput it would be great to be able to configure an Atlas cluster based on local ssd / nvme GCP VM instances.
3 votes -
configure IP whitelisting on database user level
enable the user creation to have the following option
authenticationRestrictions: [
{
clientSource: ["<IP>" | "<CIDR range>", ...],
serverAddress: ["<IP>" | "<CIDR range>", ...]
},
...
],3 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
3 votes -
Need static private ip for cluster nodes
Please see details in https://support.mongodb.com/case/00682480
3 votes -
Atlas Shard Management
Currently the Atlas UI only presents options for how many shards a cluster can have.
Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections
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 -
Renaming DATABASE without dump/restore
Hello,
after a discussion with a MongoDB architect during a consulting day, the rename of a database was possible in previous version of MongoDB but now, it's impossible without a dump / restore process.
We don't want use a dump/restore process to rename a database because it's use a lot of time.
Could you tell me why this feature was deleted ? and will it be possible in a future MongoDb version ?
thanks.
regards,
David.3 votes
- Don't see your idea?