poetry: bump aws-lambda-powertools from 2.35.1 to 3.26.0

[dependabot]

Bumps aws-lambda-powertools from 2.35.1 to 3.26.0.

Release notes

Sourced from aws-lambda-powertools's releases.

v3.26.0

Summary

In this release, we are pleased to announce a new utility for interacting with the Lambda Metadata Service, allowing you to easily retrieve information about the Lambda function, such as the Availability Zone ID.

A huge thanks to @​acascell, @​shaked-lokits, @​maxrabin, and @​amin-farjadi, for their contributions 🚀🌟

Lambda Metadata Service

Docs

You can now use get_lambda_metadata() function fetch metadata from the AWS Lambda Metadata endpoint, such as the Availability Zone ID. Results are cached for the sandbox lifetime and the utility automatically returns empty metadata outside of Lambda, so your code works seamlessly in local development and testing.

from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.metadata import LambdaMetadata, get_lambda_metadata
from aws_lambda_powertools.utilities.typing import LambdaContext
logger = Logger()
def lambda_handler(event: dict, context: LambdaContext) -> dict:
metadata: LambdaMetadata = get_lambda_metadata()
az_id = metadata.availability_zone_id  # e.g., "use1-az1"
logger.append_keys(az_id=az_id)
logger.info("Processing request")
return {"az_id": az_id}

Changes

• fix(ci): add ty check to parameters folder (#8035) by @​leandrodamascena
• feat(buffer-handler): add buffering support for external loggers (#7994) by @​acascell

📜 Documentation updates

• feat: add ldms feature (#8051) by @​leandrodamascena
• feat(batch): add Kafka/MSK batch processing support (#7941) by @​shaked-lokits

🐛 Bug and hot fixes

• fix(openapi): correct response validation for falsy objects (#7990) by @​amin-farjadi

🔧 Maintenance

• fix(ci): add ty check to dataclasses utility (#8038) by @​leandrodamascena
• fix(ci): add ty check to parser folder (#8037) by @​leandrodamascena
• chore(deps): bump valkey-glide from 2.2.5 to 2.2.7 (#8030) by @dependabot[bot]

... (truncated)

Changelog

Sourced from aws-lambda-powertools's changelog.

[v3.26.0] - 2026-03-20

Features

• add ldms feature (#8051)

Maintenance

• version bump

[v3.25.0] - 2026-03-12

Bug Fixes

• ci: remove DUB region (#8031)
• event-handler: prevent OpenAPI schema bleed when reusing response dictionaries (#7952)
• event_handler: add middleware validation per route (#8020)
• event_handler: fix bug regression in Annotated field (#7904)
• event_handler: return 415 status_code for unsupported content-type headers (#7980)
• event_handler: sync alias and validation_alias for Pydantic 2.12+ compatibility (#7901)
• event_handler: preserve openapi_examples on Body (#7862)
• logger: preserve percent-style formatting args in flush_buffer (#8009)
• parameters: fix variable shadowing in SSM parameter chunking (#8006)
• typing: resolve ty diagnostics in logging and metrics modules (#7953)
• typing: accept Mapping type in resolve() for event parameter (#7909)

Code Refactoring

• batch: improve type annotation for event parameter (#7924)

Documentation

• clarify append_context_keys behavior with overlapping keys (#7846)

Features

• Add a flag to ALBResolver to URL-decode query parameters (#7940)
• add HttpResolverAlpha resolver (#7913)
• decorators: Support Durable Context in logger and metric decorators (#7765)
• event-handler: add per-route validation support (#7965)
• event_source: add support for S3 IntelligentTiering events (#7954)
• metrics: add support for multiple dimension sets (#7848)
• openapi: add support for micro Lambda pattern (#7920)

Maintenance

• remove unused PR automation workflows (#8008)
• adding fuzzing tests (#7903)
• update swagger ui files (#7914)
• version bump

... (truncated)

Upgrade guide

Sourced from aws-lambda-powertools's upgrade guide.

---

title: Upgrade guide description: Guide to update between major Powertools for AWS Lambda (Python) versions

End of support v2

!!! warning "On March 25st, 2025, Powertools for AWS Lambda (Python) v2 reached end of support and will no longer receive updates or releases. If you are still using v2, we strongly recommend you to read our upgrade guide and update to the latest version."

Given our commitment to all of our customers using Powertools for AWS Lambda (Python), we will keep Pypi{target="_blank"} v2 releases and documentation 2.x versions to prevent any disruption.

Migrate to v3 from v2

!!! info "We strongly encourage you to migrate to v3. However, if you still need to upgrade from v1 to v2, you can find the upgrade guide."

We've made minimal breaking changes to make your transition to v3 as smooth as possible.

Quick summary

Area	Change	Code change required
Pydantic	We have removed support for Pydantic v1	No
Parser	We have replaced DynamoDBStreamModel AttributeValue with native Python types	Yes
Parser	We no longer export Pydantic objects from parser.pydantic.	Yes
Lambda layer	Lambda layers are now compiled according to the specific Python version and architecture	No
Event Handler	We have deprecated the get_header_value function.	Yes
Batch Processor	@batch_processor and @async_batch_processor decorators are now deprecated	Yes
Event Source Data Classes	We have updated default values for optional fields.	Yes
Parameters	The default cache TTL is now set to 5 minutes	No
Parameters	The config parameter is deprecated in favor of boto_config	Yes
JMESPath Functions	The extract_data_from_envelope function is deprecated in favor of query	Yes
Types file	We have removed the type imports from the shared/types.py file	Yes

First Steps

Before you start, we suggest making a copy of your current working project or create a new branch with git.

1. Upgrade Python to at least v3.10.
2. Ensure you have the latest version via Lambda Layer or PyPi{target="_blank"}.
3. Review the following sections to confirm if you need to make changes to your code.

Drop support for Pydantic v1

!!! note "No code changes required"

As of June 30, 2024, Pydantic v1 has reached its end-of-life, and we have discontinued support for this version. We now exclusively support Pydantic v2.

Use Pydantic v2 Migration Guide{target="_blank"} to migrate your custom Pydantic models to v2.

... (truncated)

Commits

• f59417a chore: version bump
• 90fbae6 feat: add ldms feature (#8051)
• 1047397 fix(ci): add ty check to dataclasses utility (#8038)
• 62591e7 fix(ci): add ty check to parser folder (#8037)
• 04436bd fix(ci): add ty check to parameters folder (#8035)
• 7929795 feat(buffer-handler): add buffering support for external loggers (#7994)
• d986de3 feat(batch): add Kafka/MSK batch processing support (#7941)
• 7b6cdce fix(openapi): correct response validation for falsy objects (#7990)
• f7290ae chore(deps): bump valkey-glide from 2.2.5 to 2.2.7 (#8030)
• 623965d chore(deps): bump aws-encryption-sdk from 4.0.3 to 4.0.4 (#8027)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

💥 Something went wrong while deploying the pull request environment.
Check Output Logs