cc_staff
172
edits
No edit summary |
No edit summary |
||
Line 43: | Line 43: | ||
# if your data container policies are set to private (default), object storage is accessible via an [[Arbutus_object_storage_clients|S3-compatible client]] (e.g. s3cmd). Managing your object store such as setting policies cannot be done via web browser and must be done with an S3-compatible client | # if your data container policies are set to private (default), object storage is accessible via an [[Arbutus_object_storage_clients|S3-compatible client]] (e.g. s3cmd). Managing your object store such as setting policies cannot be done via web browser and must be done with an S3-compatible client | ||
# if your object storage policies are set to public (not default), object storage is accessible via an HTTPS endpoint: | # if your object storage policies are set to public (not default), object storage is accessible via an HTTPS endpoint: | ||
<!--T:21--> | |||
<code>https://object-arbutus.cloud.computecanada.ca:443/DATA_CONTAINER</code> | |||
= Managing your Arbutus object store = | = Managing your Arbutus object store = | ||
Line 61: | Line 64: | ||
* Data container names must be unique across '''all''' users in the Object Store, so you may benefit by prefixing data containers your project name to maintain uniqueness. In other words, don't bother trying to create a container named ''test'', but ''def-myname-test'' is probably OK. | * Data container names must be unique across '''all''' users in the Object Store, so you may benefit by prefixing data containers your project name to maintain uniqueness. In other words, don't bother trying to create a container named ''test'', but ''def-myname-test'' is probably OK. | ||
* Container policies are managed via json files. | * Container policies are managed via json files. | ||
== Managing data containers policies for your Arbutus Object Store == <!--T:31--> | == Managing data containers policies for your Arbutus Object Store == <!--T:31--> |