docs: clarify that uploads go through the S3-compatible data proxy - #35
Merged
Merged
Conversation
The upload guide read as if data lived in AWS. Explain that the data proxy speaks the S3 API and may be backed by any object store, that AWS tools are only S3 clients, and that credentials come from Source. Fix stale s3://us-west-2.opendata.source.coop addresses in Option 2 and call out that Option 3 is the one path that is genuinely AWS. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tylere
approved these changes
Sep 24, 2026
tylere
left a comment
tylere
left a comment
Contributor
There was a problem hiding this comment.
Overall this is much clearer.
I left a few minor comments.
| @@ -408,7 +465,7 @@ This protects both you and Source Cooperative. | |||
|
|
|||
| Please do not: | |||
Contributor
There was a problem hiding this comment.
If a user tries any of these actions they will fail, correct?
Contributor
Author
There was a problem hiding this comment.
For the actions that aren't human behavior, yes, they will be denied.
Clarified the S3 bucket examples for data upload.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
alukach
commented
Sep 25, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the discussion in source-cooperative/source-coop-cli#16. The upload guide mentions AWS dozens of times and never says the backing store may be something other than AWS, so it reads as if uploading requires AWS.
Changes to
/data-uploaddata.source.coopspeaks the S3 API but is not an AWS service.s3://your-org/your-product/is a proxy address, not an S3 bucket.endpoint_urldoes, addsAWS_ENDPOINT_URLand a boto3endpoint_urlexample for credentials copied from the UI, and notes that the region value does not show where the data is stored.s3://us-west-2.opendata.source.coop/...addresses in "Where to upload" and the AWS CLI example (missed in f614344). They now uses3://your-org/your-product/with--endpoint-url.docusaurus buildpasses with no broken links or anchors.🤖 Generated with Claude Code