Registry /
type-stubs / mypy-boto3-amplifyuibuilder
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.653s · 53.5MB
glibcpy 3.10–3.910 runs
installs and imports cleanly · install 5.5s · import 0.594s · 54MB
52MB installed
● package 52MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
AmplifyUIBuilderClient
✓ from mypy_boto3_amplifyuibuilder.client import AmplifyUIBuilderClient
✗ from boto3.client import AmplifyUIBuilderClient
The client type hint is imported from the specific `mypy-boto3-amplifyuibuilder` stub package, not directly from `boto3`.
This quickstart demonstrates how to obtain a type-hinted `AmplifyUIBuilderClient` using `boto3` and the `mypy-boto3-amplifyuibuilder` stubs. The `TYPE_CHECKING` guard ensures the stub import is only active during type checking, avoiding a runtime dependency on the stub package itself. Remember to have `boto3` installed and configured with AWS credentials.
import boto3
from typing import TYPE_CHECKING
if TYPE_CHECKING:
from mypy_boto3_amplifyuibuilder.client import AmplifyUIBuilderClient
def get_amplifyuibuilder_client() -> AmplifyUIBuilderClient:
"""Gets a typed AmplifyUIBuilder client."""
client: AmplifyUIBuilderClient = boto3.client(
"amplifyuibuilder",
region_name="us-east-1"
)
return client
# Example usage (will be type-checked by MyPy)
if __name__ == "__main__":
try:
amplify_client = get_amplifyuibuilder_client()
# Replace with an actual AmplifyUIBuilder API call
# For example, listing components, if any exist
print(f"Client type: {type(amplify_client)}")
# Example: list components (requires valid AWS credentials and existing resources)
# response = amplify_client.list_components()
# print(f"Components: {response.get('entities')}")
print("AmplifyUIBuilder client initialized successfully. Further calls require valid AWS credentials and service usage.")
except Exception as e:
print(f"An error occurred: {e}")
Debug
Known issues
breakingSupport for Python 3.8 has been removed in `mypy-boto3-builder` version 8.12.0, which generates this package. Projects requiring Python 3.8 should use an older version of `mypy-boto3-amplifyuibuilder` or upgrade their Python environment.fixUpgrade to Python 3.9 or higher. If unable to upgrade, pin `mypy-boto3-amplifyuibuilder` to a version generated by `mypy-boto3-builder < 8.12.0`.
affects: >=8.12.0 of mypy-boto3-builder (generates mypy-boto3-amplifyuibuilder >=1.42.3)
breakingThe `mypy-boto3-builder` migrated to PEP 561 compliant packages in version 8.12.0. While this simplifies `mypy` integration, it might affect custom build processes or older tooling that relied on non-PEP 561 distribution methods.fixEnsure your `mypy` configuration is up-to-date and relies on standard package discovery. No specific code changes are typically required unless you have highly customized type-checking setups.
affects: >=8.12.0 of mypy-boto3-builder (generates mypy-boto3-amplifyuibuilder >=1.42.3)
gotchaThis package provides *only* type annotations. You must install `boto3` (and optionally `botocore`) separately for your application to function at runtime. Without `boto3`, your code will raise `ModuleNotFoundError`.fixAlways install `boto3` alongside `mypy-boto3-amplifyuibuilder` (e.g., `pip install boto3 mypy-boto3-amplifyuibuilder`).
affects: All versions
gotchaFor comprehensive type checking, especially when using `boto3.client()` or `boto3.resource()` without explicit type hints, it is recommended to install `boto3-stubs` with the appropriate service extras (e.g., `pip install 'boto3-stubs[amplifyuibuilder]'`). This provides overloads for the generic `boto3` functions.fixInstall `boto3-stubs` with service extras: `pip install 'boto3-stubs[amplifyuibuilder]'`.
affects: All versions
breakingThe `mypy-boto3-builder` (version 8.9.0) introduced changes to TypeDef naming conventions, potentially shortening names or reordering suffixes for clarity (e.g., `CreateDistributionRequestRequestTypeDef` -> `CreateDistributionRequestTypeDef`). If you directly reference these generated TypeDefs in your code, they might have changed.fixReview and update any explicit references to generated TypeDefs in your codebase. Refer to the specific service documentation for the updated TypeDef names.
affects: >=8.9.0 of mypy-boto3-builder
gotchaWhen using `if TYPE_CHECKING:` guards to conditionally import stubs for Pylint compatibility, Pylint might report `undefined variable` errors in the `else` block. This is a known Pylint limitation.fixTo suppress Pylint errors, assign `object` to the client/resource variables in the `else` branch (e.g., `else: AmplifyUIBuilderClient = object`) or use `# type: ignore` for those lines. Refer to the official `mypy-boto3` documentation for Pylint compatibility details.
affects: All versions
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredProvides the actual AWS SDK functionality; mypy-boto3-amplifyuibuilder only provides type annotations.
boto3-stubsoptionalThis package is often installed as a dependency of `boto3-stubs` when specifying service extras, offering comprehensive type annotations for `boto3.client` overloads. While `mypy-boto3-amplifyuibuilder` can be installed directly, using `boto3-stubs` is the recommended approach for full functionality.