Repository navigation
fix(s3): resolve region without IMDS probe when endpoint/region known - #24
Merged
Merged
Conversation
Cold S3 config load dropped ~3000ms -> ~5ms off-EC2: the default region provider probed EC2 IMDS when no region was set. Resolve region from override/env/profile first and load with a concrete region; only a genuine real-AWS target (no endpoint, no region) consults the IMDS region provider.
hoshimura
added this pull request to stack #26
October 6, 2026 07:23
hannabjorgvins
approved these changes
Oct 7, 2026
hannabjorgvins
left a comment
hannabjorgvins
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me
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.
Cold S3 config load dropped ~3000ms -> ~5ms off-EC2: the default region provider probed EC2 IMDS when no region was set. Resolve region from override/env/profile first and load with a concrete region; only a genuine real-AWS target (no endpoint, no region) consults the IMDS region provider.