Björn
My feedback
3 results found
-
417 votes
An error occurred while saving the comment Björn
supported this idea
·
-
7 votesBjörn
supported this idea
·
An error occurred while saving the comment Björn
commented
This would be very useful so we do not have to struggle with fine grained permissions / roles on the control plane but simply have a policy mechanism for the whole organization. Especially in the context of App Services where everybody has to be Project Owner to do something useful it seems to be a simple solution to just prevent unwanted features (like not allowing anonymous authentication or whitelisting of ips not known to the enterprise or disabling ssl or or or ... there seems to be some points where this can made thinks easier for enterprises or regulated companies like us.
-
36 votesBjörn
supported this idea
·
An error occurred while saving the comment Björn
commented
Would appreciate a streaming solution for the audit logs to Splunk as well. The solution mentioned by Andrew (push-based integration for logs to S3) would work for us as well. So where can I upvote for this solution ;-)
I voted for this but I came to a point where I have to say: it would be much more useful for an organization like ours (regulated) to have policies on an organization level that prevent unwanted settings espacially in App Services (like creating endpoints or allow anonymous authentication or just creating ip access lists .... there are tons of such settings) ... so if I have to decide between having fine grained permissions or policies to prevent unwanted/mistakenly made settings I would go with the second. By the way it seems that Atlas has to do some heavy lifting with the fine grained permissions compared to the time this is an open and whished feature ... ;-)