Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Ideally migration of terraform state should be handled or provide a tool for migrating state
Hello,
We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.
Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.
============================================
There are warnings related to your configuration. If no…
1 vote -
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.
10 votes -
Allow 100.64.0.0/10 IP ranges for VPC peering
add more IP ranges for VPC peering on Google GCP network in Google Cloud environment. https://cloud.google.com/vpc/docs/vpc#valid-ranges is supported. Docs only show RFC1918 IPs. https://docs.atlas.mongodb.com/security-vpc-peering/#in-configure-your-network-peering-connection-2
8 votes -
Correct DNS lookup with cross-region peering connection
A cross-region peering connection, say from an Atlas cluster in us-east-1 to some application running in eu-west-1, should allow the application to connect to the Atlas cluster through the peering connection. However, the DNS names of the cluster, e.g. my-cluster-shard-00-00.abx.mongodb.net, resolve to the public IP address of the cluster's node when looked up in eu-west-1. As a result, the application doesn't route the connection through the peering connection but rather tries to route it through the public Internet.
The solution is to manually find the private IP of each mongo node, and add an entry in /etc/hosts for each. This…
1 vote -
Allow Performance Advisor reporting export
Having the ability to extract/export the Performance Advisor report. This would allow users to share a file with others who may not have access to Mongo Atlas.
7 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…
26 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.
16 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 -
Atlas API to update Project Timezone
At the moment, Project Timezone setting can only be done via Atlas UI. We are automating project and cluster creation and setup for our application. We need an API to update Project Timezone setting just like other project settings. This feature is important for our organization to keep all the project with the same settings without a manual intervention.
21 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.
20 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.
7 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 -
Improve password manager support on login screen
Currently on the Atlas login screen it presents a button to authenticate using Google and a text field to enter an email address. Upon entering an email address there's a brief pause - presumably to check if the email address is bound to a configured SAML provider - and if not then the password field appears.
Since the password field doesn't exist in the DOM until it's needed it means password managers have to autofill the email and password fields as two separate steps. I propose to have the password field present and hidden from the start so that password…
3 votes -
The IPs of the newly created cluster should be in the terraform state directly
We are trying to deploy a cluster in Azure using Terraform and then inspect the newly created cluster to get the hostnames and IP addresses. We need these IP Addresses so we update the Azure Firewall to allow the Azure Key Vault to communicate with the Atlas cluster. We are doing this test to enable encryption at rest with our own keys.
We believe the IPs should be in the terraform state directly.
3 votes -
Atlas Endpoint Service "Description / Tag" Field
Currently when creating an Atlas Endpoint Service, there is no way to add a "tag" or "description" to the endpoint.
When a large number of endpoints are created, it because very challenging to identify which endpoint aligns with which customer service or application. Giving customers the ability to add "tag" or "description" metadata, would help give them better visibility into their configured endpoints.
This is specifically requested by an Enterprise Atlas Customer - please reach out to me for details / specifics.
19 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 -
make empty teams possible
It is currently not possible to create empty teams of remove all users from teams.
We would like to arrange our access management through teams. For our production environment we want a 'read only' and an 'admin' team. The admin team should be empty at all times, except in the case of incidents where we want to add specific users to the admin team to be able to solve the incident.7 votes -
Add support for replication lag and replication headroom metrics in Datadog
The metrics replset.replicationheadroom and replset.replicationlag would be useful to have exposed to identify network limtiations and/or too small oplogs
2 votes -
Change write concern on the Atlas Clusters
Atlas does not currently allow to change the default write concern at the cluster level.
It it necessary to have a possibility to change it in order to avoid or minimize rollbackfiles during failover.
1 vote
- Don't see your idea?