Registry /
type-stubs / mypy-boto3-bedrock-data-automation-runtime
Install & Compatibility
Where this runs
tested against v1.43.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.910 runs
installs and imports cleanly · install 0.0s · import 0.000s · 19.6MB
glibcpy 3.10–3.910 runs
installs and imports cleanly · install 3.2s · import 0.000s · 20MB
18MB installed
● package 18MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
RuntimeforBedrockDataAutomationClient
✓ from mypy_boto3_bedrock_data_automation_runtime import RuntimeforBedrockDataAutomationClient
✗ from mypy_boto3_bedrock_data_automation_runtime import RuntimeforBedrockDataAutomationClient
This quickstart demonstrates how to initialize a type-hinted client for the Bedrock Data Automation Runtime service using `boto3` and its corresponding `mypy-boto3` stubs. It includes a placeholder for calling a common operation like `list_tags_for_resource`, highlighting how type checking enhances development.
import boto3
from mypy_boto3_bedrock_data_automation_runtime.client import RuntimeforBedrockDataAutomationClient
from os import environ
def get_bedrock_data_automation_runtime_client() -> RuntimeforBedrockDataAutomationClient:
"""
Initializes and returns a typed Bedrock Data Automation Runtime client.
"""
# Using environment variables for AWS credentials is a common practice
# and makes the example runnable without hardcoding.
# In a real application, boto3 will automatically look for credentials
# in various locations (e.g., ~/.aws/credentials, IAM roles).
aws_access_key_id = environ.get('AWS_ACCESS_KEY_ID', 'YOUR_ACCESS_KEY')
aws_secret_access_key = environ.get('AWS_SECRET_ACCESS_KEY', 'YOUR_SECRET_KEY')
aws_region = environ.get('AWS_REGION', 'us-east-1')
# The actual boto3 client is untyped; mypy-boto3 provides the type hint.
client: RuntimeforBedrockDataAutomationClient = boto3.client(
"bedrock-data-automation-runtime",
region_name=aws_region,
aws_access_key_id=aws_access_key_id,
aws_secret_access_key=aws_secret_access_key
)
return client
if __name__ == "__main__":
bedrock_data_automation_client = get_bedrock_data_automation_runtime_client()
print(f"Successfully created Bedrock Data Automation Runtime client: {bedrock_data_automation_client}")
# Example of calling a method (requires a valid resourceARN for actual execution)
# This demonstrates type-checked interaction with the client.
# In a real application, consult AWS Bedrock Data Automation Runtime API docs for valid operations.
try:
# Replace with a real resource ARN if you want to run this successfully
response = bedrock_data_automation_client.list_tags_for_resource(resourceARN="arn:aws:bedrock:us-east-1:123456789012:data-automation/example")
print("list_tags_for_resource call successful:")
print(response)
except Exception as e:
print(f"Caught exception during list_tags_for_resource call (expected if ARN is not real): {e}")
Debug
Known issues
breakingSupport for Python 3.8 has been removed for all `mypy-boto3-builder` generated packages, including this one, starting with `mypy-boto3-builder` version 8.12.0. The minimum required Python version is now 3.9.fixUpgrade your Python environment to 3.9 or higher.
affects: >=8.12.0 (mypy-boto3-builder)
breakingThe `mypy-boto3-builder` migrated to PEP 561 compliant packages in version 8.12.0. While largely internal, this may affect custom build systems or environments that relied on previous packaging structures.fixEnsure your project's `pyproject.toml` and packaging tools are compatible with PEP 561 standards. Most users installing via `pip` should not experience issues.
affects: >=8.12.0 (mypy-boto3-builder)
breakingTypeDef naming conventions can change between major `mypy-boto3-builder` versions. For example, `CreateDistributionRequestRequestTypeDef` became `CreateDistributionRequestTypeDef`. While this specific change affects the CloudFront service, it's indicative of potential similar changes across other services including Bedrock Data Automation Runtime.fixReview the changelog for `mypy-boto3-builder` and service-specific stubs after updates, and adjust TypeDef imports/usage as necessary.
affects: >=8.9.0 (mypy-boto3-builder)
gotchaThis package provides *only* type annotations. It does not include the `boto3` library itself. `boto3` must be installed separately in your project for the code to run at runtime.fixEnsure `boto3` is installed in your environment: `pip install boto3`.
affects: All versions
gotchaPyCharm may experience slow performance or high CPU usage when dealing with `Literal` overloads in `mypy-boto3` packages. This is a known issue (PY-40997) within PyCharm.fixConsider using `boto3-stubs-lite` (if its limitations are acceptable), or disable PyCharm's internal type checker and rely on external tools like `mypy` or `pyright`.
affects: All versions with PyCharm
gotchaA specific fix for `ToolUseTypeType` literal was applied for the `bedrock-runtime` service in `mypy-boto3-builder` 8.12.0. While this package is for `bedrock-data-automation-runtime`, similar service-specific literal typing issues might appear or have been fixed in past versions, requiring updates.fixAlways keep your `mypy-boto3` packages updated to benefit from the latest type definition fixes and improvements.
affects: Potentially pre-8.12.0 for related Bedrock services
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredThis library provides type stubs for the `boto3` AWS SDK. `boto3` is required at runtime to execute AWS operations.
typing-extensionsoptionalOften a transitive dependency for advanced type hints, especially on older Python versions.