Skip to main content

Getting Started

Installation

pip install capo-acm-pca

Usage

from capo_acm_pca import AsyncACMPCAClient


async def main():
    async with AsyncACMPCAClient() as acmpca:
        # Example: call the create_certificate_authority operation
        response = await acmpca.create_certificate_authority()
        print(response["certificate_authority_arn"])

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_pca import AsyncACMPCAClient


async def main():
    async with AsyncACMPCAClient() as acmpca:
        # Example: paginate over list_certificate_authorities
        async for item in acmpca.iter_list_certificate_authorities():
            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_acm_pca import AsyncACMPCAClient


async def main():
    async with AsyncACMPCAClient() as acmpca:
        # Example: wait for certificate_issued
        await acmpca.wait_until_certificate_issued(max_wait_time=300)

Error Handling

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

from capo_acm_pca import AsyncACMPCAClient
from capo_acm_pca.error import InvalidArgsException


async def main():
    async with AsyncACMPCAClient() as acmpca:
        try:
            await acmpca.create_certificate_authority()
        except InvalidArgsException 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_pca import AsyncACMPCAClient


async def main():
    async with AsyncACMPCAClient() as acmpca:
        # Default: 3 attempts for every operation
        response = await acmpca.create_certificate_authority()

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

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

Metadata

Release files for capo-acm-pca 0.10.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-pca 0.10.0
File Size Uploaded Provenance
capo_acm_pca-0.10.0.tar.gz 130.7 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 369.8 kB

Release files / capo_acm_pca-0.10.0.tar.gz

Download URL capo_acm_pca-0.10.0.tar.gz
Size 130.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cd1d983ff869d666deda11943ad41cc5ce7c8424368b380696f1f98e1720f723
BLAKE2b-256 checksum
How to use checksums
b3cef63291bc69058642f9c2f59d62ca59b16183bf49a145a1b3b367514e80d3
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_pca-0.10.0-py3-none-any.whl

Download URL capo_acm_pca-0.10.0-py3-none-any.whl
Size 239.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b1f912bd6f720c09d9ce183cfca41b81a33f1ec78294f200bc6274211ce8aea9
BLAKE2b-256 checksum
How to use checksums
1c92f0eda739bf2d84f5e0b7e5c937aeb8c58e2c1b866b430f5d60f4e7defe59
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-pca 0.10.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