Fix S3 storage to honor region configuration #110
Merged
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.
The S3 storage module was not passing the region_name parameter to the boto3 client, causing AWS to default to us-east-1. When buckets were in different regions, this caused AuthorizationHeaderMalformed errors.
Changes:
Fixes region error reported by @mikeonslow
🤖 Generated with Claude Code
Note
S3 storage now passes aws_region and supports endpoint_url, with updated config/docs and a comprehensive test suite.
_create_s3_clientto passaws_regionand optionalendpoint_urltoboto3.client.save/getinserver/storage/s3/__init__.pyto use_create_s3_client; support optionals3_pathand date-based keys.example_config.ymlS3 options: addaws_region; document optionalendpoint_url,s3_path.server/storage/s3/README.mdwith accurate options, region guidance, features, key structure, and best practices.tests/storage/test_s3.pycovering client creation (regions/endpoints), save/get behavior, key prefixes, and error handling.tests/storage/__init__.py.Written by Cursor Bugbot for commit 3dcbf18. Configure here.