151 results found

1. Add a datasource for members of an organization

   Problem: The mongodbatlas_teams resource 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 usernames input attribute of the mongodbatlas_teams resource 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 trying to add a user who hasn't logged into Atlas or isn't part of the organization: 401 (request "NOT_USER_ADMIN") The currently logged in user does not have the user administrator role for any group, team, or organization containing user.

   ²: https://www.mongodb.com/docs/atlas/reference/api/organization-users-get-all-users/#get-all-organization-users

   Problem: The mongodbatlas_teams resource 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 usernames input attribute of the mongodbatlas_teams resource 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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  Zuhair responded

   this 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

2. Support webhook notification type for alert configurations

   The mongodbatlas_alert_configuration allows me to define a notification with type of WEBHOOK but 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.

   https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration#argument-reference

   Please add support for the webhook URL and secret, since otherwise the WEBHOOK type notification can't be used. Thanks

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →

3. Having tag/label in the Atlas UI

   Hello,

   The ATLAS portal used to view our organizations, projects, deployments, etc... does not offer a tag/label functionality at the visual interface level.

   This is problematic because when managing multiple organizations, projects, and deployments. We need to be able to put metadata on these objects/components (organization, project, deployment, user, custom group, API Key, Network address) in order to properly manage our inventory.

   In Azure, this notion of "tag" is very useful and can be used on all types of components (See attached image which presents tags that we have on an Azure component used for encryption at rest).

   We would like to have this functionality on the Atlas visual interface. I know there are "labels" that can be added to Atlas components/objects via APIs. Unfortunately, these do not appear on the screen.

   I hope you have the agility to make this feature available within an acceptable timeframe.

   Hello,

   The ATLAS portal used to view our organizations, projects, deployments, etc... does not offer a tag/label functionality at the visual interface level.

   This is problematic because when managing multiple organizations, projects, and deployments. We need to be able to put metadata on these objects/components (organization, project, deployment, user, custom group, API Key, Network address) in order to properly manage our inventory.

   In Azure, this notion of "tag" is very useful and can be used on all types of components (See attached image which presents tags that we have on an Azure component used for encryption at rest).

   We would… more

   • 

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Resource Tagging  ·  Delete…  ·  Admin →
   completed  ·  AdminTonya (Sr. Product Manager, MongoDB) responded

   I'm excited to announce that we recently released tags on database deployments. Check it out today.

   https://www.mongodb.com/docs/atlas/tags/

   
   

   Tags on projects is coming soon! If you want to be one of the first to test out tags on projects, let me know!

4. 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 Junior

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

   This is now out in version 1.4.2.   

5. A metric of availability of a cluster mongodb atlas for building my SLO

   Hello
   As other databases provider , their databases services (like postgresql ....) give metrics on availability of a the service (ex: postgres.canconnect) . I would like to have some metrics on the availibity of a cluster mongodb atlas for building my SLO:
   ex: mongodb.canconnect

   Thanks,

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  2 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →

6. Allow backup download through PrivateLink

   We need the ability to download our backups via PrivateLink connection. Our clusters aren't reachable via VPC peering as we solely use PrivateLink. The existing download capability doesn't support a PrivateLink URL to download our backups through.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   completed  ·  AdminKaylee (Admin, MongoDB) responded

   For Atlas clusters hosted on AWS and Azure with private endpoints configured, Atlas now enables you to download the snapshot via the private endpoints within the same region as the snapshot via both the UI and Admin API.

   
   

   Documentation can be found here.

7. Shared Clusters upgrade to MongoDB 6.0+

   Currently MongoDB 6.0.1 is only available in dedicated clusters (M10+) and in serverless clusters.

   We need to use MongoDB 6.0.1 or higher in the shared cluster (M0/M2/M5).

   I understand that this should be in the roadmap anyway, but getting it sooner than later would be great.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

8. Please add datadog US3 site also for the integration with MongoDB atlas

   Please add datadog US3 site also for the integration with MongoDB atlas

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   6 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
   completed  ·  AdminTonya (Sr. Product Manager, MongoDB) responded

   The US3 Datadog site is available.

9. Return private endpoints for peered network from mongo-db prometheus discovery endpoint

   We are using VPC peering to connect with Mongo Atlas. With the recent account about, prometheus integration. We added scrape config to mongo-db discovery API. However, scraping times out. Upon checking further it is found that discovery API returns public endpoints not private ones. Hence connection is failing. Is there a way that discovery API can send private endpoints.

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Alerts  ·  Delete…  ·  Admin →
   completed  ·  AdminFrank (Admin, MongoDB) responded

   I'm happy to announce that the Prometheus integration does now support VPC peering. This can be configured in the Prometheus configuration modal in the user interface when using the HTTP SD discovery method.  

   
   

   More information on how to configure this can also be found here: https://www.mongodb.com/docs/atlas/reference/api/third-party-integration-settings-discovery/#request-query-parameters

10. 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 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    This is now out in version 1.4.2 of the provider.  

11. To not to delete the most recent backup when the DB is deleted

    After a cluster is terminated in MongoDB Atlas, the backups disappear with it. It will be good to preserve the most recent backup of this database. Otherwise, there is no point to have backup if the DB cannot be recover after accidental delete

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Backup  ·  Delete…  ·  Admin →

12. Support tags on Mongo projects

    I support multiple orgs and projects falling under my enterprise. I'd like the ability to tag projects using a key value pair - similar to GCP, Azure, AWS. Tags will help us organise and understand what's running in our projects.

    Basic functionality that operates on tags will be helpful like filtering projects and enhanced billing that can group costs based on a tag would be beneficial.

    Right now, we need to add cost metadata to the project name, which is the only place where we can do so.

    33 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Resource Tagging  ·  Delete…  ·  Admin →
    completed  ·  AdminTonya (Sr. Product Manager, MongoDB) responded

    I'm happy to share that this capability is now available in Atlas. You can use the Admin API or Atlas UI to add tags to new or existing projects. This functionality will be extended to Terraform and the Atlas CLI in the near future.

    
    

    http://www.mongodb.com/blog/post/enhanced-atlas-functionality-introducing-resource-tagging-for-projects 

13. Configure --jsonFormat=canonical flag in export policy.

    JSON does not support all data types that are available in BSON. This means that when using JSON there will be a so called "loss of fidelity" of the information.
    However, using the --jsonFormat=canonical flag in a mongoexport command will preserve all available BSON data types, so the "loss of fidelity" issue can be completely avoided.

    Now we plan to export our cloud backups to an AWS S3 bucket. To do this, we would like to set up an export policy to automatically export the snapshots. We could already do this via the API. However, the data is output in relaxed mode. However, because of the "loss of fidelity" issue, we need canonical mode.

    MongoDB Support has already told us that there is currently no way to specify in the export policy that --jsonFormat=canonical should be used.

    However, we absolutely need this format flag and in the future we will certainly not be the only ones with this request.

    JSON does not support all data types that are available in BSON. This means that when using JSON there will be a so called "loss of fidelity" of the information.
    However, using the --jsonFormat=canonical flag in a mongoexport command will preserve all available BSON data types, so the "loss of fidelity" issue can be completely avoided.

    Now we plan to export our cloud backups to an AWS S3 bucket. To do this, we would like to set up an export policy to automatically export the snapshots. We could already do this via the API. However, the data is output in… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Backup  ·  Delete…  ·  Admin →

14. 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

    https://www.mongodb.com/docs/atlas/tutorial/integrate-msft-teams/#std-label-integrate-with-microsoft-teams

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    This is now out in version 1.4.2. 

15. 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 attacker with privilege escalation can delete backups, then take control of the database. There should be a MFA and/or multi-step/multi-person backup setting that customers can enable. This could enable a requirement of at least two factors before deleting a backup. Alternatively, it could also provide the ability to turn on a feature that would require two humans to "sign off" on the deletion of a backup.

    (extra credit) Air Gapped Backups

    An "extra credit" feature would be to have the ability to store a copy of each backup in an air gapped storage solution.

    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… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Delete…  ·  Admin →
    completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

    Hello,

    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 Snapshot Distribution to automatically copy backups (snapshots and oplogs) to additional Atlas regions. If your primary cloud experiences a region outage then Atlas will be able to recover with a copied backup from another region, just like any normal restore.

    Hello,

    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… more

16. 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 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  Zuhair responded

    We 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

17. killop

    I have read the other two suggestions on providing more killOp() and read Andrew's comment on the difficulties in the medium term.

    I just watched a situation where a primary became unresponsive and the queues piled up. The solution was to cause an election, but the dba wanted to kill operations by user (the application user) and couldn't.

    It would be nice to have something more than the real-time panel, which in this situation had become unresponsive as well so it was no use, such as a DBA console where an authorized dba could kill operations started by other users.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Delete…  ·  Admin →

18. 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 Advisor

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    The project settings can now be set via the project resource in the provider. Thank you!

19. Support tags on Mongo databases

    I have been supporting multiple projects/clusters with databases from different business units.

    I'd like the ability to tag databases using a key value pair - similar to GCP, Azure, AWS. Tags will help us organise and understand what's running in our clusters and ensuring a more efficient/granular billing process.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Delete…  ·  Admin →
    completed  ·  AdminTonya (Sr. Product Manager, MongoDB) responded

    I'm excited to announce that we recently released tags on database deployments. You can now better organize and manage Atlas resources by applying tags to categorize database deployments based on your unique business needs.

    https://www.mongodb.com/docs/atlas/tags/

    
    

    Check it out today! You can apply tags to new or existing clusters or serverless instances.

    
    

20. Ability to create GovCloud projects

    Need ability to "Designate as a Gov Cloud regions-only project" when creating projects in order to allow subsequently creating clusters in Gov Cloud regions

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →