Skip to content

v1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@bnusunny bnusunny released this 18 Sep 22:03
· 18 commits to main since this release
v1.1.0
596bdbc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.1.0

Lambda SnapStart support.

Features

  • SnapStart support (#837): two opt-in hooks, AWS_LWA_SNAPSTART_BEFORE_CHECKPOINT_PATH and AWS_LWA_SNAPSTART_AFTER_RESTORE_PATH, let your app drain before the snapshot and reconnect after restore. A non-2xx or connection failure fails that SnapStart phase. After restore the adapter rebuilds its HTTP client and re-runs the readiness check; external requests to hook paths get 403. The after-restore hook must finish inside Lambda's 10s Restore limit.
  • AWS_LWA_POOL_IDLE_TIMEOUT_SECONDS configures idle keep-alive to your app (default 4s, fractional allowed, 0 disables reuse) (#837)
  • AWS_LWA_READINESS_CHECK_TIMEOUT_SECONDS bounds the readiness check at cold start and after restore; unset stays unbounded as before (#837)
  • New fastapi-snapstart and fastapi-snapstart-zip examples (#837)

Bug Fixes

  • AWS_LWA_REMOVE_BASE_PATH now strips exactly one leading occurrence on a segment boundary — with /api, /api/api/order → /api/order and /apiorder is unchanged. Verify your routes if you relied on the old repeated/partial stripping. (#837)
  • AWS_LWA_ASYNC_INIT is now ignored (with a warning) under SnapStart and Provisioned Concurrency, where finishing init early is harmful. Those functions now wait for the readiness check; bound it with AWS_LWA_READINESS_CHECK_TIMEOUT_SECONDS. (#837)
  • Move nginx-zip to provided.al2023 and drop the PHP examples (#832)

Dependencies

  • Bump lambda_http to 1.3.0 for the SnapStart APIs. Note: on all deployments, a multi-entry API Gateway v2 cookies array is now joined with "; " instead of ";", so code splitting on a bare ; sees leading spaces.

Notes

The crate no longer publishes to crates.io (publish = false) — LWA ships as the lambda-adapter binary, so the Service impl signature changes SnapStart required affect no published API. crates.io consumers keep 1.0.0-rc1.

CI/CD

  • Publish the version-named layer parameter from the pipeline (#846)
  • Group Dependabot example updates and verify only what changed (#844)
  • Fix the deploy-beta SSM parameter collision and retry tool downloads (#843)

Full Changelog: v1.0.1...v1.1.0

Assets 2
Loading