Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
493 results found
-
Improve labeling experience in Network Access
I see option "add my current IP address in allow list" quite handy.
After I click that button there is no labeling option near.
I could use a search bar of browser to find a recent ip address but that is too tedious.I want labeling input just after added the address into allowed list.
One more cool option would be to choose a label color.
That way I can manage or distinguish all addresses/hosts simply in a instant look.
1 vote -
In the Project Overview interface of Atlas, show users that the set of clusters is incomplete
In the Project Overview web interface, in the Clusters pane, four of our clusters are listed. I am new to our MongoDB deployment and to this UI. I had no way of concluding we had more than four clusters. I thought that was the complete list.
I feel strongly that if you are going to show only a subset of clusters in a UI, you need to also give users some visual clue that this is only a subset, that the list is incomplete, and that more can be found somewhere.
1 vote -
Granular permissions needed with Federated Authentication in Atlas
Granular permissions needed with Federated Authentication in Atlas
For example(but not limited to), it would be good to assign to an external role, via Federated Authentication:
-to create RS users;
-to restore a RS.1 vote -
1 vote
-
Control Over how to upgrade minor versions or rollback if required
Hello Team,
We recently faced an issue with the automatic minor version upgrade that rolled our clusters from 6.0.16 to 6.0.17 through Atlas. Since 6.0.17 has some problems, can we request the following features:
1. Disable automatic upgrades of minor versions.
2. Allow manual rollback to previous minor versions when necessary.2 votes -
Alerting mechanism to notify when the node internal/external IP changes for MongoDB Atlas Cluster node
We would need an alerting mechanism to notify the team when the node external/internal IP changes. This helps us to troubleshoot the problem quicker and can change in the firewall configuration quickly.
1 vote -
Unblock users in Russia and Belarus
Currently MongoDB blocks access to MongoDB Atlas for users who are located on the territory of Russian Federation, Belarus (and other countries).
MongoDB Support team confirmed this is the case and stated that the reason is US regulations and sanctions, referring only to the blog post published on their website (https://www.mongodb.com/blog/post/mongodb-assistance-ukraine-shut-down-work-russia). The blog post does not mention that the access to users is blocked.
To our best understanding not many other tech companies have implemented such strict measures.
We've also taken the time to delve into the sanctions topic and have reviewed every public release of sanctions on…
5 votes -
Altas CIDR ranges for network containers are too restrictive
Background:
For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.AWS minimum imposed CIDR value/subnet size: /28
MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24Azure minimum imposed CIDR value/subnet size: /29
MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…
6 votes -
Ability to schedule "Hedged read" Turn on/off
Customer experienced read latency during maintenance after sharding.
Our guidance is to turn on "Hedged read" option.
So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.
11 votes -
Ability to create granular auditing
I want to be able to create granular auditing for a specific cluster inside a project. Right now, the audit is applied to every cluster inside a project. Some clusters need more auditing than others, and their performance should not be affected by other cluster configuration.
2 votes -
Authority Root/Intermediate Certificate from Let's Encrypt update
Need to be notified when Authority Root/Intermediate Certificate from Let's Encrypt will be upgraded. It can be a alert/rss flow/notification/email to inform the customer company.
From documentation https://www.mongodb.com/docs/atlas/reference/faq/security/#hard-coded-certificate-authority (Which certificate authority signs MongoDB Atlas TLS certificates?)2 votes -
AWS gp3 Decouple IOPs from Disk Size
With AWS EBS gp3 volumes, IOPs and throughput can be provisioned separately from EBS storage size. While Atlas now uses gp3 volumes and provides a base throughput of 3,000 IOPs, higher throughputs are still directly tied to disk size.
We run IO-intensive workloads that require high throughput, and we have to severely over-size disks to get the needed throughput. We don't require the extra-low latency of provisioned IOPs (which is much more expensive than over-provisioning storage).
According to the linked AWS documentation below, if the M60 instance size is running on an ec2 m5.4xlarge instance type, it can support a…
13 votes -
All Clusters permission for ORG level roles
Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.
When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.
7 votes -
Atlas - Queue cluster pause request to perform it when it's possible
It is impossible to pause a cluster that was recently resume.
The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.
I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either…
11 votes -
The oplog configuration is a bit confusing
The oplog configuration is a bit confusing. I think it's not clear that if we set the oplog window, we don't need to set the maximum oplog size. I believe this configuration should be more specific.
1 vote -
cloud.mongodb.com，Since this week, it often cannot be opened
cloud.mongodb.com，Since this week, it often cannot be opened
1 vote -
Live Migration with granular permissions
Today, to carry out migrations you need to be the Project Owner of the project, however we have very restricted permissions regarding Mongo projects so that people can use the company's stack, which would be via terraform. The dba's have readonly permissions on the projects so as not to modify items in the projects using the console.
The idea is to create an intermediate permission so that dba's can carry out cluster migrations without necessarily needing to have a project owner. Is there a way to do this without breaking permissions, is it possible to request this feature?1 vote -
Add usability to tags
Atlas has the option to set tags to clusters. But - now what? They are just pieces of text floating around, but are completely useless.
How about enabling to filter clusters in a project or even organization based on those tags? Split costs based on them? Query them with API calls? I have no use of those tags when they are just texts in the main page of Atlas...8 votes -
IP address, Mongo Network Issue
Why is it that we always have to provide our ip address in the Netwoek Access section and that's not even the issue the fact that we have to add 3,4 ip addresses everytime we open atlas is the main issue. Every time I login I delete ip's adn add them again or logout and add them again it's a repeating process until I get my connection going please resolve this issue now it's going on for a while.
1 vote -
Display a cluster tier size (e.g. M20) on the all Clusters page
I am opening this new feature request on behalf of the customer. Would it be possible to display a cluster size (e.g. M20) on the main status page alongside other cluster information that's already on the page?
9 votes
- Don't see your idea?