capo-sts: typed, async Python SDK for AWS STS
capo-sts is a typed Python SDK for AWS STS. It has an async client, AsyncSTSClient, for asyncio and trio, and a sync client, STSClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.
It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/sts/
Installation
pip install capo-sts
Usage
from capo_sts import AsyncSTSClient
async def main():
async with AsyncSTSClient() as sts:
# Example: call the assume_role operation
response = await sts.assume_role()
print(response["credentials"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_sts import AsyncSTSClient
from capo_sts.error import ExpiredTokenException
async def main():
async with AsyncSTSClient() as sts:
try:
await sts.assume_role()
except ExpiredTokenException as e:
print(f"Error: {e}")
print(e.data) # additional error data
Retrying
The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.
The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.
retry_mode="adaptive" (or AWS_RETRY_MODE=adaptive, or retry_mode = adaptive in the AWS profile) also slows the whole client down once the service starts throttling it, then speeds back up as requests succeed. The default is standard.
from capo_sts import AsyncSTSClient
async def main():
async with AsyncSTSClient() as sts:
# Default: 3 attempts for every operation
response = await sts.assume_role()
# Override per operation
response = await sts.assume_role(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await sts.assume_role(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-sts 0.23.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| capo_sts-0.23.0.tar.gz | 132.9 kB | Without provenance | Details for capo_sts-0.23.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| capo_sts-0.23.0-py3-none-any.whl | Python 3 | none | any | Details for capo_sts-0.23.0-py3-none-any.whl |
Total release size: 329.3 kB
Release files / capo_sts-0.23.0.tar.gz
| Download URL | capo_sts-0.23.0.tar.gz |
|---|---|
| Size | 132.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73c1665d146ba2a2eafe5d0d024cc8e92dfcd20c443e71fd5b5cdd4902862ed3
|
|
BLAKE2b-256 checksum How to use checksums |
7f9e5fb2ee342269e19fffc47978b43a8f8ab976d10e515b2da1fe9ccf86cfed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / capo_sts-0.23.0-py3-none-any.whl
| Download URL | capo_sts-0.23.0-py3-none-any.whl |
|---|---|
| Size | 196.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3438884ab7e7478a760d09cf466ca20404ce6ff3c4ebbeb8b105670052b2ec6e
|
|
BLAKE2b-256 checksum How to use checksums |
ec4afc1154ecd30f4dfb8a96478828f284efb9db8c3ce737556a16c719ce48d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for capo-sts 0.23.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.