Skip to content

Commit 875f600

Browse files
authored
Merge pull request #91 from stanford-rc/wasabi
Removing Wasabi from Globus@Stanford site
2 parents 176c940 + 0b8858b commit 875f600

1 file changed

Lines changed: 5 additions & 31 deletions

File tree

cloud.md

Lines changed: 5 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ name for more information.
3131
| <a href="#microsoft-azure-blob-storage">Microsoft Azure Blob Storage</a> ||
3232
| <a href="#microsoft-onedrive">Microsoft OneDrive</a> ||
3333
| <a href="#oracle-cloud-infrastructure-oci-object-storage">Oracle Cloud (OCI) Object Storage</a> ||
34-
| <a href="#wasabi">Wasabi</a> ||
3534

3635
&nbsp;
3736

@@ -80,9 +79,11 @@ The Globus S3 connector supports more than just Amazon S3. If you run a
8079
storage platform that supports the S3 API, the Globus-for-S3 add-on may support
8180
it.
8281

83-
As of this page's last update, besides Amazon S3, we are aware of the Globus S3
84-
connector being used with Dell EMC ECS on-prem, and with Wasabi (as mentioned
85-
later on this page).
82+
See Globus' web site for the list of [supported S3-compatible storage
83+
systems](https://www.globus.org/connectors/connecting-s3-compatible-storage).
84+
85+
Besides Amazon S3, we are aware of the Globus S3 connector being used with Dell
86+
ObjectScale (formerly known as "ECS"), and with Wasabi.
8687

8788
If you would like to use the Globus S3 connector with your own storage
8889
platform, you may do so! You will need to set up a [Globus Connect Server v5
@@ -322,30 +323,3 @@ OCI. If you use OCI Object Storage, you may be able to [run your own Globus
322323
endpoint]({{ "server5.html" | relative_url }}) with the S3 connector,
323324
configured to talk to OCI Object Storage. [Contact
324325
us](mailto:srcc-support@stanford.edu) if you are interested in this.
325-
326-
# Wasabi
327-
328-
{% include info-box.html
329-
icon="wrench"
330-
raw=collection-under-construction
331-
%}
332-
333-
{% include info-box.html
334-
icon="biohazard"
335-
header="No High Risk Access allowed"
336-
content="Some Wasabi accounts are allowed to store High Risk data (including PHI). Such accounts are not allowed to use Globus."
337-
%}
338-
339-
Access to Wasabi is possible throguh region-specific collections:
340-
341-
* **us-west-1**: [SRCC Oak Wasabi S3](https://app.globus.org/file-manager/collections/0ffbca77-d3ca-463f-b564-690366dd2625/overview)
342-
343-
**You must use the collection specific to your Wasabi region.** Wasabi accounts
344-
created through Stanford University IT are placed into the us-west-1 region by
345-
default. If you need access to a different region, [let us
346-
know](mailto:srcc-support@stanford.edu).
347-
348-
349-
350-
351-

0 commit comments

Comments
 (0)