> suitable for corporate granularity but then too complex to be used by a startup or a project To some extend. It’s perfectly possible to make a role that allo

> suitable for corporate granularity but then too complex to be used by a startup or a project To some extend. It’s perfectly possible to make a role that allows S3 access to any action on everything, but still restricts the service from operating on any of the other 400 AWS services (unlike root credentials)