Skip to main content

Manage access in S3

Last update:

Access to S3 resources is regulated:

When an action request is received in S3, the user's access is first checked against the role model.If the role model allows access to the user, the access policy is checked, if not, access is denied.

For API or FTP access , issue keys.

Role model access

For more information about role model access, see the Access Control in Selectel Products manual.

member

User with full access to all services.Unavailable access control: users, service users, user groups and federations.

Access areas
  • Account;
  • project
Who can be prescribed
  • Users;
  • to service users;
  • user groups
Available operations and resources in S3

In the Account access area:

  • S3 management in all projects:
    • view the list of bucket list in all projects of the account;
    • view the contents of the bucket in all projects of the account;
    • manage objects in bucket (load, delete, etc.) in all projects of the account;
    • changing baket settings in all projects of the account;
    • configuring access policies for bucket access in all projects of the account;
    • management of projects, their limits and quotas;
    • billing management
  • management of projects, their limits and quotas;
  • billing management

In the access area Project:

  • S3 control in the selected project:
    • viewing the list of bucket list;
    • viewing the contents of the bins;
    • management of objects in the baquette (loading, deleting, etc.);
    • changing the settings of the bins

billing

User with access to billing management and without access to service management.

Access areasAccount
Who can be prescribed
  • Users;
  • to service users;
  • user groups
Available operations and resources in S3
  • Billing Management;
  • S3 consumption view

iam_admin

User with access to user management and without access to services and billing.Cannot manage his account: change permissions, manage notifications, delete user.The first user with the iam_admin role is created by the Account Owner.

Access areasAccount
Who can be prescribed
  • Users;
  • to service users;
  • user groups
Available operations and resources in S3

reader

A user with access to view everything he controls member in the same access area.

Access areas
  • Account;
  • project
Who can be prescribed
  • Users;
  • to service users;
  • user groups
Available operations and resources in S3

In the Account access area:

  • view the list of bucket list in all projects;
  • view the contents of the bucket in all projects of the account;
  • View the settings of all projects, their limits and quotas
  • viewing of billing data (balance, bank cards, report documents, partner program, etc.)

In the access area Project:

  • view the list of baquettes of the selected project;
  • view the contents of bins in the selected project

object_storage:admin

User with full access to S3 management within the project.Does not have access to S3 in other projects or other products in their project.

Access areasproject
Who can be prescribed
  • Service Users;
  • user groups
Available operations and resources in S3
  • View the list of bucket list in the project;
  • viewing the contents of the bins;
  • management of objects in the baquette (loading, modification, deletion, etc.);
  • changing the settings of the baquettes;
  • configuring the bucket access policy

object_storage_user

A user with access to the S3 bucket if an access policy is configured in the bucket that allows access to the bucket for this user.The level of access is determined by the settings of the access policy.Does not have access to S3 in other projects and other products in his project.

Access areasproject
Who can be prescribed
  • Service Users;
  • user groups
Available operations and resources in S3
  • View the list of bucket list in the project;
  • operations in the buckets that are allowed by the access policy.

Access within the access policy

If the user's role provides access to S3, access to a particular buck depends on the availability and settings of the access policy:

See the Access Policy section for more information on how the access policy works.

Keys for API access

Depending on the type of API the user will need:

Issue an S3 key to a user

For your information

An S3 key (EC2 key) must be issued to a user who is allowed access to S3 within the role model.If the user's role does not allow access to S3, the S3 key is useless.

Users with access to the control panel can issue themselves S3 keys but we recommend to create service users and issue S3 keys to them.

S3 keys can only be issued to other users by the Account Owner or a user with the role iam_admin. Service user can't get S3-key by himself, because he doesn't have access to the control panel — he must be issued a key by Account Owner or iam_admin.

A separate key must be created for each project.Multiple keys can be issued for one project.

  1. In the control panel, on the top menu, click Account.

  2. Go to the section with the desired user type:

    • Users — for users with access to the control panel;
    • Service users — for service users.
  3. Open the user page → Access tab.

  4. In the S3 keys block, click Add Key.

  5. Enter the name of the key.

  6. Select the project for which the key will work.

  7. Click Generate. Two values will be generated:

    • Access key — Access Key ID, key identifier;
    • Secret key — Secret Access Key, secret key.
  8. Click Copy and save the key — it cannot be viewed after the window is closed.