Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
158 results found
-
Ability to delete account
I really need to delete my account as this is not what I am looking for.
5 votesHello,
I just want to update this ticket that self-serve account deletion is supported since August 2021. Please note that once you delete your Atlas account, you cannot use the same email to create a new Atlas account.
-
Allow user to specify either more date types, or arbitrary archive criteria
Currently to configure the online archive service, you specify which column you want to use, which must be a Date type. Our collections often use integer fields holding the offset from the epoch, and there are other fields people might reasonably used.
My suggsetion would be to allow for a diverse set of date types, or ideally, allow the user to specify the criteria themselves with a mongo query.
5 votes -
Support migration of existing projects, clusters, ... to be CloudFormation managed
When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.
4 votesHello, Import w/ MongoDB CloudFormation Resources is now supported (github)
-
Atlas backup to second region in a Terraform Module
Feature for selecting "Atlas backup to second region" in Terraform Module.
Currently, this option is only supported by the UI and the API.4 votes -
MS Teams alert support in terraform provider
It is possible to configure MS Teams alerts in the atlas UI, however terraform support is still missing. It would be great to have that option
4 votesThis is now out in version 1.4.2.
-
Add possibility to invite api key(s) to newly created projects
For different types of automation, api key(s) must be added to project(s). It would be helpful if it could be possible to add existing api key(s) to new projects using
mongodbatlas\_projectterraform resource, example:
resource "mongodbatlas_project" "test" {
name = "project-name"
org_id = "<ORG\_ID>"teams {
team_id = "5e0fa8c99ccf641c722fe645"
role_names = ["GROUP_OWNER"]}
api_key {
public_key = "xyzxyzxy"
role_names = ["GROUP_READ_ONLY"]
}
}4 votesThis has been added as of version 1.2.0, released today. See https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#api_key_id for more details. Thank you!
-
Allow creation of a free cluster (M0) through the API
Through the API it is possible to create several projects within an organization, and as far as I understand you offer 1 free cluster per project....
So, why not create the M0 cluster also through the API? (considering the limitation of only 1 for the project, of course)
This would be of great help for integrations that automatically generate small test environments for certain applications that plan to use atlas as a database server.
4 votesHi Bruno,
Thank you for taking the time and raising this feedback. We believe it’s crucial to support you and development teams in integrating MongoDB with your CI / CD pipeline. For example by enabling generation of small test environments using M0 clusters.
With that in mind, we’re happy to share that this capability has been recently added to our Public APIs as well as MongoCLI. To learn more and read about other new capabilities we’ve added, visit https://docs.mongodb.com/mongocli/stable/release-notes/Thank you again for sharing your idea and keep it coming.
All the best,
Jakub -
Support for tagging clusters in Atlas
Please allow tagging at a cluster level. This will help in storing related metadata if required.
4 votes -
Add Test Failover permissions to the Project Cluster Manager role
Add Test Failover permissions to the Project Cluster Manager role.
Use Case:
We'd like to have folks with this permission without also allowing them to modify Project membership and all the other permissions that come with being an Owner.4 votes -
more information in AWS IAM audit logs
We are using MongoDB-AWS for authentication, and have set up the audit log to log events taken by AWS roles. However, there is insufficient information in the logs to identify who is doing those actions, as roles can be assumed by multiple people.
An example log line in the current audit log:
{ "atype" : "authenticate", "ts" : { "$date" : "2021-01-05T00:21:52.628+00:00" }, "local" : { "ip" : "192.168.248.203", "port" : 27017 }, "remote" : { "ip" : "172.31.0.5", "port" : 54195 }, "users" : [ { "user" : "arn:aws:sts::555555555555:assumed-role/developer-role/", "db" : "$external" } ], "roles" : [ {…4 votesThe full ARN including the user information is now captured in audit logs when AWS IAM authentication is used with assumed roles. This is a delayed update; the change was made in 2021. Thank you for your feedback to make MongoDB better.
-
Terraform resource to provision maintenance windows
I propose creating a new terraform resource to provisioning maintenance windows.
This could be helpful to avoid setting this manually at the project level.
I'm new to Terraform but wouldn't mind to work on it, in case it makes sense.
Thanks
4 votesThis has been released in version 0.4.0
https://www.terraform.io/docs/providers/mongodbatlas/r/maintenance_window.htmlMore info on 0.4.0:
https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-provider -
Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration
Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
*sendCollectionLatencyMetrics
*sendDatabaseMetricsWe need to have these switches in the terraform provider as well.
3 votesThis is now available in the Terraform provider as of terraform-provider-1.33.0. Thank you!
-
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 votes -
Datadog integration for AP1 region
I am using Datadog region AP1 (Japan) and I learned that Atlas doesn't support the region for the integration.
It would be really great and helpful if the integration supports the AP1 region.
3 votesThe Atlas + DataDog integration does now support AP1 region for DataDog
-
Create option in terraform for keep backups after destruction
I saw that a feature was released to keep the backups of a cluster even if it was terminated. Basically the idea is to add a bool in terraform that does the work of activating or deactivating this feature, because whoever destroys the cluster using terraform does not have the option to keep the backup.
3 votesBackup Compliance Policy was released with v1.9.0 and Retain Backup flag is available in mongodbatlas_cluster and mongodbatlas_advanced_cluster in v1.10.0. Thank you for the feedback.
-
Allow configuration of Data Federation via Terraform
The
mongodbatlas_data_lake(which should be renamed to reflect the new Data Federation name) doesn't allow you to specify the configuration. Without it, there is little value in having the resource defined in terraform at all.This issue: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/561 was created over a year ago to ask for this. A comment from MongoDB indicates its in the plan, just wanted to provide a vote for it.
3 votes -
mongodbatlas_serverless_privatelink_endpoint
I'm trying to import a serverless private link endpoint but I have no success with the current resource "mongodbatlasprivatelinkendpoint". As I investigate I saw that "mongodbatlasprivatelinkendpoint" is using the "private endpoint" API not the "serverless private endpoint" API reference on this url https://www.mongodb.com/docs/atlas/reference/api/serverless-private-endpoints/ that is why its unable to get the resource I wanted to import.
It is good if we have a separate resource for the serverless private endpoint because it is the only way to securely connect to AWS without using the network peering connection. As of this writing network peering is not yet…
3 votes -
Comprehensive Backup Ransomware Protection
MongoDB Atlas needs a modern, comprehensive, secure ransomware protection strategy for its customers. Simply providing the ability to backup a database, and encrypt that database with "bring your own key" is not enough. Below I highlight what I believe are key components of a comprehensive strategy (or at least a good start).
Immutable and Verifiable Backups
Once backups are created, Atlas should provide a facility to ensure the backup remains immutable. Further, Atlas should provide verification that a backup continues to be untouched / unmodified for its entire lifecycle.
Deletion Protection
Atlas should provide enhanced deletion protection for backups. Any…
3 votesHello,
I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas.
Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.
With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.
Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.
In addition to Backup Compliance Policy, organizations can also utilize our multi-region…
-
ReadOnly DATA API
Current DATA API feature looks promising. However there is no way provide access controls around it. If you have access to API key then you can potentially do both read-write to cluster. We did some PoC recently but couldnt promote to prod because of this problem. If we get a readonly Data API access that would be super helpful.
3 votesHi all this should be completed now.
-
Allow to assign API Key to Project via Terraform by referencing public key
Currently you can only assign an API Key to an Atlas Project via Terraform by referencing the ID of the API Key. Unfortunately, the ID is not exposed through the UI, only through the Atlas API. This is not very ideal for customers/users that are creating API Keys through the UI.
Adding support for referencing the API Key in Terraform via the public key instead of the ID would fix this. Or alternatively, exposing the API Key ID in Atlas.
3 votesWe released support for Data Source: mongodbatlas_api_keys which exposes the api_key_id paramter as part of v1.8.0. Thank you for the feedback.
For more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/data-sources/api_keys#api_key_id
- Don't see your idea?