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

483 results found

  1. Hyperlink to "all cases" that's under the "create new case" link

    To access the support portal from the projects page:

    • Navigate to Support to the left side of the page
    • Click on Visit Support Portal button under Request Support

    It will be easier to navigate if a hyper link of "all cases" can be added to "create new case" from the "get help" drop down as in screenshot attached.

    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)
  2. LDAP Users shouldn't be successfully authenticated if not authorized

    Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.

    Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.

    Please reject any non-authorized user from connecting to an…

    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)
  3. Monospace font for Atlas project user creation fields

    When you start a new project using Atlas, a username and password are suggested. The username and password fields use a font with almost identical lowercase L and capital i.

    My suggestion is to use a monospace font in those fields for disambiguation.

    I use a password manager on my phone (as do, I imagine, many others), which means it’s very annoying to have to figure out if a character is an l or an I on the computer every time I have to copy down info for a new 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

    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. Add a command to set cluster to read only mode in MongoDB

    Relational databases (oracle, mysql, postgres) provide a single command to change a database to read only mode. e.g. alter system set database read only; This is often used to enable read only access to a cluster that is in process of being upgraded, or provide a look back to verify functionality or setup post upgrade. MongoDB should implement such a feature.

    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)
  5. Cluster configuration protection

    I would like to request adding a configuration protection feature in MongoDB Atlas. In our client's scenario, the DBA must manage multiple clusters simultaneously, posing the risk of accidental misconfigurations. Therefore, the client's feedback is that hope MongoDB Atlas can have the option to enable configuration protection so that any adjustments or changes require disabling the configuration protection first

    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)
  6. UUID Schema Validation

    It would be very handy to have the ability to specify a schema validator using bson type UUID (binData subtype 4) instead of the more generic binData subtype 0.

    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

    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)
  7. Add UUID generation to Atlas Functions

    Atlas Functions have a utils.crypto library that offers some basic cryptography functions. One of those should be the modern crypto.randomUUID() that is now standard in ECMAScript. Currently, Atlas Functions cannot generate a UUID without resorting to third-party dependencies. I prefer using full UUIDs over Mongo's proprietary ObjectID.

    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)
  8. Improve Hashing Algorithm Choices in Atlas Functions

    Atlas Functions have a utils.crypto API that offers hashing. However, the available hashes are embarrassing: SHA1, MD5, and SHA256. I understand that not everything we hash might need security and there's a speed/security tradeoff. But not even OFFERING a cryptographically-secure modern hashing algorithm in 2023 is nuts. People shouldn't have to import third party dependencies just to get best-practice hashing algorithms. Please improve the algorithm choices.

    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. I would like to compact to oplog myself instead of opening cases to resize it

    To compact my oplog and reclaim 300GB of disk space right after I finisihed migrating a database to Atlas using mongomirror, I had to open a support case. With that we were able to reduce our cluster tier thanks to lowering the disk tier (Azure deployment)

    It would be nice to do it myself to be faster without opening a case with severity 4 that will take me at least 2 days to accomplish that. Also, I assume that people without a subscription can't do it since you have to open a case which is exclusive only if you have…

    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  ·  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. Activate bypass saml only for select users

    We have recently activated SAML SSO on our Organization and we would like to only have 1 user that is able to bypass SSO as like a "break the glass" user in case our IDP fails. It would be ideal that not every user is able to use the bypass url.

    Currently any users can use the bypass sso url

    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  ·  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. Enhanced Access to Secrets in the context.environment Object

    We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.

    This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.

    As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not…

    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)
  12. compass installation for the current connected user or for all the users.

    can you please make compass installation possible for the current connected user or for all the users on windows.

    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)
  13. Generate class-based TypeScript object models for Realm from existing schema

    The Realm SDKs -> Realm Object Models page (https://realm.mongodb.com/groups/<groupId>/apps/<appId>/sdks/dataModels) uses the existing schema to generate object models in a variety of languages. However, the TypeScript generator is out-of-date.

    RealmJs now has first-class TypeScript support, allowing you to declare your models as classes and use @realm/babel-plugin to infer the schema. If your TypeScript objects don't inherit from Realm.Object (which is the case with the models generated currently), the items returned from your queries will be of type unknown as well. But if you query using models inherited from Realm.Object everything is strongly typed.

    Please update the generator to provide…

    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. 15 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)
  15. 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)
  16. create roles with rights on wildcard database like collections

    Exemple:

    use admin
    db.createRole(
    {
    role: "UserCanCreateDbTest",
    privileges: [
    { resource: { db: "test", collection: "" }, actions: [ "update", "insert", "remove" ] },
    { resource: { db: "test", collection: "" }, actions: [ "find" ] }
    ],
    roles: [
    { role: "read", db: "admin" }
    ]
    },
    { w: "majority" , wtimeout: 5000 }
    )

    https://stackoverflow.com/questions/30462767/mongodb-grant-all-with-wildcard-role-like-mysql

    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)
  17. Set "Cluster Termination" ON as default for an Atlas organisation

    Have a button in the Atlas Org setting to toggle ON/OFF Custer Termination protection.

    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)
  18. Google Private Service Connect

    Greeting from Fivetran!

    This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.

    From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed to AWS…

    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)
  19. Restrict whitelist ip

    I would like there to be an option to restrict users to what they can whitelist in network settings for a project. I want there to be option like "only users with owner access can create non-temporary IP whitelistings" so we can avoid having our developers adding IP addresses that gets outdated and pose a potential security risk.

    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. Remove the requirement to have an API Access List CIDR before being able to manage backup schedules

    The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952

    Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
    Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedules

    Our request is that the requirement to have an API Access List to manage backup policies be removed.

    At the very least,…

    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

    started  ·  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)
  • Don't see your idea?

Feedback and Knowledge Base