chore: remove v2/aws-sam and update the Lambda Web Adapter - #5303
Conversation
github.com/awslabs/aws-lambda-go-api-proxy was archived on 21 May 2025. The maintainers deprecated it in favour of Lambda Web Adapter, which is a Lambda layer or container extension rather than a Go library, so there is no drop-in replacement import and no path to a Fiber v3 adapter. The library's Fiber adapter only ever supported Fiber v2, which is the sole reason this recipe was still on Fiber v2 and the only thing keeping the v2/ directory alive. aws-sam-container already covers the same ground on current dependencies: SAM, Fiber v3, Lambda Web Adapter, and no adapter code at all, just app.Listen. Porting v2/aws-sam would have produced a near-duplicate whose only distinguishing feature is zip instead of container packaging, so it is removed rather than migrated. It was not listed in the README recipe index either. Removing it takes the archived dependency and the last Fiber v2 recipe out of the repository, and empties the v2/ directory. Also bumps the Lambda Web Adapter in aws-sam-container from 0.7.0 to 1.1.0. Verified against the ECR Public registry: 1.1.0 is the newest tag and is a multi-arch manifest list covering linux/amd64 and linux/arm64, and upstream still documents the same /lambda-adapter source path for the 1.x line. The image build itself was not exercised here, since no Docker daemon is available in this environment. The two remaining Fiber v2 references are unaffected and need no action: openapi pulls it in through huma's humafiber adapter, and svelte-netlify only has it as an unreachable module-graph entry. Both resolve to v2.52.14, the latest release with no open advisories.
📝 WalkthroughWalkthroughThe AWS SAM container image now uses AWS Lambda Web Adapter version 1.1.0. The standalone AWS SAM example README and application entry point were deleted. ChangesAWS SAM recipe updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Removes the legacy v2/aws-sam recipe that depended on the archived aws-lambda-go-api-proxy Fiber v2 adapter, and updates the aws-sam-container recipe to use a newer Lambda Web Adapter image tag.
Changes:
- Deleted the entire
v2/aws-samSAM zip-based example (template, config, docs, and Go module). - Updated
aws-sam-containerto copy the Lambda Web Adapter extension frompublic.ecr.aws/awsguru/aws-lambda-adapter:1.1.0.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| v2/aws-sam/template.yaml | Removed SAM template for the deprecated v2 recipe. |
| v2/aws-sam/samconfig.toml | Removed SAM CLI config for the deprecated v2 recipe. |
| v2/aws-sam/README.md | Removed documentation for the deprecated v2 recipe. |
| v2/aws-sam/app/main.go | Removed Lambda handler using the archived aws-lambda-go-api-proxy Fiber adapter. |
| v2/aws-sam/app/go.mod | Removed Go module for the deprecated v2 recipe (including archived dependency). |
| v2/aws-sam/app/go.sum | Removed Go dependency lockfile for the deprecated v2 recipe. |
| aws-sam-container/app/Dockerfile | Bumped the Lambda Web Adapter image tag used for the extension layer. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Background
github.com/awslabs/aws-lambda-go-api-proxywas archived on 21 May 2025. The maintainers deprecated it in favour of Lambda Web Adapter:Lambda Web Adapter is a Lambda layer or container extension, not a Go library, so there is no drop-in replacement import. And since the archived library's Fiber adapter only ever supported Fiber v2, there will never be a v3 version of it.
That adapter was the only reason
v2/aws-samwas still on Fiber v2, and that recipe was the only thing keeping thev2/directory alive.Why remove instead of port
aws-sam-containeralready covers the same ground on current dependencies:v2/aws-samaws-sam-container/fiberapp.ListenPorting
v2/aws-samto Lambda Web Adapter would have produced a near-duplicate ofaws-sam-containerwhose only distinguishing feature is zip instead of container packaging. It was also never listed in the README recipe index.Removing it takes the archived dependency and the last Fiber v2 recipe out of the repository, and empties
v2/.Dropped along with it: a dead
replace gopkg.in/yaml.v2 => v2.2.8in that recipe'sgo.mod.go mod whyreportedmain module does not need module gopkg.in/yaml.v2.README index
No change needed, verified rather than assumed.
v2/aws-samwas never linked from the rootREADME.md, which has no reference tov2/at all and no nested-path links. After this removal the index is exactly consistent: 87 links, 87 recipe directories, no dead links and no unlisted recipes.Lambda Web Adapter bump
aws-sam-containerpinnedaws-lambda-adapter:0.7.0. Updated to 1.1.0.Verified against the ECR Public registry rather than assumed:
1.1.0is the newest tag (1.1.0,1.1.0-aarch64,1.1.0-x86_64, ahead of1.0.1)manifest.list.v2coveringlinux/amd64andlinux/arm64, matching how the Dockerfile consumes it/lambda-adaptersource path for the 1.x line, so theCOPY --fromis unchanged apart from the tagThe image build itself was not exercised, since no Docker daemon is available in this environment. Worth a local
docker buildbefore merging.Remaining Fiber v2 references
Both are unaffected and need no action. Each resolves to v2.52.14, the latest release with no open advisories:
openapipulls it in throughhuma/v2/adapters/humafiber, which targets Fiber v2 upstreamsvelte-netlifyhas it only as an unreachable module-graph entry, with nogo.sumentry andgo mod whyreportingmain module does not need modulesvelte-netlifystill depends on the archived library for itscorepackage. That is handled in #5304.Summary by CodeRabbit
Updates
Removed