Allow S3-Compatible Cloud Object Storage in CloudETL Example #1264
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.
Description
This change allows the use of an S3-compatible cloud object store such as Backblaze B2 with the CloudETL example as an alternative to Amazon S3.
With this change, the user may configure an AWS profile with
endpoint_url
set to a value such ashttps://s3.us-west-004.backblazeb2.com
in theconfig
file. For example:The
setup_s3_storage.sh
script reads this value (viaaws configure get endpoint_url --profile $S3_PROFILE
) into a newS3_ENDPOINT_URL
environment variable which is used asstore.url
for the connectors. If the endpoint URL is not set in the profile, then the Amazon S3 global default,https://s3.amazonaws.com
, is used.There is also a fix to
read-data.sh
- thelist-objects
call was missing the--profile $S3_PROFILE
, so it incorrectly used the default profile.Author Validation
[x] cloud-etl
Reviewer Tasks
Describe the tasks/validation that the PR submitter is requesting to be done by the reviewer.
[ ] cloud-etl