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
-
Support serverless OLAP workloads
I can use scondaries to support OLAP workloads however I'd like autoscale read-only and analytic nodes using the serverless cost model.
2 votes -
Languages subtitles
it would be great to have languages subtitles in the videos besides English.
1 vote -
Create new Atlas Alerts integration - Integrate with Atlas App Services HTTPS Endpoints with Authentication
Today we can integrate Atlas Alerts with Atlas App Services HTTPS Endpoints (App Services function) using an Atlas webhook but the process is not easy and the use of webhook requires the alert data traverses the internet. Instead, create an built-in integration that does not traverse the internet but instead uses a private secure communication channel, that also uses Atlas App Services authentication including App Services user definitions.
1 vote -
Atlas feature request
While adding access for teams to a project in Mongo UI, there should be an option to limit access to a particular cluster.
For example: If there are 3 clusters in a project, then team 1 should have access only to cluster1 and team2 to cluster 2 and so on.1 vote -
Expose API for Self-Service Increase of the Clusters per Project Limit
Give Atlas users the ability to increase the number of clusters they can create in a single project above the 25 cluster limit without having to file a support ticket.
7 votes -
Need new redundancy node type
Atlas requires that the use of Private Service Connect for a geo-replicated cluster, requires PSC to be configured in all regions that cluster is in.
The best practice for a DR configuration in Atlas is to have a 2-2-1 configuration over 3 regions so that the cluster fails over automatically in the case of a region outage and there is no split-brain possibility.
The applications themselves really only need to be in 2 regions. The requirement for a PSC in the 3rd region, along with a customer-side project to host that connection is wasteful. This situation is especially problematic in…
2 votes -
trigger manage role
expanding Trigger management role beyond the Project Owner role
2 votes -
Support NVMe for Atlas Azure
Support NVMe disk for MongoDB Atlas Azure.
3 votes -
Ability to choose a Primary shard for newly created database
In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy
14 votes -
Serverless instances on AWS South American region
It will be nice to have serverless instances on AWS South America. This model is great for this region and I strongly believe that it can have a lot of demand.
11 votes -
Support Azure Blob Storage in addition to AWS S3 for Online Archive
Currently, there is only one option to store the archive data and that is in AWS S3 buckets. We have contractual obligations with clients to store data in Azure. It would be great if MongoDB gave an Azure alternative to AWS S3 like Azure Blob Storage.
8 votes -
Increase total number of archives limit
Hello,
We are looking to archive hundreds of collection from each of our clusters. Right now, online archive only allows you to archive maximum 50 collections. It would be very helpful to increase that limit to at least 500. It would be okay if all of them are not active, but it would really help if we could archive more than 50 collections in total.
12 votes -
change streams serverless
Hi. I need the "change streams" feature implemented for serverless deployments.
At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.
Why is that important?
My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.
Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.
…
11 votes -
Read your login suggestions.
Possibly implement a suggestion... It's horrible. It's been horrible from day one. You don't need to re-imagine logging in, okay
1 vote -
Due to some non production workloads it would nice to have the option to choose the number of replica nodes you want. I.e. 1 or 0 vs 2.
It would be nice to have a development environment that had no replica nodes and a staging environment with 1 and maybe even a production environment with 3. The ability to choose how many replication nodes you can have would be nice.
5 votes -
Copy/Duplicate Cluster configuration
It would be really useful to create a new cluster based on an existing configuration.
Snapshots are supposed to be loaded into clusters of the same configuration, but having to set up the configuration manually is prone to human error. Having an option to copy the cluster configuration would be helpful.
Support suggested the following workarounds, but the option should really exist in the UX, given that snapshots can be taken and loaded in the UX.
- use the API to create all clusters so that the config exists in code
- use terraform to create clusters3 votes -
Multiple connection URLs for Atlas clusters
Allow generation of multiple application-specific connection strings/URIs to the same Atlas cluster. This would ease migration of databases to different clusters over time; consolidating smaller databases to lower costs, or separating busier databases to isolate performance impact.
Multiple connection strings will allow us to redirect connections seamlessly when migrating databases without requiring developers to re-deploy changes to application connection strings, minimizing downtime and coordination.
1 vote -
Reference a db user from namespace A to a project in a different namespace
We need to ability to reference db user in namespace A to an Atlas project in a different namespace.
2 votes -
Implement AWS transit gateway support
VPC peering and Private Endpoints have limitations that make them unusable in some environments. Implementing native transit gateway support would allow admins with hybrid infrastructures and strict security requirements to control routing and security at a lower level then is currently supported.
VPC peers do not support pass through routing, so organizations that use transit gateways to attach IPSEC tunnels or other external networks to AWS are unable to access atlas servers via these peer connections.
Private Endpoints do allow connectivity in these cases, but cause an additional layer of expense, complexity, and reduced security. First, the "user" side still…
12 votes -
Link two different clusters to the same Vercel app with the Vercel Integration
At the moment, one can only link one cluster to a Vercel app (which creates a MONGODBURI variable in Vercel). It would be nice to be able to link another cluster (e.g. a dev cluster) to the same vercel app by customising the name of the MONGOBURI variable created (e.g. MONGODBURIDEV).
1 vote
- Don't see your idea?