Learn what happens to your existing ACL-based permissions when Vultr enables IAM. ACL rules are mapped to equivalent IAM policies to preserve current access.
When IAM is enabled for your account, your existing ACL-based access is not disrupted. Vultr performs a background migration that maps each of your existing ACL entries to an equivalent Vultr-managed permission policy and assigns them automatically. The result is that all users retain exactly the same effective access they had before, just represented through the IAM system rather than raw ACL flags.
IAM becomes the source of truth for authorization while existing ACL-based enforcement continues to function with no regressions. A background job runs as a fallback to ensure eventual consistency.
Some ACLs implicitly grant other ACLs. For example, acl_provisioning implicitly grants acl_subscriptions and acl_subscriptions_view. The corresponding managed permission policy accounts for these implicit grants, so effective permissions remain identical after migration.
0 Comments
Be the first to comment and share your perspective with the community.