Switch from boto3 to async version (aioboto3)
Open
Nobody has claimed this yet.
module: services
type: improvement
- Dominant language
- Python
- Stars
- 29
- Forks
- 14
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 5
Description
Considering the backend is async, we should consider using https://pypi.org/project/aioboto3/ instead of boto3
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
Start by locating the backend's boto3 usage and reviewing how it is called from the async API. Compare those call sites with aioboto3's documented interface; done means the relevant AWS interactions use the async-compatible approach without breaking existing API behavior and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100