Conversation
When S3 Collections were first hosted centrally, there were separate Collections for different Amazon S3 regions. That was changed in September 2024. Since it's been over 18 months from the deprecation, I think it's OK to remove the notice.
Globus-wise, SCG first became available to use through SCG. Why? Because the GBSC (SCG's owner) paid for the additional Globus subscription cost. Folks should not be using that anymore, so it's good to post a proper deprecration notice, before eventually deleting the Collection.
Updates the S3 page to call out that the Globus Collection cannot access buckets in GovCloud or China. The cloud main page already mentions no access to China, but the mention was buried in text. This makes the callout clearer, and adds GovCloud to the callout.
Many of the screenshots were still referencing the SCG-based S3 Collection. This commit updates the screenshots to reflect the correct Collection.
The S3 Collections now support multiple keys: A default key, along with zero or more bucket-specific keys. This commit updates the text accordingly.
Since we no longer have an agreement with Wasabi, it no longer makes sense to mention it here. (BTW, Stanford does still have an agreement with Box, due to Medicine Box. That's why I'm keeping it mentioned here.)
Just in case we end up supporting Backblaze B2.
This also triggers a number of dependency updates in the Gemfile.lock.
|
Static-site build available! The static site build for branch The build was completed on 2026-07-02_15-00-40; it will be deleted after seven days. NOTE: We cannot guarantee the build will look exactly like the site. Always look at the actual commit, not just this build! |
Since this section was written, the process for IAM User creation has changed a little: AWS now uses "IAM User" instead of just "User", and the process for creating an Access Key has been separated from the process of creating an IAM User.
|
Static-site build available! The static site build for branch The build was completed on 2026-07-02_16-37-57; it will be deleted after seven days. NOTE: We cannot guarantee the build will look exactly like the site. Always look at the actual commit, not just this build! |
|
Since I was in the general area of the S3 docs, I noticed that the IAM User-creation steps needed to be updated. So, I've added a commit to the PR, covering that update. |
2 participants
On the S3 page, I update the screenshots to remove references to the old SCG-hosted S3 Collection, since that Collection is being deprecated. I also add a depreciation notice at the top of the page.
The S3 Collection now supports multiple Access Keys: Users can provide a default Key, as well as Keys to be used for specific S3 Buckets.
I also add a note that the S3 Collection cannot access S3 buckets that are hosted in GovCloud.
Policy-wise, I remove a reference to the Wasabi ToS, and add a reference to the Backblaze ToS.
In the Gemfile, I update the dependency on the github-pages Gem, and update the versions in the Gemfile.lock.