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
-
M0 in eu-west-2 with API (terraform)
I really love mongo. Not having M0 in eu-west-2 and terraform is a huge limitation. It prevents me making the business case for mongodb as our backend of choice, and we end up using AWS DocumentDB. Mongo is preferable for consistent hybrid cloud deployments.
1 vote -
Single node clusters
Allow users to create a single node clusters for dev purposes.
3 votes -
Create distinct indexes for Analytics nodes
To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.
36 votes -
Live Migrate modal: Allow users to point and click to select another Atlas source cluster
It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).
Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.
It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in…
10 votes -
Deactivate use of charts on org-level
As charts meta data are processed only on US servers, a toggle to forbid the usage of charts for autonomous teams would be helpful, considering GDPR requirements
2 votes -
Project migration should not require org-owner rights
Before project migration from one org into another, we have been told to define the responsible users in both orgs with org-owner rights. There should be no need at all to permit org-owner rights on project migration. The org-owner-level should only be reserved to the very smallest group of people (admins) necessary. Project owner level should be enough for a migration of projects.
1 vote -
Add a grace period between a failure to obtain a certificate and the cluster shutting down.
If you set up encryption at rest on Atlas using an external key provider, such as an Azure Key Vault, then a link is created between being able to access the key vault and the status of the MongoDb cluster.
For example, on the 28th September, there was an issue at Azure (SM79-F88) and for over 2hrs around 19% of all authentication processes in Europe failed. This included accessing the KeyVault used by our MongoDb cluster. As Atlas checks the keys roughly every 15 minutes it failed to obtain the key at the beginning of this period and our cluster…
1 vote -
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 -
Allow customer encryption key validation time interval
Currently, Atlas has a 15 minute interval where it checks access to remotely stored Customer Managed Encryption keys for the custom encryption at rest feature.
This value is not changeable, and it implies a problem: access to encryption keys can be lost for longer periods than 15 minutes without that implying that the key has been invalidated by the customer.
A perfect example of this was the recent Azure AD global outage that prevented all authentication to the Azure platform for about 3 hours (complete outage description: https://app.azure.com/h/SM79-F88/691d78). While the key used for one of our clusters was not…
7 votes -
1 vote
-
Implement create-before-destroy when migrating NVME instances
When triggering a cross-region migration Atlas immediately degrades a cluster by going to N-1 nodes prior to creating a replacement node in the new region.
When using NVME instances, this violates the agreed upon replication depth. Once the NVME instance in the source region is destroyed, there are only N-1 copies of the data left, as there is no EBS backing.
NVME target instances should be brought up as {hidden=true, priority=0} until leaving STARTUP2 and entering SECONDARY. Once this occurs, the target instance should be brought to {hidden=false, priority=P}, and a source instance hidden, removed after a quiescence period, and…
2 votes -
An API endpoint for Live Migration
When customers have dozens and hundreds of clusters to migrate from on-prem to Atlas, automation is very important and Live Migrate is not supported via API today. Mongomirror is a shell command that can be leveraged for automation but having Live Migrate available as API will be a great enhancement to CD/CI pipeline.
2 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 -
Improve database access tab
Managing permissions for users is a pain right now. It's a lot of clicks, it quickly becomes messy and sometimes the modal closes without saving changes.
It would be a lot easier if we could import a CSV containing all permissions for a certain user (user name, permission type, database name, collection name)
4 votes -
Ability to schedule monthly maintenance windows
Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.
I realize we have the ability to defer maintenances for a week, which is great. However, we're now…
7 votes -
Love The New Look
Just wanted to say I love the new look!
1 vote -
Switch from legacy Slack tokens to Slack app
Slack tokens are now deprecated and a legacy implementation. You cannot generate new tokens anymore either, so it's impossible for us to set up Slack notifications.
Please create a Slack app to allows us to use Slack alerts again.
2 votes -
Support the ap-southeast-2 reqgion in GCP
Indonesia has strict requirements about PII remaining in region.
1 vote -
Upgrades from shared to dedicated clusters should only make the cluster available after data has been restored
We have recently upgraded from a shared tier to a dedicated cluster. As document, this process involved a downtime. However, what was not document is that the cluster becomes reachable for clients again before the data has been fully restored. That way, clients can invoke operations on the cluster, that may even interfere with the mongorestore process. I would propose to make the cluster available again to public clients only after all data has been restored to avoid the chance for such race conditions.
1 vote
- Don't see your idea?