Skip to main content

capo-ec2: typed, async Python SDK for Amazon EC2

capo-ec2 is a typed Python SDK for Amazon EC2. It has an async client, AsyncEC2Client, for asyncio and trio, and a sync client, EC2Client, 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/ec2/

Installation

pip install capo-ec2

Usage

from capo_ec2 import AsyncEC2Client


async def main():
    async with AsyncEC2Client() as ec2:
        # Example: call the accept_address_transfer operation
        response = await ec2.accept_address_transfer()
        print(response["address_transfer"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_ec2 import AsyncEC2Client


async def main():
    async with AsyncEC2Client() as ec2:
        # Example: paginate over describe_addresses_attribute
        async for item in ec2.iter_describe_addresses_attribute():
            print(item)

Waiters

Waiters poll an operation until a resource reaches a desired state. If the operation supports waiters it will have a wait_until_ prefixed method.

from capo_ec2 import AsyncEC2Client


async def main():
    async with AsyncEC2Client() as ec2:
        # Example: wait for vpc_peering_connection_exists
        await ec2.wait_until_vpc_peering_connection_exists(max_wait_time=300)

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.

from capo_ec2 import AsyncEC2Client


async def main():
    async with AsyncEC2Client() as ec2:
        # Default: 3 attempts for every operation
        response = await ec2.accept_address_transfer()

        # Override per operation
        response = await ec2.accept_address_transfer(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await ec2.accept_address_transfer(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-ec2 0.26.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-ec2 0.26.0
File Size Uploaded Provenance Actions
capo_ec2-0.26.0.tar.gz 2.2 MB Without provenance Details for capo_ec2-0.26.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for capo-ec2 0.26.0
File Interpreter ABI Platform Actions
capo_ec2-0.26.0-py3-none-any.whl Python 3 none any Details for capo_ec2-0.26.0-py3-none-any.whl

Total release size: 8.4 MB

Release files / capo_ec2-0.26.0.tar.gz

Download URL capo_ec2-0.26.0.tar.gz
Size 2.2 MB
Tags Source
SHA-256 checksum
How to use checksums
726e1c49380fc47e52c69b06200b40f6ab9bad754c43456708fc37eb90264733
BLAKE2b-256 checksum
How to use checksums
e8f84b6f22a8972b00fca732719298ccd3330cb1eb154545530c176034304eb0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_ec2-0.26.0-py3-none-any.whl

Download URL capo_ec2-0.26.0-py3-none-any.whl
Size 6.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
44c9759c2629ca5eea028a1ce7cfe122094dee25716300b196bb46367a964f34
BLAKE2b-256 checksum
How to use checksums
5e44e16b3950c94039eb734dd37ed2c97581249afe72aef338c8e05ececce983
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-ec2 0.26.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page