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
-
Atlas Administration API: Expose more information on cluster status
We are using the Atlas Administration API in order to automate scaling a production database cluster deployment in a more fine-grained way than the existing autoscaling offer. The specific database cluster is deployed as a replica set, so there is a number of electable nodes (one primary + 2, 4 or 6 secondaries) and any number of read-only (RO) nodes.
The goal is to be able to tune the number of nodes in a specific region, and being able to monitor the progress of the change being rolled out. Currently, the API offerings are too limited to do this effectively,…
1 vote -
Add project user role to Create App Services apps
(Creating on behalf of a customer.)
Create an Atlas project user role to only allow Create App Services apps (similar to the Atlas Search index creator role we have.4 votes -
Allow access to Admin API using AWS IAM role
It's possible to authenticate to a database using AWS IAM role. The same should be possible for the Admin API.
The problem with the API keys is that they can be taken away and used elsewhere. They pose an additional risk in an AWS integrated environment.
This also relates to upcoming Cloudformation Resources where the extension needs to store the API Key in AWS Secrets Manager. The resource already has a role that could simply be configured to be trusted on the Atlas side.
2 votes -
storage autoscaling at N %
Dear Mongo Team,
Your engineers advise to add more storage to the clusters when it reach 80 % usage as this is when performance degradation can occur. At the time of writing the autoscaling happens at 90 % disk usage. We want to be able to adjust at what % of usage the autoscaling happens and set it to the value of 80 % basically what your engineers advise.
10 votes -
Don't overwrite explicitl role with default organisation role configured in identity provider
we have user created in Atlas on Organisation level with specific org role. If we configure Identity Provider and set some default role, then after first login this user will receive this default role and original role will be lost. So, even after disabling identity provider, user will have this default role.
Suggestion: explicitly granted roles should be keep untouched, but not be applied in case of active identity provider.
1 vote -
Copying gbs of collection data from one project to another project
Currently it is highly time consuming process of copying a 100gb collection from one project to another project. There is no faster and proper way of copying the data. This feature is highly needed. Because each environment resides in different projects. If someone want to copy only handfull of collections from one project to another(dev to prod and vice versa) then its a nightmare for doing this kind of job. Tried mongomirror and mongodump feature but those are not quite impressive.
1 vote -
Get all databases from one cluster
Add a new Admin API to Atlas: Get all databases from one cluster
2 votes -
Add option to "Explain" a query from the "Profiler" page.
The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.
2 votes -
show the reason why you can't increase oplog
in the settings=>additional settings=>More Configuration Options=>Set Oplog Size
show the reason why you can't increase this parameter (let's say you have insufficient free space etc.)2 votes -
When Adding new CKM key/role Atlas should validate if it can safely change existing CKM key
When we create new CKM key with new role and update credentials on project level, Atlas validates that new role can read new key. But it does not validate if new role can read existing CKM key.
When Atlas starts re-encrypting existing cluster, first node goes down but can't be started because new role can't read old key. There is no way to restore/rollback this change unless raise a ticket for MongoDB support.
Suggestion: when we upgrade credentials/role/KMS key in UI, Atlas should validate if it can finish this change BEFORE applying changes to nodes.
2 votes -
SSO + SCIM for Atlas Auth
Support SCIM for SSO as this can allow for more fine grained control for access groups in Atlas. This can help IT groups hit their goal of a consistent RBAC set up and improve the user experience for MongoDB Atlas users (less back and forth with IT).
https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management
9 votes -
Atlas UI enhancement
Hi,
Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.
- When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
- Right side top corner, we can also see it states "All Clusters"
- Terraform resources/attributes talks about Clusters
- Only place we see in the home page "Database Deployments"
Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in…
2 votes -
m10 for gcp santiago zone
I would love if i can select m10 than m30 on santiago region.
1 vote -
Support for AWS China (Beijing/Ningxia) regions
Please make Atlas available in AWS's Beijing/Ningxia regions. This is important to due to China's internet restrictions to achieve the best possible performance/latency for our Mainland China customers.
14 votes -
disabling mongo user
Instead of completely removing a Mongo database user, its better if there is option to disable user so that if there is any untoward incident we can enable it back. After observing for some time, we can delete/disable the user based on organization requirements. Its useful in some cases like mongo db user returned to same department after some time .
3 votes -
Automatically detect location for Global Clusters
Currently Global Clusters require a location field for zone targeting. Could the user get an option to be auto-detected based on the incoming connection? The reason for this is, not all app services have the ability to include location, so would be good to auto-detect it.
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.
6 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…
1 vote -
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
13 votes
- Don't see your idea?