468 results found

1. Amazon Lambda

   I wish they could provide the arn service with lambda.

   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

   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

2. support

   Being unable to lodge a support ticket without paying for a support plan - when we are paying for a premium service is seriously f'ed up

   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

   1 comment  ·  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

3. Editing custom Role and Action toggle issue

   When adding or editing a custom role in Atlas - When I expand/collapse the Actions or Roles in dropdown, it also toggles the checkboxes. So, when I want to see the roles and actions available, it also checks/unchecks the checkbox, which makes editing the actions in roles difficult.

   Please click on highlighted areas in Atlas, as shown in screenshot attached

   Thanks.

   •  

   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

4. Alerts "Users do not have two-factor authentication enabled" should name violators

   In the email for alerts of type "Users do not have two-factor authentication enabled" it would be helpful to see the user id of the “violator” (user which does not have two-factor authentication enabled), so that I don’t even have to click and log in to Atlas.

   Maybe this could be make optional, if there are privacy/security concerns about sending around the user ID in cleartext.

   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

   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

5. Increase the Contrast of the Delete Document Button

   The delete button with low contrast is the one that appears after you click the delete icon on for a document on the collections screen.
   The button text is white on a pink background.
   See attached file.
   It is hard to see the button.

   •  

   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. Expose oauth apps to let other services integrate with Atlas

   Expose oauth apps to let other services integrate with Atlas, this way other platform can integrate with atlas for provisioning a mongodb instance.

   It would allow for a lot of opportunities for developers like automatic mongodb provisioning for a deployment platform

   Right now if you deploy with platforms like Zeit or Heroku you have to create a mongodb database and whitelist the right iP manually

   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

   1 comment  ·  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. There should be a way to try MongoDB beta versions in Atlas

   As we move into a more stable version of testing the 4.4 beta it would be useful to allow beta-testers to spin up a cluster with the beta version of MongoDB. Right now beta testers have to download MongoDB which means for some of the more exotic server features in 4.4 they have to build a sharded cluster or replica set. This would be much easier to do in Atlas.

   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

8. Make a more realist design, with hack themes, and fancy UI

   Please look at the images, try to make similar UI, it would improve a lot the productivity

   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

   1 comment  ·  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

9. Stitch CLI error messages - account/publicApi redirect fails

   Stitch CLI error messages are obsolete.

   I'm having difficult with connecting to a Stitch app and the 403 forbidden returns a message to check https://cloud.mongodb.com/v2#/account/publicApi but it redirects to /overview.

   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

10. Show billing amount on top all the time

    Would be nice if I can see my current billing on top all the time, even in Atlas, like it used to be before UI change. Thanks.

    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

    1 comment  ·  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. Support multiple LDAP servers and TLS connection options

    When integrating my Atlas project with an LDAP service, we want to specify multiple LDAP servers rather than just one, and to specify options for the TLS connection such as allowing invalid hostnames. Both of these can be done in self-managed MongoDB Enterprise.

    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

    1 comment  ·  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

12. Login auto-redirects to 2FA screen but shouldn't, or offer logout

    I have three MongoDB Atlas logins and when I visit the Atlas login page it then redirects me to the 2FA page.

    I actually just want to swap between accounts, so either a logout option would be useful, or let me return to the login screen from the 2FA screen. Unfortunately if I click 'back' the app forwards me back to the 2FA screen.

    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

13. Allow me to pay for a month of "developer" level support without committing to a subscription

    AWS lets you pay for a month of support at any time.
    My understanding of MongoDB support is that if you discontinue support and then start again a year later, you have to pay for all the interim months.
    Another way of doing this would be to pay per-incident. I like the monthly model better because it would work for people just getting started to ask a lot of questions.

    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

    1 comment  ·  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

14. Zapier Integration

    Currently The Mongo Atlas connection string is not supported by Zapier! What??

    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

    1 comment  ·  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

15. Provide UI to test failover of a sharded cluster

    Currently we can test failover of replica set to test that application gracefully handle elections etc. I'd like to see a way to do the same for sharded clusters. Maybe this could turn off a random mongos router node at the same time as trigger an election on one of the shards.

    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

16. Atlas MongoDB Users Page has Confusing Role Assignment

    There is currently some confusion that has been introduced in the UI regarding the “old” way of specifying namespace-level roles and the “new” way that is used when using custom roles in Atlas.

    Let's say I create a user, hi, with the readWrite default role on funkydb:

    https://cl.ly/bf42cae9383b/Image%202019-02-27%20at%2010.21.46%20AM.png

    And create a separate MongoDB user, hi_again, assigned the funkydbreadwrite custom role (which is defined the same way, with the readWrite default role on funkydb):

    https://cl.ly/0b0b1ee50722/Image%202019-02-27%20at%2010.22.48%20AM.png

    These two roles are essentially the same, but the UI in the MongoDB Users tab renders them differently:

    https://cl.ly/5cc211e2c7d7/Image%202019-02-27%20at%2010.19.40%20AM.png

    In the example described above, the @admin and @funkydb portions in the "MongoDB Roles" column seemingly have different definitions even though both are functionally the same.

    A few suggestions for improving the UI:

    • Have all user roles specified with @admin in the MongoDB Users tab, that way there is no confusion with regards to where these role definitions are stored (in the admin database). Any references to @namespace other than @admin should not be used in the MongoDB Users’ “MongoDB Roles” tab (https://cl.ly/a4a7fa3710f1/Image%202019-02-27%20at%204.28.31%20PM.png). The current UI implies that these users are stored on that database, which we know not to be the case.
    • Custom roles should be linked in the "MongoDB Users" tab to the actual Custom Roles that is is referring to (https://cl.ly/014f6e327dd0/Image%202019-02-27%20at%204.29.22%20PM.png), or at the very least to the "MongoDB Roles" tab. For extra clarity, the modal should actually pop up for that custom role to give the user the full picture of what that role does.
    • I've always found calling out the namespace in the MongoDB Users tab if they were defined with a default role through the old UI (by clicking "Add Default Privileges" in the modal window) to be confusing, especially given that we now have custom roles that specify @admin by default. We should probably have an additional column in the MongoDB Users tab that notes which namespaces the role in question is scoped to, to make it more explicit. As in the prior suggestion, the "MongoDB Roles" column would still be changed to @admin in all instances, and this would be a new column to indicate which namespaces the role is being applied to.

    There may be some aspects of this that I overlooked, however the current implementation leaves a lot to be desired, and can be difficult to reason about from just looking at it from the customer side of things.

    There is currently some confusion that has been introduced in the UI regarding the “old” way of specifying namespace-level roles and the “new” way that is used when using custom roles in Atlas.

    Let's say I create a user, hi, with the readWrite default role on funkydb:

    https://cl.ly/bf42cae9383b/Image%202019-02-27%20at%2010.21.46%20AM.png

    And create a separate MongoDB user, hi_again, assigned the funkydbreadwrite custom role (which is defined the same way, with the readWrite default role on funkydb):

    https://cl.ly/0b0b1ee50722/Image%202019-02-27%20at%2010.22.48%20AM.png

    These two roles are essentially the same, but the UI in the MongoDB Users tab renders them differently:

    https://cl.ly/5cc211e2c7d7/Image%202019-02-27%20at%2010.19.40%20AM.png

    In the example… 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  ·  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

17. Middle Clicking MongoDB Account should open a new tab
    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

18. Support HITRUST certification for Atlas

    Some companies want a certification from HITRUST https://hitrustalliance.net/about-us/ in order to put workloads in the cloud

    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

    1 comment  ·  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

19. Pause and Resume clusters needs a timestamp in the JSON

    Currently clusters can only be paused for 7 days. After that period they must be resumed for at least one hour. However the time of resumption is not included in the result from the resume REST call. If that data was included a script could determine easily when to pause a cluster again after maintenance jobs are finished.

    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

    1 comment  ·  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. Allow to Peer with VPC's that doesn't follow Private Networks Ranges

    Allow to Peer with VPC's that doesn't follow Private Networks Ranges

    Currently I have one infrastructure based on a VPC with the CIDR range of 30.0.0.0/16, and I'm unable to make it safe with VPC peering because of the restrictions on this.

    https://docs.atlas.mongodb.com/security-vpc-peering/

    I thinl that allowing to peer with any AWS VPC's that do not overlap would be nice, as it is difficult to change the VPC when you have a running infrastructure, just to integrate safely with MongoDB Atlas

    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

    1 comment  ·  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