Skip to content

Paul

My feedback

2 results found

  1. 30 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

    6 comments  ·  Atlas » 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)
    Paul supported this idea  · 
    An error occurred while saving the comment
    Paul commented  · 

    This is a critical missing feature for using Atlas with modern AWS VPC's. Allowing multiple CIDR's in as single VPC is now a fundamental part of AWS VPC architecture. Not being able to address multiple ranges from Atlas makes it impossible for us to make use of this feature, which we need to be able to support enough IP's in our VPC's for all the resources they contain.

  2. 86 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

    12 comments  ·  Atlas » IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Paul commented  · 

    Agreed. It is very tedious and error prone to have to create individual custom roles for every database.

    I'd add that when assigning the custom role to a user then at that point it can be applied against specific databases. This is how the built in roles currently work and would continue to allow a user to be tied to a single DB, but the extra control of their access rights given by custom roles. All without having to create a separate custom role for each user/db combo.

    Paul supported this idea  · 

Feedback and Knowledge Base