Maintenance: remove Parameters utility from Lambda Layers

[dreamorosi]

Summary

In a previous PR we have introduced the Parameters utility as part of the Lambda Layers. After some testing however we have realized that before doing that we need to decide whether we want to include the AWS SDK v3 in the layer or not.

We see this as a one-way door decision and as such, we want to take the time to consider the implications fully before doing it.

Why is this needed?

In order to include the Parameters utility in the Lambda layers we need to investigate the tradeoffs of including also the @aws-sdk/client-* libraries needed. For the nodejs18x runtime that version of the SDK is present in the execution environment, however for runtimes nodejs14x and nodejs16x the SDK is not there and must be included either in the Layer or in the deployment package/bundle.

Which area does this relate to?

Parameters

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v1.11.1 version!