Skip to main content

capo-shield: typed, async Python SDK for AWS Shield

capo-shield is a typed Python SDK for AWS Shield. It has an async client, AsyncShieldClient, for asyncio and trio, and a sync client, ShieldClient, 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/shield/

Installation

pip install capo-shield

Usage

from capo_shield import AsyncShieldClient


async def main():
    async with AsyncShieldClient() as shield:
        # Example: call the associate_drt_log_bucket operation
        response = await shield.associate_drt_log_bucket()
        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_shield import AsyncShieldClient


async def main():
    async with AsyncShieldClient() as shield:
        # Example: paginate over list_attacks
        async for item in shield.iter_list_attacks():
            print(item)

Error Handling

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

from capo_shield import AsyncShieldClient
from capo_shield.error import AccessDeniedForDependencyException


async def main():
    async with AsyncShieldClient() as shield:
        try:
            await shield.associate_drt_log_bucket()
        except AccessDeniedForDependencyException 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_shield import AsyncShieldClient


async def main():
    async with AsyncShieldClient() as shield:
        # Default: 3 attempts for every operation
        response = await shield.associate_drt_log_bucket()

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

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

Metadata

Release files for capo-shield 0.9.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-shield 0.9.0
File Size Uploaded Provenance
capo_shield-0.9.0.tar.gz 124.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-shield 0.9.0
File Interpreter ABI Platform
capo_shield-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 391.2 kB

Release files / capo_shield-0.9.0.tar.gz

Download URL capo_shield-0.9.0.tar.gz
Size 124.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9038458b193e0019336693b77f2d50a2563e91a38f278763650087e9e95d7ba8
BLAKE2b-256 checksum
How to use checksums
49c685d79dc4a16cb7e7b55b5167bb5ace5c2010e91db156edeb0c7c5028f57a
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_shield-0.9.0-py3-none-any.whl

Download URL capo_shield-0.9.0-py3-none-any.whl
Size 267.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
32a8f2edc447c6975bfaf4e22fd3da8fb11631142c352e2ead478ea64d7264eb
BLAKE2b-256 checksum
How to use checksums
5f34d4bdaf3fbde57515bb275d090b565649f982e87d97717332af18e204dd0e
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-shield 0.9.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