Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
Role to work with vpc peering with READ ONLY access for rest in the Atlas Dashboard
The requirement is:-
An individual will be able to see (READ ONLY access) the Metrics. He/She will be able to work (Add/Delete) with Network VPC Peering.1 vote -
Support of new EBS Volume type (gp3)
When creating cluster , We have not option to select GP3/GP2. while newly introduce gp3 EBS volume have less price and high IOPS.
So why we need to settle for less.
1 vote -
Page title says "Create Cluster" when editing cluster config
Small thing I just noticed (confused me for a second because I had a second tab open to actually create a new cluster). My idea is to have the the title say "Edit Cluster" instead.
1 vote -
NodeJS Trigger Dependencies
I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.
1 vote -
Allow transactionLifetimeLimitSeconds to be modified from Atlas
We need to be increasing the default value of transactionLifetimeLimitSeconds to larger numbers (usually 300 instead of default 60). Considering number of clusters we running / we are going to be spinning up in the future its cumbersome to keep requesting this change from support. Instead please allow us to set or modify this from the Atlas GUI.
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…
6 votes -
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 -
Configurable number of insertion workers per collection for mongomirror
Mongorestore allows for the number of concurrent insertion workers per collection to be increased using the --numInsertionWorkersPerCollection option.
However, this is not available for mongomirror -- while you can increase the number of collections copied in parallel (--numParallelCollections), there's no parameter surfaced to allow more inserts to be occurring at the same time over multiple threads within each collection.
|t would be helpful to have a parameter like this to use to increase parallelization in order to increase the speed of migrations of large collections.
9 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…
20 votes -
Ability to provide IP addresses as a list for Network Access
When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.
7 votes -
Stop dismissing dialogs by losing focus
When filling in the password field in Atlas user, sometimes I click show then start typing a new password, or Home/end to highlight it. Somehow half the time it dismisses the dialog and I have to start over.
I suspect it is the dialog losing focus. Stop dismissing the dialog when I click off of the box. Other dialogs do the same thing. A lot of web apps do that now and it seems really dumb -- save one specific Cancel click to aggravate me many more times when the dialog I have worked on for 5 minutes disappears.
2 votes -
Allow the ability for a rolling cluster restart like during maintenance
Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.
17 votes -
OCSP stapling support for Atlas Clusters
What is the problem that needs to be solved? As a user (MongoDB Driver) you'd like to check revocation status of X.509 certificate via TLS Certificate Status Request extension (also known as OCSP stapling) instead of doing outgoing HTTP connection to OCSP endpoint from a user (MongoDB Driver) side.
Why is it a problem? (the pain) MongoDB Server v. 4.4.X introduces OCSP stapling functionality, however OCSP stapling is not enabled on Atlas Clusters with MongoDB Server v. 4.4.X.
6 votes -
Include security group and tag for privateLink setup
On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:
- include or modify "security group"
- attach a "tag = name"
That way when user has the AWS CLI command generated, it includes security & tag
1 vote -
Comments on Private Endpoints to aid identification
On Atlas when creating private endpoints, add comments field to allow easier identification.
2 votes -
if we had option for diabling javascript execution on database we would have to no worry about it
javascript excuiton can be used for harm and mass deletion data. İf we had no javascript execution we would be safer.
1 vote -
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>", ...]
},
...
],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 -
Cluster version overview on Owner level
We have partially older mongoDB versions running on our clusters. We get notified about it by EOL mails from mongoDB. However, as an org owner, I cannot see which clusters are affected. This makes it extremely time consuming for me to identify the relevant contacts per cluster. Our org structure entails self-sufficient teams with independent accountability of the mongoDB clusters. There is no central contact person.
It would be desirable to be able to call an overview of all clusters with the respective installed version in the GUI with owner rights.
1 vote -
Ability to apply the same settings to multiple projects
As described in support case #00739901, we have exceeded the 50 limit of clusters in our production project.
We are going to have a lot of new clusters in the coming year, and they all need to be in the production environment.
There should be a way either to add more clusters to one project or to share the same settings between multiple production projects for growing customers of MongoDB like us.
2 votes
- Don't see your idea?