Sourced from software.amazon.lambda:powertools-cloudformation's releases.

v2.3.0

Summary

This release introduces Lambda SnapStart priming techniques to both the powertools-metrics and powertools-idempotency utilities, optimizing cold start performance for customers using SnapStart.

We've also updated dependencies across the library, with the most notable change being the removal of AWS SDK v1 dependency from the powertools-tracing utility, aligning with the recent AWS X-Ray SDK update (Release 2.19.0).

⭐️ Thanks to @​subhash686 for contributing the SnapStart priming techniques!

⚡ Lambda SnapStart Priming

Lambda SnapStart AWS Docs

SnapStart reduces Lambda cold start times by taking a snapshot of your initialized function and reusing it for subsequent invocations. We can run custom code before the snapshot is taken to initialize code that would otherwise be initialized at runtime. This process is referred to as "priming", and this is achieved using Java runtime hooks from the open source CRaC (Coordinated Restore at Checkpoint) project.

The following example shows how to prime an AWS S3 client:

import org.crac.Core;
import org.crac.Resource;
import com.amazonaws.services.lambda.runtime.Context;

import com.amazonaws.services.lambda.runtime.RequestHandler;
import software.amazon.awssdk.services.s3.S3Client;
public class Handler implements RequestHandler<String, String>, Resource {
private final S3Client s3Client = S3Client.create();
public Handler() {

Core.getGlobalContext().register(this);

}
@Override

public String handleRequest(String input, Context context) {

// Business logic using s3Client

return &quot;Hello SnapStart&quot; + input;

}
@Override

public void beforeCheckpoint(org.crac.Context&lt;? extends Resource&gt; context) {

// Will be called before SnapStart takes the snapshot

s3Client.listBuckets();

}
@Override

public void afterRestore(org.crac.Context&lt;? extends Resource&gt; context) {

// Reinitialize after restore

}


</tr></table>

... (truncated)

• 9725d44 chore(ci): bump version to 2.3.0
• 74d3e66 chore: bump org.assertj:assertj-core from 3.27.3 to 3.27.4 (#2031)
• ab66f95 chore: bump software.amazon.awscdk:aws-cdk-lib from 2.208.0 to 2.210.0 (#2030)
• 877042b chore: bump aws.sdk.version from 2.32.18 to 2.32.19 (#2029)
• 174a19f chore: bump co.elastic.logging:logback-ecs-encoder from 1.6.0 to 1.7.0 (#2028)
• 6c84fb7 chore: bump com.github.spotbugs:spotbugs-maven-plugin from 4.8.4.0 to 4.9.3.2...
• 58e09cb chore: bump com.amazonaws:aws-lambda-java-runtime-interface-client (#2026)
• bed5106 chore: bump github/codeql-action from 3.29.7 to 3.29.8 (#2027)
• ca75f24 chore: bump org.crac:crac from 1.4.0 to 1.5.0 (#2025)
• ee79c20 chore: bump aws.sdk.version from 2.32.6 to 2.32.18 (#2024)
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)