sameersbn / sameersbn/docker-gitlab
using IAM profile for AWS backups
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
when AWS_BACKUP_USE_IAM_PROFILE: true set in the environment to use IAM profile for AWS backups, the code still using AWS_BACKUP_ACCESS_KEY_ID & AWS_BACKUP_SECRET_ACCESS_KEY to upload to S3. Also, AWS_BACKUP_ACCESS_KEY_ID &AWS_BACKUP_SECRET_ACCESS_KEY can not be set to empty or not being set in the enviroment.
Contributor guide
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
No file or test is identified in the issue; start by locating the AWS backup upload path and its handling of AWS_BACKUP_USE_IAM_PROFILE, AWS_BACKUP_ACCESS_KEY_ID, and AWS_BACKUP_SECRET_ACCESS_KEY. Done means IAM-profile uploads reach S3 without requiring the key variables, while explicit credentials continue to work, with coverage for both configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100