SysEleven Stack provides S3 compatible Object Storage.
It stores and retrieves arbitrary unstructured data objects via a RESTful, HTTP-based API. It is highly fault tolerant with its data replication and scale-out architecture. In its implementation as a distributed eventually consistent object storage, it is not mountable like a file server.
You can create the OpenStack API to generate credentials to access the SysEleven Stack Object Storage. You can then use the S3 API with various S3 clients and/or SDKs.
|request signature authentication||yes|
|predefined ACL groups||yes|
|bucket/IAM user ACP||no|
|regions and storage classes||no|
|website hosting configuration||no|
Setting bucket/object ACLs is only partially possible and currently unintuitive to use. We are in contact with the software manufacturer to solve this problem. For detailed information feel free to contact our Cloud Support.
Buckets are the logical unit SysEleven Stack Object Storage uses to stores objects.
Every bucket name is unique within a SysEleven Stack region.
Basically, SysEleven Stack Object Storage is a big key/value store.
A file or file object can be assigned a file name like key, and made available under this key.
The SEOS (SysEleven-Object-Storage / S3) is available in every region. The storage systems run independent from each other.
For historical reasons 's3.cloud.syseleven.net' redirects to 's3.cbk.cloud.syseleven.net'.
We recommend to always use a region specific URL like in the table above.
You need to meet the following prerequisites to generate credentials:
When these prerequisites are met, you can generate and display S3 credentials:
openstack ec2 credentials create openstack ec2 credentials list
Since the authentication service is centralised, the credentials created have access to SEOS/S3 in all regions.
Access to a specific region is gained by defining different storage backend URLs.
Information about the
s3cmd client can be found here.
Now you can create an
s3cmd configuration which could look like this:
syseleven@kickstart:~$ cat .s3cfg [default] access_key = < REPLACE ME > secret_key = < REPLACE ME > use_https = True check_ssl_certificate = True check_ssl_hostname = False host_base = s3.dbl.cloud.syseleven.net host_bucket = %(bucket).s3.dbl.cloud.syseleven.net
Next, create an S3 Bucket.
s3cmd mb s3://BUCKET_NAME -P
--acl-public makes this a public bucket which means that public objects in this bucket and a list of public objects can be retrieved. Without this option or with
--acl-private the public retrieval of objects and the list is not possible.
Then add some object(s):
s3cmd put test.jpg s3://BUCKET_NAME -P
Here we upload a file and make it public by specifying the option
--acl-public. Objects without this option or with
--acl-private are not publicly available and will not be contained in the listing.
Please note that
s3cmd may be configured to return incorrect URLs, i.e. by default:
Public URL of the object is: http://BUCKET_NAME.s3.amazonaws.com/test.jpg
The correct URL for this object in SysEleven Stack would be:
where REGION is the SysEleven Stack region (e.g. cbk or dbl).
You can use these URLs to refer to the uploaded files as static assets in your web applications.
Information about the Minio client can be found here.
Installation of Minio client into the home directory of the current user is necessary for the following example commands to work!
The Minio client is currently incapable of generating public files.
While synchronising many files Minio's performance is much better than with
Now you can create a Minio S3 configuration:
~/mc config host add <ALIAS> <YOUR-S3-ENDPOINT> <YOUR-ACCESS-KEY> <YOUR-SECRET-KEY> --api <API-SIGNATURE> --lookup <BUCKET-LOOKUP-TYPE> ~/mc config host add dbl https://s3.dbl.cloud.syseleven.net accesskey secretkey --api S3v4 --lookup dns ~/mc config host add cbk https://s3.cbk.cloud.syseleven.net accesskey secretkey --api S3v4 --lookup dns
Next, create an S3 Bucket:
~/mc mb dbl/bucketname Bucket created successfully ‘dbl/bucketname’.
Then, use it to add some file(s):
~/mc cp /root/test.jpg dbl/bucketname/test.jpg /root/test.jpg: 380.21 KB / 380.21 KB ┃▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓┃ 100.00% 65.42 MB/s 0s
List the file(s):
~/mc ls dbl/bucketname [2018-04-27 14:18:28 UTC] 380KiB test.jpg