Skip to main content

capo-acm: typed, async Python SDK for AWS ACM

capo-acm is a typed Python SDK for AWS ACM. It has an async client, AsyncACMClient, for asyncio and trio, and a sync client, ACMClient, 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/acm/

Installation

pip install capo-acm

Usage

from capo_acm import AsyncACMClient


async def main():
    async with AsyncACMClient() as acm:
        # Example: call the add_tags_to_certificate operation
        response = await acm.add_tags_to_certificate()
        print(response)

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_acm import AsyncACMClient


async def main():
    async with AsyncACMClient() as acm:
        # Example: paginate over list_acme_accounts
        async for item in acm.iter_list_acme_accounts():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_acm import AsyncACMClient
from capo_acm.error import InvalidArnException


async def main():
    async with AsyncACMClient() as acm:
        try:
            await acm.add_tags_to_certificate()
        except InvalidArnException 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.

from capo_acm import AsyncACMClient


async def main():
    async with AsyncACMClient() as acm:
        # Default: 3 attempts for every operation
        response = await acm.add_tags_to_certificate()

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

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

Metadata

Release files for capo-acm 0.11.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-acm 0.11.0
File Size Uploaded Provenance
capo_acm-0.11.0.tar.gz 156.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-acm 0.11.0
File Interpreter ABI Platform
capo_acm-0.11.0-py3-none-any.whl Python 3 none any Details

Total release size: 492.0 kB

Release files / capo_acm-0.11.0.tar.gz

Download URL capo_acm-0.11.0.tar.gz
Size 156.9 kB
Tags Source
SHA-256 checksum
How to use checksums
64c399d0ea0dd9a678a979b8390b27404440bbe2014fc1d8a2167a03797495e1
BLAKE2b-256 checksum
How to use checksums
a605c3118121fdc1830413afaa8c2e1dfb929c1fb7f27e2213d6335695f56406
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_acm-0.11.0-py3-none-any.whl

Download URL capo_acm-0.11.0-py3-none-any.whl
Size 335.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f26eb04ac88aaec70d0c03756d8c586d3b2c7f295cfc4a84fe025aa7fa1188f0
BLAKE2b-256 checksum
How to use checksums
f1a6c400ec7d420424660397042f9edb09fa2f34a2981be74ccc7074e68a80a8
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-acm 0.11.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.

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