Skip to main content

Getting Started

Installation

pip install capo-bedrock-runtime

Usage

from capo_bedrock_runtime import AsyncBedrockRuntimeClient


async def main():
    async with AsyncBedrockRuntimeClient() as bedrock_runtime:
        # Example: call the get_async_invoke operation
        response = await bedrock_runtime.get_async_invoke()
        print(response["invocation_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_bedrock_runtime import AsyncBedrockRuntimeClient


async def main():
    async with AsyncBedrockRuntimeClient() as bedrock_runtime:
        # Example: paginate over list_async_invokes
        async for item in bedrock_runtime.iter_list_async_invokes():
            print(item)

Streaming Request

Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.

A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.

from capo_bedrock_runtime import AsyncBedrockRuntimeClient, Body


async def main():
    async with AsyncBedrockRuntimeClient() as bedrock_runtime:
        # Example: call invoke_model_with_bidirectional_stream with a streaming request body
        async def chunks():
            yield b'Hello, World!'

        response = await bedrock_runtime.invoke_model_with_bidirectional_stream(body=chunks())
        print(response)

        # Or pass the whole body as bytes
        response = await bedrock_runtime.invoke_model_with_bidirectional_stream(body=b'Hello, World!')
        print(response)

        # Or stream a file with Body: the file is reopened on every retry
        # and Content-Length is taken from its size, so no content_length needed
        response = await bedrock_runtime.invoke_model_with_bidirectional_stream(body=Body.async_from_path("hello.txt"))
        print(response)

Error Handling

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

from capo_bedrock_runtime import AsyncBedrockRuntimeClient
from capo_bedrock_runtime.error import AccessDeniedException


async def main():
    async with AsyncBedrockRuntimeClient() as bedrock_runtime:
        try:
            await bedrock_runtime.get_async_invoke()
        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_runtime import AsyncBedrockRuntimeClient


async def main():
    async with AsyncBedrockRuntimeClient() as bedrock_runtime:
        # Default: 3 attempts for every operation
        response = await bedrock_runtime.get_async_invoke()

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

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

Metadata

Release files for capo-bedrock-runtime 0.14.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-runtime 0.14.0
File Size Uploaded Provenance
capo_bedrock_runtime-0.14.0.tar.gz 166.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-bedrock-runtime 0.14.0
File Interpreter ABI Platform
capo_bedrock_runtime-0.14.0-py3-none-any.whl Python 3 none any Details

Total release size: 522.2 kB

Release files / capo_bedrock_runtime-0.14.0.tar.gz

Download URL capo_bedrock_runtime-0.14.0.tar.gz
Size 166.0 kB
Tags Source
SHA-256 checksum
How to use checksums
c6da8ec6bbaa68884ce8459af384f2dea6503a4dca42823f7126744a6331ec14
BLAKE2b-256 checksum
How to use checksums
3a2f712ca212e03ea737e4433c339a77ffa74735ff5e95bb8570dab812017961
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_runtime-0.14.0-py3-none-any.whl

Download URL capo_bedrock_runtime-0.14.0-py3-none-any.whl
Size 356.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8009bda0682121c886dc2d287ac573d0ae20ce0685f0952abee9ef15d451128e
BLAKE2b-256 checksum
How to use checksums
ffa90f7742bc3c7bbcc91248d65c087200a96e6c8b0710f1e24f33774817882d
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-runtime 0.14.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