Skip to main content

Getting Started

Installation

pip install capo-bedrock-data-automation

Usage

from capo_bedrock_data_automation import AsyncBedrockDataAutomationClient


async def main():
    async with AsyncBedrockDataAutomationClient() as bedrock_data_automation:
        # Example: call the copy_blueprint_stage operation
        response = await bedrock_data_automation.copy_blueprint_stage()
        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_bedrock_data_automation import AsyncBedrockDataAutomationClient


async def main():
    async with AsyncBedrockDataAutomationClient() as bedrock_data_automation:
        # Example: paginate over list_data_automation_library_entities
        async for item in bedrock_data_automation.iter_list_data_automation_library_entities():
            print(item)

Error Handling

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

from capo_bedrock_data_automation import AsyncBedrockDataAutomationClient
from capo_bedrock_data_automation.error import AccessDeniedException


async def main():
    async with AsyncBedrockDataAutomationClient() as bedrock_data_automation:
        try:
            await bedrock_data_automation.copy_blueprint_stage()
        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_bedrock_data_automation import AsyncBedrockDataAutomationClient


async def main():
    async with AsyncBedrockDataAutomationClient() as bedrock_data_automation:
        # Default: 3 attempts for every operation
        response = await bedrock_data_automation.copy_blueprint_stage()

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

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

Metadata

Release files for capo-bedrock-data-automation 0.7.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-bedrock-data-automation 0.7.0
File Size Uploaded Provenance
capo_bedrock_data_automation-0.7.0.tar.gz 116.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-bedrock-data-automation 0.7.0
File Interpreter ABI Platform
capo_bedrock_data_automation-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 400.9 kB

Release files / capo_bedrock_data_automation-0.7.0.tar.gz

Download URL capo_bedrock_data_automation-0.7.0.tar.gz
Size 116.1 kB
Tags Source
SHA-256 checksum
How to use checksums
221759dcd51a444c5e5097f5d556b73ffb81673e2b9d2648d07cd5f81776e9b3
BLAKE2b-256 checksum
How to use checksums
c88676a02e805a93340a869bf2288ebac266cd4358789ba3cd2c80a27d35473a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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_bedrock_data_automation-0.7.0-py3-none-any.whl

Download URL capo_bedrock_data_automation-0.7.0-py3-none-any.whl
Size 284.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
622d214438b853db596d0ce08ad0859bab35df637d04c01794b74b9caeebcd77
BLAKE2b-256 checksum
How to use checksums
8acbc1b25415904bf52d507f4d9588bf7cfeb5d6e34f0f412fbc823a4772d120
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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-bedrock-data-automation 0.7.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