aiobotocore provides asyncio support for the botocore AWS SDK, using aiohttp to make botocore-style clients work in async Python. It is useful if you want to call Amazon services such as S3 asynchronously, including examples for streaming responses, paginators, and async context manager usage.
Project status
- Actively maintained, with ongoing updates through May 2026 (latest upstream push 2026-05-15) and a sequence of versioned updates in 2026 (3.1.1 to 3.7.0), indicating active development rather than maintenance mode.
- Apparent update cadence is roughly every 2 to 3 weeks in early 2026, slowing slightly to about weekly in May (2026-04-21, 2026-05-01, 2026-05-09).
AI summary generated 2026-05-18
Recent updates
3.7.0
2026-05-09Release 3.7.0 adds a new AioSession cache pre-warming API, fixes an async race that could trigger InfiniteLoopConfigError, and improves credential_process behavior on Windows event loops by falling back to synchronous subprocess execution. It also introduces an AI-driven release flow where contributors no longer edit version or changelog files directly at PR time.
Features3.6.0
2026-05-01Release 3.6.0 primarily relaxes the `botocore` dependency upper bound (documented in the release notes). The code diff also shows broader project maintenance changes, including dropping Python 3.9 support and several CI/bot workflow updates.
Breaking3.5.0
2026-04-21Release 3.5.0 is largely focused on internal CI and Claude bot workflow automation for botocore synchronization, including prompt/template changes and dependency spec adjustments. The only explicitly user-facing change called out in release notes is the botocore dependency specification relaxation and related botocore spec bump, while the rest is workflow and tooling updates.
Breaking3.4.0
2026-04-07Release 3.4.0 primarily updates automation around syncing aiobotocore with newer botocore versions, along with various CI workflow and prompt refinements. The release notes also include a botocore dependency specification bump and several GitHub Actions dependency/version updates.
SecurityFeatures3.3.0
2026-03-18Release 3.3.0 primarily updates the declared botocore dependency range to allow newer botocore versions. It also includes CI and tooling bumps, plus a small internal documentation update to reflect the default branch name change from master to main.
3.2.1
2026-03-04Release 3.2.1 primarily relaxes the declared botocore version constraints to allow newer botocore releases, and it includes an internal dependency bump for joserfc. The code changes are limited to metadata and dependency specifications, with the lockfile updated accordingly.
3.2.0
2026-02-24Release 3.2.0 mainly updates the declared botocore dependency range and the CI tooling that installs dependencies via uv. It also removes the stale GitHub workflow used for auto-closing inactive issues and PRs.
3.1.3
2026-02-14Release 3.1.3 primarily relaxes the supported `botocore` version upper bound, allowing `botocore` versions up to `< 1.42.50` instead of `< 1.42.43`. The diff also includes build and development tooling updates (pre-commit, lockfile, dev deps) and updates test fixtures.
3.1.2
2026-02-05Release 3.1.2 primarily relaxes the allowed version range for the botocore dependency, and regenerates the uv lockfile. It also updates CI and developer tooling versions (actions/checkout and pre-commit/uv-pre-commit revs), which affects the build/test environment but not the runtime library API.
3.1.1
2026-01-20Release 3.1.1 primarily relaxes the allowed version range for the botocore dependency. In addition, it updates several development and CI tooling dependencies (setup-uv, GitHub Actions, pre-commit hooks, and documentation tooling).