Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1257 results found
-
Alert notification for new cluster created in the project
Greetings, Support
After looking over the alert settings, I discovered that there aren't any alarms that can be monitored to be informed when a new cluster is created on the present project. Please include a notice about the future release, as it directly correlates with and impacts the price and invoicing.(Confirmed with support as there is not such alerts in Atlas with the current settings and case:01298603)
1 vote -
Terraform provider should handle pagination for mongodbatlas_atlas_users resource
The resource mongodbatlasatlasusers limits results returned by page with a default of 100 and max of 500. Attempting to retrieve a complete list of users where that list is not a known size isn't possible because of Terraform limitations on dynamic blocks. It would be quite helpful if the Terraform provider handled pagination and this resource by default returned a complete list.
1 vote -
Customer feedback around the UI of Atlas - unable to edit multiple documents at once
The customer wanted me to provide product feedback around the inability to edit multiple documents at once from the Atlas UI. The customer uses a 3rd party tool to do this instead and thought it would be better and more intuitive if this was built right into the Atlas UI.
1 vote -
More Granular Node Read Preference Tags
I would like the ability to set tags on individual nodes so that I can change the read preference with more granularity.
Mongo supports these tags on non-Atlas deployments: https://www.mongodb.com/docs/manual/core/read-preference-tags/#std-label-replica-set-read-preference-tag-sets
Analytic Nodes are very useful, and they are built as way of isolating workloads. The problem is that you can only really isolate into two different buckets (well three if you consider local read nodes). What I'd like to do is isolate more than two different sets of users and queries, so say user reporting and internal dev activities have their own sets, and they work independently.
You could kind…
1 vote -
Stop scamming your users
How about you stop scamming your users with deceptive instruction on your download pages.
1 vote -
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
2 votes -
"Manage your own encryption keys deactivated" event
We recently discovered that there is no event when deactivating the option "Manage your own encryption keys" within the cluster configuration.
While there are hints towards this within the CLUSTERUPDATESTARTED and AUTOMATIONCONFIGPUBLISHED_AUDIT events, there is no clear warning that the encryption keys of the cluster are affected.
As an unwanted change of encryption at rest keys for data can have severe impact on data accessibility and security, I would propose adding a "Manage your own encryption keys deactivated" event to the Activity Feed.
3 votes -
Integrar la alerta de Replication lag de Atlas en el API de Prometheus
Se solicita incluir métricas en el API de prometheus para poder implementar la alarma de Replication lag
6 votes -
Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs
Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.
This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…
2 votes -
Support tags in terraform-provider-mongodbatlas mongodbatlas_project
terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.
1 vote -
Terraform Downward Autoscaling "Use Smallest possible" placeholder
When setting "providerautoscalingcomputemininstancesize", is it possible to either;
- Loosen the validation by ignoring current disk configuration size.
- Create a placeholder to indicate "Use smallest possible value".
Atlas appears to support invalid values, provided it was entered when it was valid.
I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
1. I define an…1 vote -
serverless concurrent connection limit
Increase to the 500 concurrent connections hard limit so that we can use this in a production domain service. We would also need connection pooling / proxy as described in another idea.
1 vote -
Restore a snapshot from one organization to another organization via API call
I have tried to create automation to restore the snapshot from One organization cluster to other organization cluster. Example Prod cluster from Organization A -> Stage cluster from Organization B.
currently this method is not possible to restore a snapshot from one organization to another organization via API call as API key cannot be shared over the scope of different organization.( As per mongo atlas support Engineer)
Please enable this feature to automate the snapshot restore instead of using UI for restore.
1 vote -
Analytics node with NVMe option
We currently have use mongodb mainly to correct data and visualize with chart features. Some chart require heave disk read operation and need more performance. We need fast storage access only for analytics nodes. If we can select NVMe option only for analytics nodes, we use it but we don't want to switch whole clusters to it since main cluster don't need higher cpu/memory/stroage/iops. We just want to use NVMe only with analytics nodes. Some restriction such as min storage size for main cluster is acceptable but don't want to upgrade to higher tier of main cluster.
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…
3 votes -
Add support for GCP (Google Cloud Platform) region of dammam (me-central2)
Dear MongoDB Atlas Support Team,
I hope this email finds you well. I am writing to inquire about the availability of the MongoDB Atlas region in Dammam, Saudi Arabia.
As our organization expands its operations, we are seeking a reliable and secure cloud database solution. However, we are obligated to comply with local regulations that mandate the hosting of our data within Saudi Arabia. Therefore, it is essential for us to find a suitable hosting option that meets these requirements.
After reviewing the available regions for MongoDB Atlas, we noticed that the Dammam region (me-central2) is not currently listed. We…
1 vote -
Storage autoscaling of storage should also occur when Atlas searches are being rebuild
When the storage requirement exceeds the available storage when rebuilding Atlas searches a warning is issued and manual intervention is needed.
I would like that autoscaling of storage will occur when needed for rebuilding Atlas indexes.
This would save us time and no need to react to warnings.1 vote -
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.
2 votes -
Push Logs to AWS S3 bucket: IAM role Max_Session expect 12hours
With respect to the feature "Push Logs to AWS S3 bucket " Atlas expect max-session-duration for IAM cross account role is : 43200 (12HRS) by default.
Some organizations like us have limitations on max-session. We reached out MongoDB Support, They said " The Atlas team has confirmed that currently, we do not support max session durations of less than 12 hours. However, there is an internal ticket for improvement, where session duration can be internally configurable via MongoDB's internal support UI. Case ref: 01276442This will provide a flexibility for the organizations to have max-session configured according to their internal…
1 vote -
Push Logs to AWS S3 bucket: Terraform
Push Logs to AWS S3 bucket, This feature is helpful, It gives a flexibility for large organizations who need to segregate logs considering Inventory, Security and Observability to organize logs to a respective destinations from S3.However the terraform provider does have api's to fulfill this feature https://www.mongodb.com/docs/atlas/push-logs/ . If it can available in terms of terraform resources, This will help our organization to enable logging in terraform IAC to simplify the logging and deployments
3 votesHi Jai, thanks for sharing feedback. This item is already under development and should be published to Terraform Registry over next few weeks!
- Don't see your idea?