fix(lambda): bump the aws-powertools group in /lambdas with 4 updates #4425

dependabot · 2025-02-17T19:14:37Z

Bumps the aws-powertools group in /lambdas with 4 updates: @aws-lambda-powertools/parameters, @aws-lambda-powertools/logger, @aws-lambda-powertools/metrics and @aws-lambda-powertools/tracer.

Updates @aws-lambda-powertools/parameters from 2.13.1 to 2.14.0

Release notes

Sourced from @aws-lambda-powertools/parameters's releases.

v2.14.0

Summary

In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.

Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥

⭐️ Thanks to @VatsalGoel3 and @cyrildewit for their contributions to this release!

Working with S3 events delivered via SQS

Docs

When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the S3SqsEventNotificationSchema built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.

New AWS Transfer Family schema

Docs

You can now work with AWS Transfer Family events using the new TransferFamilySchema built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.

Prevent overwriting Logger standard keys

Docs

Before this release, customers could overwrite the standard Logger keys such as level, message, service or even timestamp with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.

Lambda layer SSM Parameter lookup

Docs

You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the /aws/service/powertools/typescript/generic/all/latest to fetch the ARN of the current latest layer or /aws/service/powertools/beta/typescript/generic/all/<semantic-version> to get the one for a specific version published on npmjs.com.

This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:
aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest
Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:
const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', {
  parameterName: '/aws/service/powertools/typescript/generic/all/latest'
</tr></table> 

... (truncated)

Changelog

Sourced from @aws-lambda-powertools/parameters's changelog.

2.14.0 (2025-02-10)

Bug Fixes

logger: prevent overwriting standard keys (#3553) (f0bdf3c)

parser: parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (#3529) (bcd4b9f)

Features

ci: Add advanced automation (#3438) (4e9ff07)

parser: add TransferFamilySchema for AWS Transfer Family events (#3575) (2c27c5e)

parser: simplify ParseResult and parse inference (#3568) (95762ad)

Commits

a40b326 chore(ci): bump version to 2.14.0 (#3582)
9060e54 chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...
3e1aaa8 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3579)
a59b097 chore(ci): remove pinned actions & pkg versions (#3576)
a5708be chore(deps): bump esbuild from 0.24.2 to 0.25.0 (#3581)
a5cc74f docs: add SSM examples to docs (#3577)
2c27c5e feat(parser): add TransferFamilySchema for AWS Transfer Family events (#3575)
66364b5 chore(deps): bump squidfunk/mkdocs-material from 7e841df to c62453b in /d...
8df0430 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3569)
3ae87c3 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3570)
Additional commits viewable in compare view

Updates @aws-lambda-powertools/logger from 2.13.1 to 2.14.0

Release notes

Sourced from @aws-lambda-powertools/logger's releases.

v2.14.0

Summary

In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.

Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥

⭐️ Thanks to @VatsalGoel3 and @cyrildewit for their contributions to this release!

Working with S3 events delivered via SQS

Docs

When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the S3SqsEventNotificationSchema built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.

New AWS Transfer Family schema

Docs

You can now work with AWS Transfer Family events using the new TransferFamilySchema built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.

Prevent overwriting Logger standard keys

Docs

Before this release, customers could overwrite the standard Logger keys such as level, message, service or even timestamp with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.

Lambda layer SSM Parameter lookup

Docs

You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the /aws/service/powertools/typescript/generic/all/latest to fetch the ARN of the current latest layer or /aws/service/powertools/beta/typescript/generic/all/<semantic-version> to get the one for a specific version published on npmjs.com.

This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:
aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest
Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:
const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', {
  parameterName: '/aws/service/powertools/typescript/generic/all/latest'
</tr></table> 

... (truncated)

Changelog

Sourced from @aws-lambda-powertools/logger's changelog.

2.14.0 (2025-02-10)

Bug Fixes

logger: prevent overwriting standard keys (#3553) (f0bdf3c)

parser: parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (#3529) (bcd4b9f)

Features

ci: Add advanced automation (#3438) (4e9ff07)

parser: add TransferFamilySchema for AWS Transfer Family events (#3575) (2c27c5e)

parser: simplify ParseResult and parse inference (#3568) (95762ad)

Commits

a40b326 chore(ci): bump version to 2.14.0 (#3582)
9060e54 chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...
3e1aaa8 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3579)
a59b097 chore(ci): remove pinned actions & pkg versions (#3576)
a5708be chore(deps): bump esbuild from 0.24.2 to 0.25.0 (#3581)
a5cc74f docs: add SSM examples to docs (#3577)
2c27c5e feat(parser): add TransferFamilySchema for AWS Transfer Family events (#3575)
66364b5 chore(deps): bump squidfunk/mkdocs-material from 7e841df to c62453b in /d...
8df0430 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3569)
3ae87c3 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3570)
Additional commits viewable in compare view

Updates @aws-lambda-powertools/metrics from 2.13.1 to 2.14.0

Release notes

Sourced from @aws-lambda-powertools/metrics's releases.

v2.14.0

Summary

In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.

Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥

⭐️ Thanks to @VatsalGoel3 and @cyrildewit for their contributions to this release!

Working with S3 events delivered via SQS

Docs

When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the S3SqsEventNotificationSchema built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.

New AWS Transfer Family schema

Docs

You can now work with AWS Transfer Family events using the new TransferFamilySchema built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.

Prevent overwriting Logger standard keys

Docs

Before this release, customers could overwrite the standard Logger keys such as level, message, service or even timestamp with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.

Lambda layer SSM Parameter lookup

Docs

You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the /aws/service/powertools/typescript/generic/all/latest to fetch the ARN of the current latest layer or /aws/service/powertools/beta/typescript/generic/all/<semantic-version> to get the one for a specific version published on npmjs.com.

This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:
aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest
Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:
const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', {
  parameterName: '/aws/service/powertools/typescript/generic/all/latest'
</tr></table> 

... (truncated)

Changelog

Sourced from @aws-lambda-powertools/metrics's changelog.

2.14.0 (2025-02-10)

Bug Fixes

logger: prevent overwriting standard keys (#3553) (f0bdf3c)

parser: parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (#3529) (bcd4b9f)

Features

ci: Add advanced automation (#3438) (4e9ff07)

parser: add TransferFamilySchema for AWS Transfer Family events (#3575) (2c27c5e)

parser: simplify ParseResult and parse inference (#3568) (95762ad)

Commits

a40b326 chore(ci): bump version to 2.14.0 (#3582)
9060e54 chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...
3e1aaa8 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3579)
a59b097 chore(ci): remove pinned actions & pkg versions (#3576)
a5708be chore(deps): bump esbuild from 0.24.2 to 0.25.0 (#3581)
a5cc74f docs: add SSM examples to docs (#3577)
2c27c5e feat(parser): add TransferFamilySchema for AWS Transfer Family events (#3575)
66364b5 chore(deps): bump squidfunk/mkdocs-material from 7e841df to c62453b in /d...
8df0430 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3569)
3ae87c3 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3570)
Additional commits viewable in compare view

Updates @aws-lambda-powertools/tracer from 2.13.1 to 2.14.0

Release notes

Sourced from @aws-lambda-powertools/tracer's releases.

v2.14.0

Summary

In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.

Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥

⭐️ Thanks to @VatsalGoel3 and @cyrildewit for their contributions to this release!

Working with S3 events delivered via SQS

Docs

When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the S3SqsEventNotificationSchema built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.

New AWS Transfer Family schema

Docs

You can now work with AWS Transfer Family events using the new TransferFamilySchema built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.

Prevent overwriting Logger standard keys

Docs

Before this release, customers could overwrite the standard Logger keys such as level, message, service or even timestamp with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.

Lambda layer SSM Parameter lookup

Docs

You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the /aws/service/powertools/typescript/generic/all/latest to fetch the ARN of the current latest layer or /aws/service/powertools/beta/typescript/generic/all/<semantic-version> to get the one for a specific version published on npmjs.com.

This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:
aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest
Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:
const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', {
  parameterName: '/aws/service/powertools/typescript/generic/all/latest'
</tr></table> 

... (truncated)

Changelog

Sourced from @aws-lambda-powertools/tracer's changelog.

2.14.0 (2025-02-10)

Bug Fixes

logger: prevent overwriting standard keys (#3553) (f0bdf3c)

parser: parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (#3529) (bcd4b9f)

Features

ci: Add advanced automation (#3438) (4e9ff07)

parser: add TransferFamilySchema for AWS Transfer Family events (#3575) (2c27c5e)

parser: simplify ParseResult and parse inference (#3568) (95762ad)

Commits

a40b326 chore(ci): bump version to 2.14.0 (#3582)
9060e54 chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...
3e1aaa8 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3579)
a59b097 chore(ci): remove pinned actions & pkg versions (#3576)
a5708be chore(deps): bump esbuild from 0.24.2 to 0.25.0 (#3581)
a5cc74f docs: add SSM examples to docs (#3577)
2c27c5e feat(parser): add TransferFamilySchema for AWS Transfer Family events (#3575)
66364b5 chore(deps): bump squidfunk/mkdocs-material from 7e841df to c62453b in /d...
8df0430 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3569)
3ae87c3 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3570)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

npalm · 2025-02-19T21:20:29Z

@dependabot recreate

Bumps the aws-powertools group in /lambdas with 4 updates: [@aws-lambda-powertools/parameters](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/metrics](https://github.com/aws-powertools/powertools-lambda-typescript) and [@aws-lambda-powertools/tracer](https://github.com/aws-powertools/powertools-lambda-typescript). Updates `@aws-lambda-powertools/parameters` from 2.13.1 to 2.14.0 - [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases) - [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md) - [Commits](aws-powertools/powertools-lambda-typescript@v2.13.1...v2.14.0) Updates `@aws-lambda-powertools/logger` from 2.13.1 to 2.14.0 - [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases) - [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md) - [Commits](aws-powertools/powertools-lambda-typescript@v2.13.1...v2.14.0) Updates `@aws-lambda-powertools/metrics` from 2.13.1 to 2.14.0 - [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases) - [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md) - [Commits](aws-powertools/powertools-lambda-typescript@v2.13.1...v2.14.0) Updates `@aws-lambda-powertools/tracer` from 2.13.1 to 2.14.0 - [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases) - [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md) - [Commits](aws-powertools/powertools-lambda-typescript@v2.13.1...v2.14.0) --- updated-dependencies: - dependency-name: "@aws-lambda-powertools/parameters" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: aws-powertools - dependency-name: "@aws-lambda-powertools/logger" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: aws-powertools - dependency-name: "@aws-lambda-powertools/metrics" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: aws-powertools - dependency-name: "@aws-lambda-powertools/tracer" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: aws-powertools ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot requested a review from a team as a code owner February 17, 2025 19:14

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Feb 17, 2025

npalm previously approved these changes Feb 19, 2025

View reviewed changes

dependabot bot dismissed npalm’s stale review via 20df8e7 February 19, 2025 21:21

dependabot bot force-pushed the dependabot/npm_and_yarn/lambdas/aws-powertools-2956d12df2 branch from 2ea2755 to 20df8e7 Compare February 19, 2025 21:21

dependabot bot force-pushed the dependabot/npm_and_yarn/lambdas/aws-powertools-2956d12df2 branch from 20df8e7 to 1efb5b3 Compare February 19, 2025 21:23

npalm approved these changes Feb 19, 2025

View reviewed changes

npalm merged commit 49d40b3 into main Feb 19, 2025
5 checks passed

npalm deleted the dependabot/npm_and_yarn/lambdas/aws-powertools-2956d12df2 branch February 19, 2025 21:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(lambda): bump the aws-powertools group in /lambdas with 4 updates #4425

fix(lambda): bump the aws-powertools group in /lambdas with 4 updates #4425

Uh oh!

dependabot bot commented on behalf of github Feb 17, 2025 •

edited

Loading

Uh oh!

npalm commented Feb 19, 2025

Uh oh!

Uh oh!

Uh oh!

fix(lambda): bump the aws-powertools group in /lambdas with 4 updates #4425

fix(lambda): bump the aws-powertools group in /lambdas with 4 updates #4425

Uh oh!

Conversation

dependabot bot commented on behalf of github Feb 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v2.14.0

Summary

Working with S3 events delivered via SQS

New AWS Transfer Family schema

Prevent overwriting Logger standard keys

Lambda layer SSM Parameter lookup

2.14.0 (2025-02-10)

Bug Fixes

Features

v2.14.0

Summary

Working with S3 events delivered via SQS

New AWS Transfer Family schema

Prevent overwriting Logger standard keys

Lambda layer SSM Parameter lookup

2.14.0 (2025-02-10)

Bug Fixes

Features

v2.14.0

Summary

Working with S3 events delivered via SQS

New AWS Transfer Family schema

Prevent overwriting Logger standard keys

Lambda layer SSM Parameter lookup

2.14.0 (2025-02-10)

Bug Fixes

Features

v2.14.0

Summary

Working with S3 events delivered via SQS

New AWS Transfer Family schema

Prevent overwriting Logger standard keys

Lambda layer SSM Parameter lookup

2.14.0 (2025-02-10)

Bug Fixes

Features

Uh oh!

npalm commented Feb 19, 2025

Uh oh!

Uh oh!

Uh oh!

dependabot bot commented on behalf of github Feb 17, 2025 •

edited

Loading