Arbutus object storage clients: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Inital version)
 
No edit summary
Line 13: Line 13:
Depending on your Linux distribution, the <code>s3cmd</code> command can be installed using the appropriate yum or apt command:
Depending on your Linux distribution, the <code>s3cmd</code> command can be installed using the appropriate yum or apt command:


<code>$ sudo yum install s3cmd</code>
<code>$ sudo yum install s3cmd</code><br/>
<code>$ sudo apt-get install s3cmd </code>
<code>$ sudo apt-get install s3cmd </code>


Line 20: Line 20:


And make the following configurations:
And make the following configurations:
{
<code>
Enter new values or accept defaults in brackets with Enter.
Enter new values or accept defaults in brackets with Enter.
Refer to user manual for detailed description of all options.
Refer to user manual for detailed description of all options.
Line 49: Line 49:
Try setting it here if you can't connect to S3 directly
Try setting it here if you can't connect to S3 directly
HTTP Proxy server name:
HTTP Proxy server name:
}
</code>


The next task is to make a bucket.  Buckets contain files. Bucket names must be globally unique across the Arbutus object storage solution.  Therefore, you will need to create a uniquely named bucket which will not conflict with other users.  For example, the buckets "s3://test/" and "s3://data" are likely already taken.  Consider creating buckets reflective of your project, for example "s3://def-test-bucket1" or "s3://atlas_project_bucket".  Bucket names can only use the characters A-Z, a-z, 0-9, ., - and _.
The next task is to make a bucket.  Buckets contain files. Bucket names must be globally unique across the Arbutus object storage solution.  Therefore, you will need to create a uniquely named bucket which will not conflict with other users.  For example, the buckets "s3://test/" and "s3://data" are likely already taken.  Consider creating buckets reflective of your project, for example "s3://def-test-bucket1" or "s3://atlas_project_bucket".  Bucket names can only use the characters A-Z, a-z, 0-9, ., - and _.
Line 69: Line 69:
<code>$ s3cmd setacl --acl-public s3://BUCKET_NAME</code>
<code>$ s3cmd setacl --acl-public s3://BUCKET_NAME</code>


The result of this command is that anyone can access the bucket and the files in the bucket.  Files can be accessed via URLs such as https://object-arbutus.cloud.computecanada.ca/BUCKET_NAME/FILE_NAME.
The result of this command is that anyone can access the bucket and the files in the bucket.  Files can be accessed via URLs such as https://object-arbutus.cloud.computecanada.ca/BUCKET_NAME/FILE_NAME.dat.


The second ACL example limits access to the bucket by the owner:
The second ACL example limits access to the bucket by the owner:
cc_staff
172

edits

Navigation menu