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

480 results found

  1. general cpu class for M400 and M600

    Currently when selecting M400 or M600 only "Low CPU" class is available. Our only option to increase CPU is going back to M300 with "General" class to get 96cpu. We would benefit a lot from "General" option of 128cpu and 160cpu.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add a Atlas control plane in UK region

    Currently Atlas control plane IP addresses originate from your AWS us-east-1 region. With our region being UK, security team does not like request into our network originating from US.
    Request a control place in UK region.

    2 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

    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Atlas dedicated tier is not actually dedicated

    MongoDB Atlas, despite the documentation and Atlas UI reflecting M10+ as dedicated tier, is not actually dedicating all resources. While CPU and Memory can be considered dedicated, storage is not dedicated until M300+. After working with MongoDB Support, and support working with AWS support, our performance issues were identified by a noisy neighbor who was choking our disk IOPS even though we are running M40_NVME clusters which are supposed to be high performance.

    MongoDB should at a minimum highlight this as a consideration for latency sensitive deployments.

    A new Atlas alert should be created to identify issues where slow 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Mongodb Atlas Malaysia AWS regions

    Malaysia region is poised to be the largest AWS region and it is pertinent that Atlas can support it for south east asia. Writing in to petition of this region's support.

    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

    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Show warning when user is configured with access to invalid resources

    When an invalid resource is specified in data plane user's access policy ("grant access to") authentication errors are misleading.

    For Example: if user "John" is limited access to cluster "xo" but cluster is created as "x0" by mistake, when John is authenticated against "x0" we simply get "user not found error" in client.

    If the Atlas UI can highlight the potential error, that cluster "xo" is not found, as cluster cannot be implicitly created. it will save valuable time for developers debugging entitlement issues.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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/

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Higher memory hardware option in NVMe

    By experience, an optimized MongoDB usually needs more IO and memory, so we can enable a horizontal scale during the live incident.
    So a larger memory SSD would be preferred.
    For AWS, eg. x2iedn or x8g(require to switch ARM) would be an option.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Improve labeling experience in Network Access

    I see option "add my current IP address in allow list" quite handy.
    After I click that button there is no labeling option near.
    I could use a search bar of browser to find a recent ip address but that is too tedious.

    I want labeling input just after added the address into allowed list.

    One more cool option would be to choose a label color.

    That way I can manage or distinguish all addresses/hosts simply in a instant look.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. In the Project Overview interface of Atlas, show users that the set of clusters is incomplete

    In the Project Overview web interface, in the Clusters pane, four of our clusters are listed. I am new to our MongoDB deployment and to this UI. I had no way of concluding we had more than four clusters. I thought that was the complete list.

    I feel strongly that if you are going to show only a subset of clusters in a UI, you need to also give users some visual clue that this is only a subset, that the list is incomplete, and that more can be found somewhere.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Granular permissions needed with Federated Authentication in Atlas

    Granular permissions needed with Federated Authentication in Atlas
    For example(but not limited to), it would be good to assign to an external role, via Federated Authentication:
    -to create RS users;
    -to restore a RS.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Control Over how to upgrade minor versions or rollback if required

    Hello Team,

    We recently faced an issue with the automatic minor version upgrade that rolled our clusters from 6.0.16 to 6.0.17 through Atlas. Since 6.0.17 has some problems, can we request the following features:

    1. Disable automatic upgrades of minor versions.

    2. Allow manual rollback to previous minor versions when necessary.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Alerting mechanism to notify when the node internal/external IP changes for MongoDB Atlas Cluster node

    We would need an alerting mechanism to notify the team when the node external/internal IP changes. This helps us to troubleshoot the problem quicker and can change in the firewall configuration quickly.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Unblock users in Russia and Belarus

    Currently MongoDB blocks access to MongoDB Atlas for users who are located on the territory of Russian Federation, Belarus (and other countries).

    MongoDB Support team confirmed this is the case and stated that the reason is US regulations and sanctions, referring only to the blog post published on their website (https://www.mongodb.com/blog/post/mongodb-assistance-ukraine-shut-down-work-russia). The blog post does not mention that the access to users is blocked.

    To our best understanding not many other tech companies have implemented such strict measures.

    We've also taken the time to delve into the sanctions topic and have reviewed every public release of sanctions on…

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Authority Root/Intermediate Certificate from Let's Encrypt update

    Need to be notified when Authority Root/Intermediate Certificate from Let's Encrypt will be upgraded. It can be a alert/rss flow/notification/email to inform the customer company.
    From documentation https://www.mongodb.com/docs/atlas/reference/faq/security/#hard-coded-certificate-authority (Which certificate authority signs MongoDB Atlas TLS certificates?)

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Ability to schedule "Hedged read" Turn on/off

    Customer experienced read latency during maintenance after sharding.
    Our guidance is to turn on "Hedged read" option.
    So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.

    Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.

    8 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

    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. The oplog configuration is a bit confusing

    The oplog configuration is a bit confusing. I think it's not clear that if we set the oplog window, we don't need to set the maximum oplog size. I believe this configuration should be more specific.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. cloud.mongodb.com,Since this week, it often cannot be opened

    cloud.mongodb.com,Since this week, it often cannot be opened

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Atlas - Queue cluster pause request to perform it when it's possible

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 23 24
  • Don't see your idea?

Feedback and Knowledge Base