Access Control
The Object Storage service controls access depending on which type of credentials are used to access a bucket. There are two types of credentials:
- IAM principal (users or IAM Service Accounts) credentials
- Bucket service account credentials
IAM principals
An IAM principal can be a human user or an IAM Service Account.
Both human users and service accounts can exchange their evroc access tokens for
short-lived S3 compatible credentials, which can then be used to access the S3
compatible Object Storage API. They're valid for 1 hour by default. When you
request them with the CLI you can choose a lifetime between 15 minutes and 12
hours with the --duration flag of the evroc storage bucket get-s3-credentials command.
Additionally, IAM service accounts can have long-lived S3 compatible credentials. These can be used directly with the S3 compatible Object Storage API without any additional token/credential exchange needed.
The principal must explicitly be assigned the relevant Role (with sufficient permissions) in order to be able to access a given bucket or object (see Manage role bindings).
Bucket service account credentials
Note: Bucket service accounts are a legacy concept, which is bound to be deprecated in the near future. Prefer creating IAM Service Accounts for long-lived bucket access.
A bucket service account can be created to give long-lived programmatic access to specific buckets. A given bucket service account only has access to specific buckets configured, and only within the same project as it was created in. Additionally, a bucket service account does not have permission to list buckets in a project. A bucket service account can create a new bucket, but only if that bucket has already been included in the list of buckets configured in the bucket service account.
Note: Bucket service accounts do not support fine-grained permissions. Prefer creating IAM Service Accounts.