Feature request: AWS Lambda Layers support

[saragerion]

Description of the feature request

Problem statement

Currently AWS Lambda Powertools for Python supports usage via a Lambda Layer. The TypeScript Powertools do not.

Summary of the feature

Lambda Layer is a .zip file archive that can contain additional code, pre-packaged dependencies, data, or configuration files. Layers promote code sharing and separation of responsibilities so that you can iterate faster on writing business logic.

This issue would include Lambda Powertools Lambda Layer using AWS Lambda Console, or your preferred deployment framework.

When using Layers, you can add Lambda Powertools as a dev dependency (or as part of your virtual env) to not impact the development process.

Additionally, Lambda Layers allow us to understand who uses this library in a non-intrusive way. This helps us justify and gain future investments for other Lambda Powertools languages.

Code examples

https://awslabs.github.io/aws-lambda-powertools-python/latest/#install

Benefits for you and the wider AWS community

A different way to install and leverage the library.

Describe alternatives you've considered

N/A

Additional context

N/A

Related issues, RFCs

N/A

[orozcoadrian]

Lambda layers can be architecture-specific, if they contain native code. Assuming there's no native code in this library, it will be compatible with both x86 and arm64. It'd be nice to make that explicit in the documentation.

Reference:
https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-to-arm-based-aws-graviton2-processors/#:~:text=Functions%20without%20architecture%2Dspecific%20dependencies%20or%20binaries

For illustration, here's a lambda layer that only works with x86, but there's no mention of it in the docs: https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/image-magick-lambda-layer