Support IAM service accounts for S3 access
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
Sync-engine should not require AWS secrets to access resources. The code should be able to use the container's underlying service account/role to authenticate. This is often accomplished by simply passing in None for aws_access_key_id and aws_secret_access_key. The codebase might already support this use case but it should be confirmed everything works as expected if these two config variables aren't set.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AWS configuration variables and the S3 client or access entry point used by sync-engine. Verify behavior when the access key and secret are unset, confirm the container service account or role is used, and add or update coverage for that configuration so the IAM-based access path is demonstrably working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100