3 ms·
I found this article on their IAM/ABAC service interesting: https://www.ubicloud.com/docs/architecture/attribute-based-access-control-abac https://www.ubiclou
by anonymousDan 2y ago
I found this article on their IAM/ABAC service interesting:
https://www.ubicloud.com/docs/architecture/attribute-based-access-control-abac https://www.ubicloud.com/docs/architecture/attribute-based-a...
I always wonder how the big cloud providers manage to scale their IAM services (from a distributed systems perspective) given they presumably need both low latency and some reasonable level of consistency. Anyone have any pointers to architectural descriptions/publications?
- VoVAllen 2y agoAmazon has open sourced their policy engine https://github.com/cedar-policy/cedar https://github.com/cedar-policy/cedar
- otterley 2y agoCedar is not the policy engine used by AWS IAM. Other AWS services do use it, though: https://www.cedarpolicy.com/en/integrations https://www.cedarpolicy.com/en/integrations
- rrdharan 2y agoZanzibar: Google’s Consistent, Global Authorization System https://research.google/pubs/zanzibar-googles-consistent-global-authorization-system/ https://research.google/pubs/zanzibar-googles-consistent-glo...
- anonymousDan 2y agoThanks, this looks interesting.
- giovannibonetti 2y agoWouldn't a geo-replicated single-primary DB suffice? Reads would have low-latency, and only writes would pay for the latency to reach the primary far away.