Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

139 results found

  1. Define Default Backup Policy

    The ability to save a custom backup policy as the default, so all new clusters don't have to be customized to meet the backup policy requirements.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Admin →

    Hello,


    I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that enables the ability to define a default backup policy.


    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.



  2. Add Terraform resource for custom database roles

    Could we have a Terraform resource for creating custom database roles?

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Allow to add tags to Atlas Project Clusters

    Tagging resources is not a new idea and it is widely used across cloud/service providers, that allow the operators to use tags to better identify deployed business resources.
    Today, this is not available, making it harder to create processes that allow operators to identify deployed resources, in particular deployed clusters. Leading operators to use the cluster name or project name to build strict hierarchies, to distinguish, as an example, which projects or clusters are development or production by providing a prefix or suffix. This approach is brittle, since you cannot change the name of a cluster (or want to) needing…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. 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…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Admin →
  7. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Alerts  ·  Admin →
  8. Automatic backup outside Atlas

    For DR strategy, one need to have its backups outside Atlas.
    This can be achieved in several ways. Some are:
    - Provide APIs to download the current backups and let the customers automate this on their side
    - Write backups in the customer provided cloud account (aws s3, azure blob stroage...) My favorite option

    I found many ideas related to my needs, but they were too specific. This need is more general: just provide a way to have backups automatically outside of atlas.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Backup  ·  Admin →
  9. Ability to delete account

    I really need to delete my account as this is not what I am looking for.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Other  ·  Admin →
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Online Archive  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. 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\_project terraform 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi 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

  15. Support for tagging clusters in Atlas

    Please allow tagging at a cluster level. This will help in storing related metadata if required.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  IAM  ·  Admin →

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

  • Don't see your idea?

Feedback and Knowledge Base