Skip to main content

capo-auto-scaling: typed, async Python SDK for AWS Auto Scaling

capo-auto-scaling is a typed Python SDK for AWS Auto Scaling. It has an async client, AsyncAutoScalingClient, for asyncio and trio, and a sync client, AutoScalingClient, 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/auto-scaling/

Installation

pip install capo-auto-scaling

Usage

from capo_auto_scaling import AsyncAutoScalingClient


async def main():
    async with AsyncAutoScalingClient() as auto_scaling:
        # Example: call the attach_instances operation
        response = await auto_scaling.attach_instances()
        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_auto_scaling import AsyncAutoScalingClient


async def main():
    async with AsyncAutoScalingClient() as auto_scaling:
        # Example: paginate over describe_auto_scaling_groups
        async for item in auto_scaling.iter_describe_auto_scaling_groups():
            print(item)

Error Handling

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

from capo_auto_scaling import AsyncAutoScalingClient
from capo_auto_scaling.error import ResourceContentionFault


async def main():
    async with AsyncAutoScalingClient() as auto_scaling:
        try:
            await auto_scaling.attach_instances()
        except ResourceContentionFault 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_auto_scaling import AsyncAutoScalingClient


async def main():
    async with AsyncAutoScalingClient() as auto_scaling:
        # Default: 3 attempts for every operation
        response = await auto_scaling.attach_instances()

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

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

Metadata

Release files for capo-auto-scaling 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-auto-scaling 0.11.0
File Size Uploaded Provenance
capo_auto_scaling-0.11.0.tar.gz 293.9 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 931.2 kB

Release files / capo_auto_scaling-0.11.0.tar.gz

Download URL capo_auto_scaling-0.11.0.tar.gz
Size 293.9 kB
Tags Source
SHA-256 checksum
How to use checksums
223b41a3d974a9b89ad979b970bd166a81c9974ac5811d4b0eb7817ac5a54384
BLAKE2b-256 checksum
How to use checksums
8ce8fa6daaadd2e1c5370b442d5ee31af03d4b22b2031cabbe4400c7a320769a
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_auto_scaling-0.11.0-py3-none-any.whl

Download URL capo_auto_scaling-0.11.0-py3-none-any.whl
Size 637.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ed1e9f420f9f975b87e8a361d67c118e8ea7e21c3b9fa4cb6e4882332e57ba9c
BLAKE2b-256 checksum
How to use checksums
cc0bb069fe5fe3bb54c9030ac8fb7d951273a3296f71fe6ce2abf9419e7ddedc
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-auto-scaling 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