ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Migrate from long-term AWS access keys to IAM Role with STS
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Currently, we are using long-term AWS Secret Access Keys to access our storage path. This approach is less secure and not aligned with AWS best practices.
We need to migrate to using IAM Roles and fetch temporary credentials via AWS STS (Security Token Service). This will ensure better security, automatic credential rotation, and compliance with AWS standards.
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
The issue names no files, tests, or entry points. Start by locating the current storage access and AWS credential configuration, then determine how temporary STS credentials and the IAM role should be integrated; done means long-term access keys are no longer used and storage access remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100