Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1360 results found
-
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 -
Calculate Atlas Enterprise by sku
On the invoice, calculate the support value per SKU. Currently, the value of Atlas Enterprise is not included in the SKU.
1 vote -
Data Explorer should reflect the status of the Hybrid Index Build process
At present the Data Explorer has a very limited ability to report the status of the hybrid index build. For instance, when the coordinator is waiting for quorum the Data Explorer may report the index at 100% readiness. That may lead to a confusion that the index should already be available for use - it's not. Such a condition can last for hours.
Ideally, Data Explorer should reflect the status of the Hybrid Index build process showing the progress per individual nodes.
1 vote -
Notification "Failed maintenance"
It would be helpful to have a "Failed maintenance" notification. While we cannot resolve the issue ourselves in such cases and need to open an Atlas support ticket, it is still important for us to receive a notification so that we are informed about the problem and can respond accordingly.
1 vote -
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 -
Control shard balancing window with Terraform
This documentation page talks about how to manage shard balancing - https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window
but it requires connecting to the db first, I see no way to manage this through the Atlas Gui or terraform.
We have had some instances recently where shard balancing has caused a large resource usage spike on our cluster and affected our services and we would really like to be able to set a shard balancing window using terraform to prevent this from happening during the middle of the day2 votes -
Edit PSC connections
Allow admins to edit existing GCP PSC networks -- currently, if a client wants to increase the number of IPs allocated in a PSC, they have to increase the limit, delete the PSC, then create a new PSC.
In a Production environment, this can cause 2 hours of downtime while reprovisioning PSC IPs that don't need to be provisioned, rather than scaling the number of IPs in-place.
4 votes -
Push Atlas org events and projects to S3
Similar to cluster logs being pushed to s3 feature, if a feature to push organization, project and cluster events to s3, our event ingestion pipelines could be simplified significantly. Without the feature we are forced spin up event ingestion agents and make them reliable/available. These ingestion agents source the events via API and publish them to cloud watch logs, that are eventually fed into our observability stack. If the events can be pushed into s3, we can eliminate multiple intermediate components.
6 votes -
Terraform lifecycle ignore_changes tags
It would be nice if tags would not be set of list and will be a map, like tags for Azure resources.
In that case, you can ignore some tags by name. Like thislifecycle {
ignore_changes = [
tags["costcenter"],
tags["environment"],
tags["projectcode"]
]
}https://github.com/mongodb/terraform-provider-mongodbatlas/issues/2006
5 votes -
Implement the role mapping for the MongoDB atlas teams to the Projects Using terraform
Currently terraform supports to assign single user invitation with role assignment to the projects, however we do not see any role assignment enabled for the teams & API keys.
We would like to know whether this feature can be enabled in coming versions or if we have any alternative/workaround solutions please share with us.
1 vote -
Data transfer costs - Capacity Units Breakdown Invoice
On the invoices include the costs of data-transfer based on capacity units / hour. Capacity units are calculated based on 3 categories: "New connections or flows","Active connections or flows" or "Processed bytes".
One of the difficulties from the user perspective is to understand how much is the usage of our application on MongoDB is contributing for each category?Example: I was charged for 10000 Capacity Units for 3h, at $0.012 hour. Final charge is 360$. The problem with this is that I don't know what is contributing most for my cost, is it the "New connections"? "Active Connections? or "Processed…
1 vote -
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.
9 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 -
"Atlas Onboarding"
Allow user to escape from onboarding without having to edit the url.
When the system doesn't accept the input, the user cannot escape and see their dashboard.1 vote -
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 -
Support Online Archive in AWS Hong Kong region
Request to make Online Archive available in AWS Hong Kong region
Customer are using MongoDB Atlas in AWS HK region to store data that are required to be located in the same region.
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 -
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Managed Grafana instance
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Grafana Managed Instance.
Azure Managed Grafana instance has Enterprise plugin for MongoDB but that is a Market place product which is not available to customers with CSP contract with Microsoft.
1 vote -
Enable Replica Set Scaling Mode
Currently, it's not possible to configure the replica set scaling mode for shards and other configs available in the UI through terraform (see attached screenshot).
1 vote -
Incorporate Resource Tags in Atlas alerts
Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
14 votes
- Don't see your idea?