mypy-boto3-amplify

boto3.typed

Type annotations for boto3 Amplify 1.43.115 compatible with VSCode, PyCharm, Emacs, Sublime Text, mypy, pyright and other tools.

Generated with mypy-boto3-builder 8.12.0.

More information can be found on boto3-stubs page and in mypy-boto3-amplify docs.

See how it helps you find and fix potential bugs:

types-boto3 demo

mypy-boto3-amplify

How to install

Generate locally (recommended)

You can generate type annotations for boto3 package locally with mypy-boto3-builder. Use uv for build isolation.

Run mypy-boto3-builder in your package root directory: uvx --with 'boto3==1.43.115' mypy-boto3-builder
Select boto3-stubs AWS SDK.
Add Amplify service.
Use provided commands to install generated packages.

VSCode extension

Add AWS Boto3 extension to your VSCode and run AWS boto3: Quick Start command.

Click Modify and select boto3 common and Amplify.

From PyPI with pip

Install boto3-stubs for Amplify service.

# install with boto3 type annotations
python -m pip install 'boto3-stubs[amplify]'

# Lite version does not provide session.client/resource overloads
# it is more RAM-friendly, but requires explicit type annotations
python -m pip install 'boto3-stubs-lite[amplify]'

# standalone installation
python -m pip install mypy-boto3-amplify

How to uninstall

python -m pip uninstall -y mypy-boto3-amplify

Usage

VSCode

Install Python extension
Install Pylance extension
Set Pylance as your Python Language Server
Install boto3-stubs[amplify] in your environment:

python -m pip install 'boto3-stubs[amplify]'

Both type checking and code completion should now work. No explicit type annotations required, write your boto3 code as usual.

PyCharm

⚠️ Due to slow PyCharm performance on Literal overloads (issue PY-40997), it is recommended to use boto3-stubs-lite until the issue is resolved.

⚠️ If you experience slow performance and high CPU usage, try to disable PyCharm type checker and use mypy or pyright instead.

⚠️ To continue using PyCharm type checker, you can try to replace boto3-stubs with boto3-stubs-lite:

pip uninstall boto3-stubs
pip install boto3-stubs-lite

Install boto3-stubs[amplify] in your environment:

python -m pip install 'boto3-stubs[amplify]'

Both type checking and code completion should now work.

Emacs

Install boto3-stubs with services you use in your environment:

python -m pip install 'boto3-stubs[amplify]'

Install use-package, lsp, company and flycheck packages
Install lsp-pyright package

(use-package lsp-pyright
  :ensure t
  :hook (python-mode . (lambda ()
                          (require 'lsp-pyright)
                          (lsp)))  ; or lsp-deferred
  :init (when (executable-find "python3")
          (setq lsp-pyright-python-executable-cmd "python3"))
  )

Make sure emacs uses the environment where you have installed boto3-stubs

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Sublime Text

Install boto3-stubs[amplify] with services you use in your environment:

python -m pip install 'boto3-stubs[amplify]'

Install LSP-pyright package

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Other IDEs

Not tested, but as long as your IDE supports mypy or pyright, everything should work.

mypy

Install mypy: python -m pip install mypy
Install boto3-stubs[amplify] in your environment:

python -m pip install 'boto3-stubs[amplify]'

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

pyright

Install pyright: npm i -g pyright
Install boto3-stubs[amplify] in your environment:

python -m pip install 'boto3-stubs[amplify]'

Optionally, you can install boto3-stubs to typings directory.

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Pylint compatibility

It is totally safe to use TYPE_CHECKING flag in order to avoid mypy-boto3-amplify dependency in production. However, there is an issue in pylint that it complains about undefined variables. To fix it, set all types to object in non-TYPE_CHECKING mode.

from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from mypy_boto3_ec2 import EC2Client, EC2ServiceResource
    from mypy_boto3_ec2.waiters import BundleTaskCompleteWaiter
    from mypy_boto3_ec2.paginators import DescribeVolumesPaginator
else:
    EC2Client = object
    EC2ServiceResource = object
    BundleTaskCompleteWaiter = object
    DescribeVolumesPaginator = object

...

Explicit type annotations

Client annotations

AmplifyClient provides annotations for boto3.client("amplify").

from boto3.session import Session

from mypy_boto3_amplify import AmplifyClient

client: AmplifyClient = Session().client("amplify")

# now client usage is checked by mypy and IDE should provide code completion

Paginators annotations

mypy_boto3_amplify.paginator module contains type annotations for all paginators.

from boto3.session import Session

from mypy_boto3_amplify import AmplifyClient
from mypy_boto3_amplify.paginator import (
    ListAppsPaginator,
    ListBranchesPaginator,
    ListDomainAssociationsPaginator,
    ListJobsPaginator,
)

client: AmplifyClient = Session().client("amplify")

# Explicit type annotations are optional here
# Types should be correctly discovered by mypy and IDEs
list_apps_paginator: ListAppsPaginator = client.get_paginator("list_apps")
list_branches_paginator: ListBranchesPaginator = client.get_paginator("list_branches")
list_domain_associations_paginator: ListDomainAssociationsPaginator = client.get_paginator(
    "list_domain_associations"
)
list_jobs_paginator: ListJobsPaginator = client.get_paginator("list_jobs")

Literals

mypy_boto3_amplify.literals module contains literals extracted from shapes that can be used in user code for type checking.

Full list of Amplify Literals can be found in docs.

from mypy_boto3_amplify.literals import BuildComputeTypeType


def check_value(value: BuildComputeTypeType) -> bool: ...

Type definitions

mypy_boto3_amplify.type_defs module contains structures and shapes assembled to typed dictionaries and unions for additional type checking.

Full list of Amplify TypeDefs can be found in docs.

# TypedDict usage example
from mypy_boto3_amplify.type_defs import AutoBranchCreationConfigOutputTypeDef


def get_value() -> AutoBranchCreationConfigOutputTypeDef:
    return {
        "stage": ...,
    }

How it works

Fully automated mypy-boto3-builder carefully generates type annotations for each service, patiently waiting for boto3 updates. It delivers drop-in type annotations for you and makes sure that:

All available boto3 services are covered.
Each public class and method of every boto3 service gets valid type annotations extracted from botocore schemas.
Type annotations include up-to-date documentation.
Link to documentation is provided for every method.
Code is processed by ruff for readability.

What's new

Implemented features

Fully type annotated boto3, botocore, aiobotocore and aioboto3 libraries
mypy, pyright, VSCode, PyCharm, Sublime Text and Emacs compatibility
Client, ServiceResource, Resource, Waiter Paginator type annotations for each service
Generated TypeDefs for each service
Generated Literals for each service
Auto discovery of types for boto3.client and boto3.resource calls
Auto discovery of types for session.client and session.resource calls
Auto discovery of types for client.get_waiter and client.get_paginator calls
Auto discovery of types for ServiceResource and Resource collections
Auto discovery of types for aiobotocore.Session.create_client calls

Latest changes

Builder changelog can be found in Releases.

Versioning

mypy-boto3-amplify version is the same as related boto3 version and follows Python Packaging version specifiers.

Thank you

Allie Fitter for boto3-type-annotations, this package is based on top of his work
black developers for an awesome formatting tool
Timothy Edmund Crosley for isort and how flexible it is
mypy developers for doing all dirty work for us
pyright team for the new era of typed Python

Documentation

All services type annotations can be found in boto3 docs

Support and contributing

This package is auto-generated. Please reports any bugs or request new features in mypy-boto3-builder repository.

Metadata

Release files for mypy-boto3-amplify 1.43.115

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mypy-boto3-amplify 1.43.115
File	Size	Uploaded	Provenance
mypy_boto3_amplify-1.43.115.tar.gz	22.2 kB	Oct 19, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for mypy-boto3-amplify 1.43.115
File	Interpreter	ABI	Platform	Reset
mypy_boto3_amplify-1.43.115-py3-none-any.whl 30.8 kB Oct 19, 2026 Without provenance	Python 3	none	any	Details

Total release size: 52.9 kB

Release files / mypy_boto3_amplify-1.43.115.tar.gz

Download URL	mypy_boto3_amplify-1.43.115.tar.gz
Size	22.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`3c70d83fe7b314275f9e26aaa94bafb9bedb442091bc7c4c174888d185c5646e`
BLAKE2b-256 checksum How to use checksums	`a25cb14f1c9c94766c4ee05cc6e68d6635366032c12c170abd6554f88101c3d8`
Upload date	Oct 19, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.16`

Release files / mypy_boto3_amplify-1.43.115-py3-none-any.whl

Download URL	mypy_boto3_amplify-1.43.115-py3-none-any.whl
Size	30.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`d58e29e80647357721ef28920fd92cef2ac8c836c394d683bcd10d8e7feafe15`
BLAKE2b-256 checksum How to use checksums	`03d857f71fb2bf3b0d3362e8750b5374f3ce63c93f0170dd01110c8107a0a399`
Upload date	Oct 19, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.16`

Security for mypy-boto3-amplify 1.43.115

Report project as malware

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.