Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
Return a user createdDate for Atlas control plane and database users
Automated user systems such as Hashi-Vault will automatically create users. Typically these users have a 90day expiration. Any team using continuous delivery hits the atlas user limit. There is not a way to know when an atlas user was created from the API data
4 votes -
Support OIDC as Authentication Protocol for access to Mongo Portal
Currently SAML is supported: https://www.mongodb.com/docs/atlas/security/federated-authentication/#configure-federated-authentication
It would be preferable if OIDC was supported.
4 votes -
Metric reporting private endpoint state
On Mongo Atlas platform we are able to see the status of both Atlas Private Endpoint and Azure Private Endpoint. It would be helpful to have these statuses available as a metric on the prometheus integration.
4 votes -
Integrated Benchmark utility for mongodb
I would like to request a mongodb utility which can do benchmark tests and can be used by developers and DBA to test mongodb for release changes, application code changes etc. The utlity should be able to simulate multiple users and produce different types of workloads (like reads, updates, deletes, inserts etc). This would need to be similar to other nosql benchmark tool like asbench used in aerospike nosql database.
Link is : https://docs.aerospike.com/tools/asbench4 votes -
LDAP Users shouldn't be successfully authenticated if not authorized
Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.
Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.
Please reject any non-authorized user from connecting to an…
4 votes -
Add a role or modify Project Cluster Admin role to allow administrators to mange backup
Today you must be Project Owner to manage backup scheduling and retention. This is far more excessive a permission than needed for DBAs to manage backup scheduling and retention. A role or another permission group for administrative tasks would be important for this product.
4 votes -
Support terraform plan with ORG_READ_ONLY role
An API key with ORGREADONLY should be sufficient to run a terraform plan. Afterall its describe is "Provides read-only access to the settings, users, projects, and billing in the organization.")
However, this is not the case: checking settings for "Cloud Provider Access" [1] and "Encrypting at Rest" [2] fail due to mission permission. Read-write project permissions like GROUP_OWNER on each project are required.[1] https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Provider-Access/operation/listCloudProviderAccessRoles
[2] https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Encryption-at-Rest-using-Customer-Key-Management/operation/getEncryptionAtRest4 votes -
Google Private Service Connect
Greeting from Fivetran!
This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.
From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed to AWS…
4 votes -
Add more information to "We are deploying your changes..." blue bar
Occasionally we see the deployment blue bar but aren't sure exactly what is being done. It would be very useful to have a link to click to see what changes are currently being pushed out.
4 votes -
Introduce serverless clusters for GCP Frankfurt region
Would be great to have the serverless clusters in FRA GCP as well. Would be good for performance.
4 votes -
activity feed filters
Currently it is not possible to filter out from activity feed by certain pattern e.g. we want to filter out all db users which start with smth-* and be able to see if there were db users created which follow a certain naming pattern. So we need to be able to filter activity feed by the username or any other detail in the activity feed text. Thank you so much!
4 votes -
Improve Mongo activity feed for project page
Mongo Atlas activity feed page does not update automatically nor does it have a refresh button. Each time the user wants to refresh the page they have to refresh the URL which removes all the filters(unless you copy the link). It would be very helpful if there was a refresh button which would not remove the filters as this means that the page does not have to be refreshed from the URL.
Additionally an auto-refresh(timed) option would enhance this feature more so that the user does not have to do anything on the page to see the latest updates, eg…
4 votes -
Allow API Access via Private Endpoint Connection
To automate processes ATLAS Admin API is used but does only work if your cluster is not connected via Private Endpoint.
4 votes -
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 -
REST API for sizing and pricing information
To keep our configuration on optimized terms we need a way to keep sizing and pricing data of the configuration on our side up to date. We have to get this information automatically for example via REST API.
This would help us to be up to date concerning
- Tier sizing: e.g. tier, RAM, CPU, min HDD, price included HDD, max HDD
- Pricinig: e.g. how much $ per hour / month for tier ***, with XX GB HDD and RAM, KMS encryption, backup and so on4 votes -
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.
4 votes -
invoice
Invoice should show the ClusterName combined with Cluster Tier and Server Hours same with Data Transfer. With these, it is easy to determine how much cost we are spending per ClusterName. Right now it only shows per ClusterTier which is hard to separate the cost if you have 2 same ClusterTier.
4 votes -
Recommendation to the change the tier cluster
Based on CPU and memory usage metrics over a certain period of time, a recommendation could be made to change the cluster tier to a higher or lower one (inform which cluster it would be recommended to change to) and notify through some channel, such as eg email/slack.
4 votes -
Expose Locking Metrics
One of our customers have asked if we can expose locking metrics through the Atlas UI to assist with investigating suspected lock contention issues.
We have this information in FTDC and our customer feels it would be helpful for them to have this information too.
4 votes -
Atlas UI Show Snapshot ID in web
Please provide a capability to show the snapshot ID of a snapshot in the web GUI, currently we have to make an API call to get the snapshot-id
4 votes
- Don't see your idea?