capo-route53-recovery-cluster: typed, async Python SDK for AWS Route53 Recovery Cluster¶
capo-route53-recovery-cluster is a typed Python SDK for AWS Route53 Recovery Cluster. It has an async client, AsyncRoute53RecoveryClusterClient, for asyncio and trio, and a sync client, Route53RecoveryClusterClient, 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/route53-recovery-cluster/
Installation¶
Usage¶
from capo_route53_recovery_cluster import AsyncRoute53RecoveryClusterClient
async def main():
async with AsyncRoute53RecoveryClusterClient() as route53_recovery_cluster:
# Example: call the get_routing_control_state operation
response = await route53_recovery_cluster.get_routing_control_state()
print(response["routing_control_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_route53_recovery_cluster import AsyncRoute53RecoveryClusterClient
async def main():
async with AsyncRoute53RecoveryClusterClient() as route53_recovery_cluster:
# Example: paginate over list_routing_controls
async for item in route53_recovery_cluster.iter_list_routing_controls():
print(item)
Error Handling¶
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_route53_recovery_cluster import AsyncRoute53RecoveryClusterClient
from capo_route53_recovery_cluster.error import AccessDeniedException
async def main():
async with AsyncRoute53RecoveryClusterClient() as route53_recovery_cluster:
try:
await route53_recovery_cluster.get_routing_control_state()
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_route53_recovery_cluster import AsyncRoute53RecoveryClusterClient
async def main():
async with AsyncRoute53RecoveryClusterClient() as route53_recovery_cluster:
# Default: 3 attempts for every operation
response = await route53_recovery_cluster.get_routing_control_state()
# Override per operation
response = await route53_recovery_cluster.get_routing_control_state(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await route53_recovery_cluster.get_routing_control_state(config_overrides={"retry_max_attempts": 1})