Skip to main content

Getting Started

Installation

pip install capo-route53resolver

Usage

from capo_route53resolver import AsyncRoute53ResolverClient


async def main():
    async with AsyncRoute53ResolverClient() as route53_resolver:
        # Example: call the associate_firewall_rule_group operation
        response = await route53_resolver.associate_firewall_rule_group()
        print(response["firewall_rule_group_association"])

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_route53resolver import AsyncRoute53ResolverClient


async def main():
    async with AsyncRoute53ResolverClient() as route53_resolver:
        # Example: paginate over list_firewall_configs
        async for item in route53_resolver.iter_list_firewall_configs():
            print(item)

Error Handling

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

from capo_route53resolver import AsyncRoute53ResolverClient
from capo_route53resolver.error import AccessDeniedException


async def main():
    async with AsyncRoute53ResolverClient() as route53_resolver:
        try:
            await route53_resolver.associate_firewall_rule_group()
        except AccessDeniedException 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_route53resolver import AsyncRoute53ResolverClient


async def main():
    async with AsyncRoute53ResolverClient() as route53_resolver:
        # Default: 3 attempts for every operation
        response = await route53_resolver.associate_firewall_rule_group()

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

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

Metadata

Release files for capo-route53resolver 0.1.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-route53resolver 0.1.0
File Size Uploaded Provenance
capo_route53resolver-0.1.0.tar.gz 195.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-route53resolver 0.1.0
File Interpreter ABI Platform
capo_route53resolver-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 697.4 kB

Release files / capo_route53resolver-0.1.0.tar.gz

Download URL capo_route53resolver-0.1.0.tar.gz
Size 195.0 kB
Tags Source
SHA-256 checksum
How to use checksums
a737f92387e0312bf2eea10b5064deeb4926bf26a68510b6871f98ac931550be
BLAKE2b-256 checksum
How to use checksums
51b4ad3851836b4d0c1912b53838e93faf8fc783d3bb7c1a782f343d792998b8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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_route53resolver-0.1.0-py3-none-any.whl

Download URL capo_route53resolver-0.1.0-py3-none-any.whl
Size 502.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
818a21f9b39e1169f50bbfd6145749ce9f1a751abe84430903aeca574ff7ea87
BLAKE2b-256 checksum
How to use checksums
714ca11db0f9f462d509e70aaa3c63dba0a1cc9c8e689bbd5bef30a602942ff7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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-route53resolver 0.1.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