broker/fragment: region support for s3 stores #365
Merged
Conversation
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
Previously s3 stores could only use the region available via a given profile or the AWS application default credentials. This adds the ability to set an alternate region in the endpoint URL for an s3 fragment store for buckets that are in a different region.
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 11, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
williamhbaker
added a commit
to estuary/flow
that referenced
this pull request
Mar 14, 2024
Allows setting the region for S3 storage mappings, for buckets that are not in the us-east-1 region. See also: gazette/core#365
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously s3 stores could only use the region available via a given profile or the AWS application default credentials. This adds the ability to set an alternate region in the endpoint URL for an s3 fragment store for buckets that are in a different region.
This change is