Administrator’s Command Line Guide

Chapter 3. Accessing Storage Clusters via S3 Protocol
# ostor-ctl get-config
SVC_ID TYPE URI
0800000000000000 NS vstorage://stor1/s3-data/services/0800000000000000
0800000000000001 NS vstorage://stor1/s3-data/services/0800000000000001
0800000000000002 NS vstorage://stor2/s3-data/services/0800000000000002
1000000000000003 OS vstorage://stor1/s3-data/services/1000000000000003
1000000000000004 OS vstorage://stor2/s3-data/services/1000000000000004
1000000000000005 OS vstorage://stor1/s3-data/services/1000000000000005
HOST_ID HOSTNAME URI
0fcbf5602197245da host510:2530 vstorage://stor1/s3-data
4f0038db65274507 host511:2530 vstorage://stor1/s3-data
958e982fcc794e58 host512:2530 vstorage://stor2/s3-data
953e976abc773451 host513:2530 vstorage://stor2/s3-data
3.3 Managing S3 Users
The concept of S3 user is one of the base concepts of object storage along with those of object and bucket
(container for storing objects). The Amazon S3 protocol uses a permission model based on access control
lists (ACLs) where each bucket and each object is assigned an ACL that lists all users with access to the given
resource and the type of this access (read, write, read ACL, write ACL). The list of users includes the entity
owner assigned to every object and bucket at creation. The entity owner has extra rights compared to other
users. For example, the bucket owner is the only one who can delete that bucket.
User model and access policies implemented in Acronis Storage comply with the Amazon S3 user model and
access policies.
User management scenarios in Acronis Storage are largely based on the Amazon Web Services user
management and include the following operations: create, query, and delete users as well as generate and
revoke user access key pairs.
You can manage users with the ostor-s3-admin tool. To do this, you will need to know the ID of the volume
that the users are in. You can obtain it with the ostor-ctl get-config command. For example:
# ostor-ctl get-config -n 10.94.97.195
VOL_ID TYPE STATE
0100000000000002 OBJ READY
...
Note: As ostor-s3-admin commands are assumed to be issued by object storage administrators, they
do not include any authentication or authorization checks.
30