Publish every release as a Lambda layer

[moltar]

Is your feature request related to a problem? Please describe.

The problem we are encountering:

• Large bundle sizes (See: Bundle sizes are way too large #3023, esm build targets es5 #2056)
• Duplicate dependencies (esbuild issue Useless repeated imports when using external modules evanw/esbuild#475 )

Which leads to:

• Slow builds
• Slow deployments
• Slow cold starts

Describe the solution you'd like

Publish every release as a predictable Lambda layer.

This would allow us to exclude @aws-sdk/* packages from the bundle, yet target specific and exact package versions via the layer.

A great example of this use case is done by Sentry. They package their Lambda handler as a layer, in every region, and tagged with a version. Then they make the manifest published.

Describe alternatives you've considered

1. Further optimizing the use of @aws-sdk/client-* packages.
2. Switching back to v2
3. Not using SDKs at all

Additional context

🌱 We can help save the planet and make the solution greener by reducing the need to bundle and ship useless bits across the continents.

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[moltar]

Not stale.

GitHub stale bot considered harmful

[kuhe]

We are not planning to do this because the combined size of the hundreds of SDK clients is in the 100-120mb range even after removing things like dist-es, dist-types, and READMEs. This would take up almost half of the function's allowance as a layer.

I recommend creating a layer with the only the SDK clients that you want, which also controls the package versioning.

[aBurmeseDev]

Closing as not planned for the reason mentioned above but if community demand grows significantly, feel free to reopen.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.