Repository navigation
Use EC2 instance role instead of AWS keys - #55
Merged
Merged
Conversation
- Updated .example.env to configure S3 mock settings and added access key details. - Modified .example.env.json to include bucket block list and IAM role usage flag. - Enhanced BlobHandler to manage blocked buckets and improve AWS credential handling. - Adjusted bucket listing logic to respect blocked buckets. - Updated docker-compose.yml to streamline S3 mock service configuration.
…ting related comments
Akopti8
marked this pull request as ready for review
October 13, 2026 18:30
Akopti8
changed the title
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
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.
Summary
.env.jsoncan use the EC2 instance role instead of static keys: set"use_iam_role": true(or leaveaccountsempty). In IAM mode credentials come only from instance metadata; static keys andAWS_*env vars are ignored.bucket_block_list: blocked buckets are never exposed, even with"*"in the allow list.s3:ListAllMyBuckets.s3mockcompose profile.docker composev2, s3mock profile).Testing
ffrd-pilot(cross-account).