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
  1. NodeJS Trigger Dependencies

    I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow transactionLifetimeLimitSeconds to be modified from Atlas

    We need to be increasing the default value of transactionLifetimeLimitSeconds to larger numbers (usually 300 instead of default 60). Considering number of clusters we running / we are going to be spinning up in the future its cumbersome to keep requesting this change from support. Instead please allow us to set or modify this from the Atlas GUI.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Determine programmatically if maintenance includes server version upgrade

    Recently, Atlas introduced a feature that shows a cluster will have its MongoDB server version upgraded to the next dot version. This is displayed on the cluster card in the UI. However, this information is not surfaced in the Activity Feed or through any maintenance endpoints in the API. We would like to be able to identify when maintenance includes a MongoDB server version upgrade and do so programmatically.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Ability to provide IP addresses as a list for Network Access

    When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. Include security group and tag for privateLink setup

    On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:

    • include or modify "security group"
    • attach a "tag = name"

    That way when user has the AWS CLI command generated, it includes security & tag

    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  ·  Flag idea as inappropriate…  ·  Admin →
  6. Comments on Private Endpoints to aid identification

    On Atlas when creating private endpoints, add comments field to allow easier identification.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  7. if we had option for diabling javascript execution on database we would have to no worry about it

    javascript excuiton can be used for harm and mass deletion data. İf we had no javascript execution we would be safer.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. configure IP whitelisting on database user level

    enable the user creation to have the following option

    authenticationRestrictions: [
    {
    clientSource: ["<IP>" | "<CIDR range>", ...],
    serverAddress: ["<IP>" | "<CIDR range>", ...]
    },
    ...
    ],

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Cluster version overview on Owner level

    We have partially older mongoDB versions running on our clusters. We get notified about it by EOL mails from mongoDB. However, as an org owner, I cannot see which clusters are affected. This makes it extremely time consuming for me to identify the relevant contacts per cluster. Our org structure entails self-sufficient teams with independent accountability of the mongoDB clusters. There is no central contact person.

    It would be desirable to be able to call an overview of all clusters with the respective installed version in the GUI with owner rights.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  10. ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps

    In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.

    As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.

    Please provide a way to simply ignore the notimeout option, instead of breaking its connection.

    Thanks!

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. SNMP

    Enable SNMP setup on Atlas Resources.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add MFA status to the API

    A field indicating whether MFA is on for organization users (i.e. on https://docs.atlas.mongodb.com/reference/api/organization-users-get-all-users) would be extremely useful!

    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  ·  Flag idea as inappropriate…  ·  Admin →
  13. MongoDB Orphaned Docs Utility

    When we upgrade MongoDB there is the possibility that orphaned collections that need to be deleted can prevent the upgrade from completing.

    It would make sense for Atlas to include a proactive utility that searched a customers sharded cluster for orphaned docs and gave them the option to clean up the orphaned docs ahead of a major version upgrade.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. IO throttling

    Atlas should be able to throttle IO in a way that does not allow excessive IO to degrade a node or take a node offline. Current functionality has no defense against a high IO data job other than to allow a node to fail.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  15. Governance rules at the organization level

    Hello team,

    Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.

    For example:
    Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)

    Check the allowed IP (IP Access List) addresses

    Disable the use of SCRAMS accounts for database access.

    Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  16. Redirection of ATLAS activity feed to a MongoDB cluster that we own.

    Hello team,

    Would it be possible to have a feature to redirect activity logs from ATLAS to a MongoDB cluster.

    The idea is to be able to easily retrieve these logs with Kafka Connect and also to be able to easily query in these logs.

    One could configure the redirection of activities at the organization and projects level by providing the Atlas cluster to use and the access accounts.

    Example:
    Main organization
    - Project: "Activity Feed"
    - - Cluster: "Activity Feed Cluster"
    - - DB: "Atlas Activities by organization"
    - - - Collection: "Activities by project"

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support for delayed replicas

    It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.

    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

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Setup activity feed retention

    It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  19. major version downgrade request (4.0 to 3.6)

    Right now I am running the MongoDB cluster on 3.6. Now I want to upgrade this cluster to 4.0. But when I want again to revert back to 3.6 I have no option to downgrade.

    Use case :

    Right now our production is running on 3.6, when we upgrade this to 4.0 and if we face any major issues on prod, then we have no option to get back to old version 3.6.

    Without this option we cannot move our production to 4.0.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  20. Provide an option to block access for certain username and source IP

    We would like to provide users an access to database from our VPN to browse the data with some database tools - this access should be read only. As for now if somebody connected via VPN and uses production credentials he will be able to write to the database. To be able to configure it I think Atlas should provide a IP whitelist/blacklist during the user creation becaouse global Access Lists are not enough.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base