Bump the npm group across 2 directories with 2 updates

[dependabot]

Bumps the npm group with 1 update in the /example directory: aws-cdk.
Bumps the npm group with 1 update in the /package directory: @aws-lambda-powertools/logger.

Updates aws-cdk from 2.1137.0 to 2.1138.0

Release notes

Sourced from aws-cdk's releases.

aws-cdk@v2.1138.0

2.1138.0 (2026-08-19)

Features

• cli: add "errors-only" progress mode that only prints errors (#1800) (a4c0282)
• cli: support notification-arns in cdk import (#1740) (f8e7da1), closes aws/aws-cdk#23548

Bug Fixes

• cli: cdk context header always claims the context was found in cdk.json (#1816) (b7783b5), closes #1814
• cli: cdk flags --set leaks synthesized cloud assembly directories (#1833) (fd891fb), closes #1832
• cli: fail fast when --proxy has no or an unsupported protocol (#1843) (da37001), closes #453
• cli: refactor fails on stacks with bundled assets (#1812) (8458a4a), closes #1810
• cli: reject non-numeric ids in cdk acknowledge (#1844) (c71ab23), closes #248

Commits

• a4c0282 feat(cli): add "errors-only" progress mode that only prints errors (#1800)
• 8458a4a fix(cli): refactor fails on stacks with bundled assets (#1812)
• fd891fb fix(cli): cdk flags --set leaks synthesized cloud assembly directories (#1833)
• f8e7da1 feat(cli): support notification-arns in cdk import (#1740)
• da37001 fix(cli): fail fast when --proxy has no or an unsupported protocol (#1843)
• bcc0f2b chore(deps): upgrade dependencies (#1841)
• b7783b5 fix(cli): cdk context header always claims the context was found in cdk.json ...
• c71ab23 fix(cli): reject non-numeric ids in cdk acknowledge (#1844)
• See full diff in compare view

Updates @aws-lambda-powertools/logger from 2.34.0 to 2.35.0

Release notes

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

v2.35.0

Summary

In this release, the Parameters utility gains support for the AWS AppConfig Agent Lambda extension. A new getConfig function fetches application configurations from the agent's local HTTP endpoint, without the AWS SDK and without a cache to manage, since caching, polling, and prefetching are all handled by the agent.

In Logger, the log buffer and the debug sampling log level are now scoped per invocation under Lambda Managed Instances concurrency, so concurrent invocations no longer clear each other's buffered logs or override each other's sampling decision. Logger also now accepts IANA timezone aliases such as Asia/Kolkata in the TZ environment variable, which were previously rejected and produced timestamps for the wrong instant. When a timezone can't be resolved at all, Logger now falls back to UTC consistently and emits a warning, instead of doing so silently.

The Parser utility adds a schema for Amazon Connect Outbound Campaigns custom action events.

Finally, the documentation site has been restyled to match the AWS Developer Guide.

[!IMPORTANT] The project's Discord server has been shut down. Community conversations now happen in GitHub Discussions, and all Discord links in the READMEs, docs, and issue templates now point there.

⭐ Congratulations to @​leiwilson for their first PR merged in the project 🎉

AppConfig Agent support

If you use the AWS AppConfig Agent Lambda extension, you can now fetch application configurations from the agent's local HTTP endpoint with getConfig:

import { getConfig } from '@aws-lambda-powertools/parameters/appconfig-agent';
const config = await getConfig('my-configuration', {
environment: 'my-env',
application: 'my-app',
transform: 'json',
});
export const handler = async (): Promise<void> => {
console.log(config);
};

A few things to know:

• You must add the AppConfig Agent Lambda extension layer to your function. getConfig talks to it over the agent's local endpoint, so it doesn't need the AWS SDK.
• Because the agent handles caching, polling, and prefetching, the maxAge and forceFetch options don't apply. You can reduce cold start latency by setting AWS_APPCONFIG_EXTENSION_PREFETCH_LIST so the agent fetches your configuration before your handler runs.
• When the configuration doesn't exist, getConfig returns undefined, so you can fall back with ??, or set throwOnMissing to get a ParameterNotFoundError instead. Any other failure to reach the agent throws a GetParameterError.
• Outside of Lambda, or when POWERTOOLS_DEV is enabled, getConfig returns undefined without making a request, so your tests never need to mock the agent. Set POWERTOOLS_APPCONFIG_AGENT_RETURN_VALUE when you want it to return a value instead.

Changes

• refactor(logger): isolate log level InvokeStore access in a store (#5548) by @​vishwakt
• fix(logger): scope log buffer per invocation under LMI concurrency (#5543) by @​vishwakt
• fix(logger): scope debug sampling log level per invocation under LMI concurrency (#5544) by @​vishwakt
• chore(ci): remove boring-cyborg and semantic config files (#5535) by @​dreamorosi
• chore(ci): remove greetings now handled by oss-automation (#5532) by @​dreamorosi
• chore: replace Discord server with GitHub Discussions (#5530) by @​dreamorosi
• docs: restyle documentation to match AWS Developer Guide (#5426) by @​dreamorosi

... (truncated)

Changelog

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

2.35.0 (2026-08-18)

Improvements

• logger isolate log level InvokeStore access in a store (#5548) (a47c7a6)

Bug Fixes

• logger scope log buffer per invocation under LMI concurrency (#5543) (0d4071b)
• logger scope debug sampling log level per invocation under LMI concurrency (#5544) (1b4b013)
• logger accept resolvable IANA timezone aliases in timestamps (#5458) (4cdc936)

Features

• parameters add support for AppConfig Agent (#5399) (f1deacc)
• parser add schema for Amazon Connect Outbound Campaigns (#5502) (30d7beb)

Commits

• 7bcc27b chore(ci): bump version to 2.35.0 (#5563)
• 66e901c chore(deps): bump the aws-cdk group across 1 directory with 3 updates (#5524)
• 6bd97ae chore(deps-dev): bump @​valkey/valkey-glide from 2.5.0 to 2.5.1 (#5559)
• f100ced chore(deps): bump the codeql-action group across 1 directory with 3 updates (...
• b681b94 chore(deps-dev): bump @​biomejs/biome from 2.5.7 to 2.5.8 (#5560)
• 97581fd chore(deps-dev): bump @​redis/client from 6.2.0 to 6.2.1 (#5558)
• 4742290 chore(deps): bump the aws-sdk-v3 group across 1 directory with 48 updates (#5...
• 6c96925 chore(deps-dev): bump protobufjs from 8.7.1 to 8.7.2 (#5551)
• 347f60f chore(deps): bump esbuild from 0.28.1 to 0.28.2 (#5552)
• a47c7a6 refactor(logger): isolate log level InvokeStore access in a store (#5548)
• 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 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

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/aws-cdk	2.1138.0	Unknown	Unknown
npm/@aws-lambda-powertools/logger	2.35.0	🟢 8.9	Details Check Score Reason Security-Policy 🟢 10 security policy file detected Code-Review 🟢 10 all changesets reviewed Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Pinned-Dependencies 🟢 10 all dependencies are pinned Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices 🟢 5 badge detected: Passing License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Packaging 🟢 10 packaging workflow detected Vulnerabilities ⚠️ 0 11 existing vulnerabilities detected Fuzzing 🟢 10 project is fuzzed SAST 🟢 10 SAST tool is run on all commits Branch-Protection 🟢 8 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 11 contributing companies or organizations

Scanned Files

• example/package.json
• package/package.json