Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
create API keys that support linked orgs
It is possible to link multiple orgs to each other. It should therefore be possible to use a single API key to access all linked orgs.
5 votes -
Preserve Oplog upon storage downgrade in Azure
Oplog was wiped out upon storage downgrade from 128Gb -> 16Gb, even though the database size incl. oplog was less than 2-3Gb.
Please change the downgrade procedure to NOT wipe out the oplog.
This was tested/experienced on Azure.
2 votes -
Support GCP Private Services Access to Atlas
Hello,
this is a request to support Private Service Access for Atlas deployments on GCP. Today, our options with Atlas are IP access lists or VPC Peering. However, these options create downstream limitations for our organizations. Additionally, only one peering connection can be made per Atlas project, which also limits us.
Thanks
3 votes -
1 vote
-
docsexamined
in profile tab, there are only keysexamined, nreturned we can see.
If we have "docsexamined" , it would be good to check whether the queries are well tuned or not at first glance.1 vote -
Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.
Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.
But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.
2 votes -
API Key Expiration date
We have a security reqirement that secrets must expire after 2 years.
Therefore it would be awesome if MongoDB Atlas API Keys would support an expiration date.
Somethig similar exists for the IP Whitelisting. Here we have the option to remove IP Whitelist entries after er certain time period. But for API Keys it would be better to have an expiration date and keep the API Key in the list even if its expired.
In addition it would be good to have a daily notification once the expiration date is ahead less than 30 day.
3 votes -
Delete one (last)endpoint deletes private endpoint service
If no further endpoint is associated with Private endpoint service, making a call to api resource https://docs.atlas.mongodb.com/reference/api/private-endpoints-endpoint-delete-one/ will delete the endpoint as well as service.
1 vote -
1 vote
-
I'd like the ability to be on premise and burst into Atlas when needed.
As an system administrator running MongoDB EA, I'd like the ability to be on premise and burst into Atlas when needed.
1 vote -
Live Migrate Individual Namespaces
Mongomirror allows you to migrate particular databases or collections using the --includeDB and --includeNamespace parameters:
https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includedb
https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includenamespaceIt would be helpful if Live Migrate allowed for use of these options as well to migrate subsets of data, instead of only migrating an entire cluster.
53 votes -
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
6 votes -
Add date added and date updated to Network Access IP table
The network access table should have a way to see the date an IP was added and if/when is was last updated. This will give better insight and control over company users add and maintain their IPs when only whitelisted access is allowed.
1 vote -
To modify transactionLifetimeLimitSeconds parameter
As this is one of the most common request from Atlas customers to modify
transactionLifetimeLimitSecondsit would be beneficial to grant the privilege so the Atlas customers are able change this parameter within a certain limit. Please add this functionality.2 votes -
Provide an interface that can stream logs directly to Splunk.
I'm trying to get logs from MongoDB Atlas to Splunk, and there's currently no native interface to do it, so instead of streaming to Splunk directly, I'm having to execute https calls in intervals, unzip them and then ship them to Splunk. Many products have interfaces to stream to Splunk directly, and it would certainly be handy in this situation.
17 votes -
Unpause Cluster for X Duration
Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.
Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours
Current Atlas Control Plane: "Pause Cluster"
Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"
This is similar to how customers can create temporary database users that are only active for X number of hours.…
1 vote -
Set schedules for pausing clusters
It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.
10 votes -
rolling maintenance for replicasets
Similar to the process outlined in this doc for index builds
https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/
It would be beneficial if the same process can be allowed in Atlas for running database maintenance processes such as dropping large databases that are no longer needed or to purge out old data using this method without impacting the primary.
Bulk Data can be purge out easier using the rolling maintenance method for example when implementing TTL index. If prior to implementing TTL index there is a lot of data to purge out that meets the TTL index criteria, this can be done prior to creating the…
1 vote -
MongoDB Atlas Provider for AWS CDK
We use AWS CDK to deploy our infrastructure. Currently there is only a Terraform provider available to automate the MongoDB Atlas deployment. We would like to have such a provider also for AWS CDK.
In a first step this provider should support:
- mongodbatlascluster create, edit and delete clusters
- mongodbatlasdatabaseUser create and remove usersLater full feature set like in Terraform should be supported.
Currently we use a self written provider. But this has hundreds of lines of code and means a lot of maintenance effort. For our teams this additional effort can be a reason to…
5 votes -
Support optional fallback to source cluster after cutover in Live Migration
Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.
It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.
Having a "fallback sync" option could help with this.
7 votes
- Don't see your idea?