aws lambda integration

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

AWS Lambda packaging approaches for Pydantic

Pydantic integrates well with AWS Lambda functions using three main approaches: .zip file archives to package code and dependencies, AWS Lambda Layers to share libraries across multiple functions, or container images to package code and dependencies. If using Pydantic across multiple functions, AWS Lambda Layers are recommended for seamless sharing of libraries.

Pip command for installing Pydantic on AWS Lambda

When installing Pydantic for AWS Lambda in a local virtual environment or Lambda Layer, use a pip command with platform-specific flags to ensure compatibility. The recommended command uses: --platform manylinux2014_x86_64 (or corresponding Lambda runtime platform), --target=<your_package_dir> to specify installation directory, --implementation cp for CPython, --python-version 3.10 (or compatible version), --only-binary=:all: to ensure pre-built binary wheels, and --upgrade pydantic to install the latest version.

Missing pydantic_core module error

The error 'no module named pydantic_core._pydantic_core' indicates Pydantic was installed incorrectly for the Lambda environment. To debug: (1) Check the installed pydantic-core package contains the compiled library and type stubs, expecting two files like PackagePath('pydantic_core/_pydantic_core.pyi') and PackagePath('pydantic_core/_pydantic_core.cpython-312-x86_64-linux-gnu.so'); (2) Verify the Lambda's Python version matches the compiled library version by comparing the suffix from sysconfig.get_config_var('EXT_SUFFIX') with the compiled library suffix.

Platform and Python version mismatches in Lambda

Most common build errors when installing Pydantic for Lambda are: OS or CPU architecture mismatches (darwin vs x86_64-linux-gnu), fixed by passing correct --platform argument (manylinux2014_x86_64 or manylinux2014_aarch64) or building in a Linux Docker container; Python version mismatches (cpython-310 vs cpython-312), fixed by passing correct --python-version argument to pip install.

Email-validator package metadata missing in Lambda

Pydantic uses version from importlib.metadata to check the installed email-validator version, which is incompatible with AWS Lambda environments. For serverless framework deployments using serverless-python-requirements, set slim: false in serverless.yml under pythonRequirements to include package metadata. For .zip archives, ensure the dist-info directory for email-validator is included in the archive.

Validating event and context data in AWS Lambda

Pydantic can validate event and context data in AWS Lambda functions. For debugging validation failures that disappear with invocation, integration with Logfire records each failed validation with its payload, and Logfire's AWS Lambda integration captures the surrounding invocation context.

Give your agent this brain