Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
55 results found
-
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 -
Terraforming IP access list for project API key
The Terraform provider supports setting up IP access lists for organization API keys with "mongodbatlasaccesslistapikey". For project API keys, however, there is no way of managing IP access lists with Terraform, and we have to do it manually using the MongoDB Atlas UI.
Terraforming this is valuable because it would allow us to document the why and the what for each IP address or CIDR block. Having it in code will also increase the visibility of these access lists to the rest of the team, as changes to project API key access lists will be code-reviewed…
5 votes -
Shared-Tier (M2 & M5 Clusters) Snapshot and Restore Jobs Resource in Terraform
Shared-Tier (M2 & M5 Clusters) Snapshot and Restore Jobs Data Sources are on the near-term roadmap for the MongoDB Atlas Terraform Provider, but is there any interest in also having a Terraform Resource as well? This way users will be able to create, update, and destroy these resources as well.
Note: there is no DELETE http method in Atlas Admin API for either Shared-Tier Snapshot or Restore Jobs (https://lnkd.in/e3-GZH6M). So this will likely have to be supported first before team can create the associated Terraform resource which is likely going to be some time away.
1 voteReleased as part of v1.11.0, try today and thank you for all the feedback!
-
Add v1.5 API support to Terraform to support asymmetric hardware
We use a base tier MongoDB cluster (M20) and an analytics tier (M30), where they are of different sizes due to different business requirements.
Currently this is not supported by Terraform unless tiers use the same hardware (e.g. either both are set to M20 or M30).
See the error message below.
Error: error reading MongoDB Cluster (development): GET https://cloud.mongodb.com/api/atlas/v1.0/groups/1234567890/clusters/development: 400 (request "ASYMMETRICHARDWAREINVALID") Asymmetric hardware is not supported by the v1.0 API. Please use the v1.5 API instead. Documentation for the v1.5 API is available at https://docs.atlas.mongodb.com/reference/api/clusters-advanced/.
Please add v1.5 API support to Terraform to support asymmetric hardware.
1 vote -
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.
-
Make optimized connection strings available from api
When creating a cluster that has Optimized Connection Strings as documented here: https://www.mongodb.com/docs/atlas/connect-to-database-deployment/#improve-connection-performance-for-sharded-clusters-behind-a-private-endpoint, those connection strings do not appear to be available through the Atlas API, and thus not available through the Terraform provider.
Since legacy connection strings are not the default anymore, it would be important to make those optimized strings available through API and Terraform.
In addition it would be nice to be able to get the legacy connection strings for old drivers even if the cluster qualifies for optimized connection strings. Those legacy connection strings are simply not populated unless the cluster was initially a replicaset…
1 votethis feature has been released as part of v1.10.0. thank you for the feedback.
for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster#connection_strings.private_endpoint.#.srv_shard_optimized_connection_string
-
Add Enable Extended Storage Sizes in terraform project settings
Add an Enable Extended Storage Sizes flag in terraform project settings
Example:
resource "mongodbatlasproject" "default" {
name = var.name
orgid = "TEST"iscollectdatabasespecificsstatisticsenabled = true
isdataexplorerenabled = true
isperformanceadvisorenabled = true
isrealtimeperformancepanelenabled = true
isschemaadvisorenabled = true
isextendedstorage_sizes = true
}1 votehi this feature has been release as part of v1.10.0. thank you for the feedback.
for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#is_extended_storage_sizes_enabled
-
Add a datasource for members of an organization
Problem: The
mongodbatlas_teamsresource only works with email addresses of user accounts which are existing members of the organization at apply time¹, and Team memberships can't (yet?) be managed via Identity Federation (third-party SAML IdP).Solution: If there was a datasource using the "Get All Organization Users" API² to return a list of organization members, that data could be used to filter the
usernamesinput attribute of themongodbatlas_teamsresource to only add valid users.Workaround: We're using a Python script as an external datasource to get the data needed to perform said filtering.
¹: An error is thrown when…
1 votethis feature has has been released as part of v1.10.0 release. thank you for the feedback.
for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/data-sources/organizations
-
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 -
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 -
Support webhook notification type for alert configurations
The
mongodbatlas_alert_configurationallows me to define a notification withtypeofWEBHOOKbut I can't complete the configuration because it doesn't seem to support any arguments to provide the webhook URL and webhook secret/integration key.Please add support for the webhook URL and secret, since otherwise the
WEBHOOKtype notification can't be used. Thanks1 vote -
Terraform feature request: Cluster Termination Protection
Termination Protection has been added. Would be great to add support for it in the terraform provider, so clusters can be provisioned and configured entirely via terraform.
Without this support, we need to perform some configuration manually in the UI.
15 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 -
Terraform Serverless VPC Endpoint configuration
Create the equivalent of mongodbatlasprivatelinkendpoint but for serverless.
8 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.
-
Disable data explorer and other features in project settings
The following features cannot be disabled in the terraform provider (project settings):
Real Time Performance Panel
Data Explorer
Performance Advisor and Profiler
Schema Advisor2 votesThe project settings can now be set via the project resource in the provider. Thank you!
-
Add autoExport snapshot to AWS S3 Bucket on mongodbatlas_cloud_backup_schedule
By company policy, we have to export our snapshots automatically to an AWS S3 Bucket.
I started following https://www.mongodb.com/docs/atlas/backup/cloud-backup/export/ and implemented on terraform due to the high number of projects, and clusters that we need to backup.
However, looks like the terraform provider doesn't support "autoExportEnabled" from https://www.mongodb.com/docs/atlas/reference/api/cloud-backup/schedule/modify-one-schedule/ on https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloud_backup_schedule terraform resource.
Best regards,
Wagner Sartori Junior9 votesThis is now out in version 1.4.2.
-
Granular permissions via roles / hashicorp vault
We are using the Hashicorp Vault Atlas plugin in order to generate credentials for Atlas.
We are able to generate roles on the Atlas end and then use those roles to provision vault users.
However, I don't see a way to restrict those roles to just certain resources/clusters.
So the user can access all the deployments in a project.
It should be possible to restrict roles to certain resources only.1 voteHi,
This has already been added some time ago. You need to specify the scopes you want to include, here's the code - https://github.com/hashicorp/vault-plugin-database-mongodbatlas/blob/master/mongodbatlas.go#L206. It should be an array like roles, but with the resource name and then if it's a cluster or data lake (see scopes here: https://www.mongodb.com/docs/atlas/reference/api/database-users-create-a-user/). I hope that helps!
Best,
Melissa
-
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
-
Add Prometheus as a Supported Third-Party Integration Settings type
Great work releasing the new Prometheus Integration functionality!
Ideally, we'd like to use Terraform to codify our interface with the Prometheus Integration, similar to how we leverage the existing Third-Party Integration Settings types.
8 votesThis is now out in version 1.4.2 of the provider.
- Don't see your idea?