Python developers struggle to type-check boto3 code
Boto3’s dynamic clients, resources, and responses make it hard for Python developers to get reliable type checking and IDE support. The requesters describe missing or incomplete type definitions, with one hand-writing a stub from AWS documentation and another considering a wrapper they expected would be too large to build. These signals are several years old, so the size of the unmet need should be validated against today’s generated-stub options.
For python developers using boto3. Mentioned from Apr 2017 to Jun 2025 on GitHub and Hacker News.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Having fleshed-out type definitions for the objects that boto3 generates at runtime would make writing bug-free code against boto3 a lot easier
Even if you don't want to do a wholesale refactoring, just providing a set of types for responses would be super helpful. (I'm assuming there's some of specification that is generating the resources and clients). As an example, I made a type stub for the S3PutEvent (based on AWS docs)
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks