Yep - table scoped...https://twitter.com/mweagle/status/935884554597908486 …
-
-
-
Replying to @ben11kehoe @mweagle
Well, there’s always Firebase for you. That lets you go as deep as you want.
1 reply 0 retweets 2 likes -
Wait, couldn’t you use federated roles and dynamodb:LeadingKeys to go sub-table-level?
1 reply 0 retweets 1 like -
Replying to @JoeEmison @mweagle
For keys, yes. But that's like customer id. I want to regulate whether you can see their address
1 reply 0 retweets 1 like -
Replying to @ben11kehoe @mweagle
Gotcha. You’d have to do that in lambda then?
2 replies 0 retweets 0 likes -
Are you talking about attribute permissions? http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/specifying-conditions.html …pic.twitter.com/fvbdn3e3gQ
1 reply 0 retweets 1 like -
Right, but what creds are used to access DDB? Caller or service? If caller, that will probably work. If service, it’s different. I have lots of thoughts about which versions of *possible* are *good*, too
1 reply 0 retweets 1 like -
Replying to @ben11kehoe @geoff_baskwill and
I want to hear
@southpolesteve’s thoughts2 replies 0 retweets 2 likes -
I suspect a LOT of people will be pulling the escape hatch to Lambda for auth. I see VTL -> Dynamo being a path fraught with error and security problems.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.