1331 results found

1. Support tags in terraform-provider-mongodbatlas mongodbatlas_project

   terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.

   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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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 M30 Cluster with a Disk Size of 64gb and a minimum Cluster size of M10 through Terraform.
   2. The Cluster's Disk Size is scaled to 129gb
   3. Time passes.
   4. I execute/run my previously valid Terraform definition, Terraform returns a validation failure.

   ---

   This matters to us because it would simplify our MongoDB operations. "providerautoscalingcomputemininstancesize" is a parameterized value where, if empty, we use an instance size of M10. Having the deployment fail unexpectedly when updating/creating a cluster can be a frustrating experience (Especially when people do not read error messages).

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

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Serverless Instances  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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: /24

   Azure minimum imposed CIDR value/subnet size: /29
   MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21

   For 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 from IPAM does not scale when your project footprint in MongoDB Atlas grows sufficiently large.

   Attempting to combine projects into a single cohesive project for utilizing the larger IP space (as MongoDB likely intended) does not scale either. There is a soft cap on the amount of clusters which can be deployed to a project (25). The cap can be raised but concerns with monitoring, backups, and visibility into all clusters in the project becomes a concern, as well as further complicating billing and RBAC management in larger orgs.

   For customers with smaller deployments, like simple 3 node replica sets in AWS, MongoDB asking us to allocate a bare minimum of /24 (255 IPs) when only 3 IPs are needed, thats a ton of overhead on IPAM that goes to waste unnecessarily. The problem is even more exaggerated for 3 node replica sets in Azure, where the bare minimum network container size Atlas is /21 resulting in over 2000+ IPs going to waste.

   Proposed solution:
   MongoDB raise the minimum required network container size to /28 for all projects.

   Thank you

   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: /24

   Azure minimum imposed CIDR value/subnet size: /29
   MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21

   For 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… 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  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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 kindly request your assistance in clarifying whether this region is planned for future availability or if there are any alternatives that can help us meet the data localization requirements within Saudi Arabia.

   We understand the significance of data sovereignty and the importance of adhering to regional regulations. Therefore, we would greatly appreciate your guidance and support in identifying the best solution that aligns with our compliance needs.

   Thank you in advance for your attention to this matter. We look forward to your prompt response.

   Sincerely,
   Salem Yaslem

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

   0 comments  ·  Serverless Instances  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Autoscaling  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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

   0 comments  ·  Activity Feed  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. 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: 01276442

    This will provide a flexibility for the organizations to have max-session configured according to their internal security policy.

    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: 01276442

    This will provide a flexibility for the organizations to have max-session configured according to their internal… 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

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Alert for the absence of a snapshot backup policy

    It would be great to have an alert option that notifies when there is a cluster configured without a backup policy defined.

    This alert option would be helpful to ensure any defined company backup policy is audited and we are notified if a policy does not exist, or if someone accidently removes any defined policies on a give production cluster.

    6 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Backup Compliance Policy to enforce "Snapshot Distribution"

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and also makes backup compliance policy feature comprehensive/consistent covering all backup related features offered by Atlas.

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and… 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

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Support Online Archive in Azure Switzerland North region

    Please make Online Archive available in Azure's Switzerland North region

    We are using MongoDB Atlas in Azure notably to store personal health data of patients. We are based in Switzerland (which is not part of the EU), and the regulation requires that health data remains in Switzerland. We would like to use the Online Archive on Azure feature for our Atlas data but require that it is available in the Switzerland North region.

    6 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  ·  Online Archive  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.

    Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.

    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

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. View all documents in a collection on Atlas UI

    The current limitation in Atlas restricts viewing documents within collections to a maximum of 200 per view. It would be beneficial to have the functionality to scroll through all documents without encountering the message: "To view additional results, connect to your cluster using the mongo shell."

    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

    0 comments  ·  Data Explorer  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Make IP linking easy for Atlas customers deployed on Google Cloud

    I know it may not seem MongoDB's responsibility, but understanding how to get IP addresses for my Google app engine services so that I can put them in MongoDB (which for some reason wants IP addresses instead of URLs) it's difficult. If MongoDB wants to sell to Google Cloud customers they should make it easy to set up, not only for the billing.

    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

    0 comments  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. There is no way I can delete my account.

    There is no way I can delete my account. It says I have to get rid of active organizations. When I try to get rid of my organization it says I have to get rid of my active clusters. When I try to get rid of my clusters. In clusters page it says I have no clusters.
    I tried to sign out and wait but the same problem continues.

    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  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. API - Version 2

    We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

    We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
    Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

    to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
    "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

    What I need to change is only the "instanceSize":"M10", but I need to use IN A PATCH all this other parameters. It doesn't make any sense to need to inform all of this if I'm using a PATCH (it is not a PUT, it should work fine receiving only what I'm about to change)

    It would be great if this could be fixed so it would work just receiving what we want to change, or at least just receiving the parameters that v1 needed.

    We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

    We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
    Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

    to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
    "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

    What I need to change is only the… more

    35 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  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Export logs to S3 at the organization level rather than project level

    Currently if we have to export logs to S3 we need to enable log export to S3 at project level. If I multiple projects then same things needs to be done, there should be an option to send logs to S3 on organization level when setup should send the logs to S3 bucket with path name (projectname+'/'+clustername).

    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  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Support for Push-Based Logging to Azure and GCP

    Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/

    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

    2 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close