Manage S3 access
Access to S3 resources is regulated by:
- projects — determine access within an isolated resource group;
- roles — define access for control panel users, service users groups within an account and project.
- access policy — determines access within a bucket.
When an S3 action request is received, the user role is checked first. If the role is:
-
does not allow the action — access is denied;
-
allows the action — the presence and settings of the bucket policy are checked. If the bucket policy:
- not created — access will be granted to all users with access within roles, except users with the object_storage_user, s3.user, and s3.bucket.user roles;
- is created — everything not allowed by the policy rules is denied.
To access via API, automation tools, and FTP, use keys.
Learn more about access management in the Overview of access management in Selectel products guide.
Access within projects
All resources in S3 are created in a specific project. You can group resources by different projects and configure user permissions depending on which projects they need access to.
Access within roles
Access to S3 is granted by S3 roles and global roles. Learn more about role types in the Role reference.
S3 roles
s3.admin
The s3.admin role provides access to managing S3 within a project. It has no access to S3 in other projects or to other products in its project.
* Managing access policies and bypassing temporary Object Lock restrictions in the control panel is not available.
s3.user
The s3.user role grants access to the S3 bucket if an access policy is configured in it that allows this user access to the bucket. The level of access is determined by the access policy settings. Does not have access to S3 in other projects or to other products within your project.
s3.bucket.user
The s3.bucket.user role grants access to the S3 bucket if an access policy is configured in it that allows this user access to the bucket. The level of access is determined by the access policy settings. Does not have access to S3 in other projects or to other products within your project.
data_migration.admin
The data_migration.admin role grants access to managing S3 migrations.
data_migration.user
The data_migration.user role grants access to viewing created S3 migrations and managing their execution.
data_migration.viewer
The data_migration.viewer role grants access to view everything managed by data_migration.admin.
object_storage.admin
The object_storage:admin role will be deprecated soon and cannot be assigned to new users. Existing users with the object_storage:admin role can continue working.
Deprecated version of the s3.admin role. Has identical permissions.
object_storage_user
The object_storage_user role will be deprecated soon and cannot be assigned to new users. Existing users with the object_storage_user role can continue working.
Deprecated version of the s3.user role. Has identical permissions.
Global roles
member
The member role provides full access to all services. It does not provide access to managing panel users, service users, user groups, and federations.
billing
The billing role provides access to billing management without access to service management.
iam.admin
The iam.admin role provides access to user management and does not provide access to product and billing management. It does not allow managing your own account: changing permissions, managing notifications, or deleting a user. The first user with the iam.admin role is created by the Account owner.
iam.viewer
The iam.viewer role provides access to view everything managed by iam.admin.
reader
The reader role provides access to view everything managed by member within the same scope.
API Access Keys
Depending on the API type, the user will need:
- Project-scoped IAM token (X-Auth-Token). Used for access via the Object Storage API and Swift API. Can be issued to service users and panel users. To issue an IAM token to a service user, use the Get a project-scoped IAM token section of the Authenticating requests API documentation guide. It is recommended to use a panel user's IAM token for testing purposes only; for more details, see the Manage IAM tokens section of the Manage access keys guide;
- S3 key (EC2 key). Used to sign S3 API requests and for access via FTP. Consists of a pair of values: an Access Key ID and a Secret Key. S3 keys can be issued to service users and panel users. Panel users can issue S3 keys for themselves. We recommend creating service users and issuing S3 keys to them.