feat(parameters): add support for AppConfig Agent - #5399
Merged
Conversation
svozza
force-pushed
the
feat/parameters-appconfig-agent
branch
from
July 7, 2026 12:17
5d0bfe0 to
ba6478b
Compare
svozza
marked this pull request as draft
July 7, 2026 12:26
…rtools/powertools-lambda-typescript into feat/parameters-appconfig-agent
Contributor
Author
svozza
commented
Jul 8, 2026
2 tasks
dreamorosi
reviewed
Jul 13, 2026
…rtools/powertools-lambda-typescript into feat/parameters-appconfig-agent
|
…rtools/powertools-lambda-typescript into feat/parameters-appconfig-agent
dreamorosi
approved these changes
Jul 15, 2026
Contributor
|
Thanks for working on this - and glad we were able to smooth out the non-Lambda experience. |
Contributor
Author
|
Yeah, the non-lambda part was trickier than I expected but I think we landed on a nice solution in the end. Thank you for helping iterate on the design! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Adds a new
getConfigfunction exported from@aws-lambda-powertools/parameters/appconfig-agentthat retrieves configurations from the AWS AppConfig Agent Lambda extension's local HTTP endpoint. Since caching, polling, and prefetching are handled by the agent, the implementation is a lean standalone function modeled on the commonsmetadatamodule rather than theBaseProviderpattern, keeping customer bundles small.Changes
getConfigfunction inpackages/parameters/src/appconfig-agent/that fetches fromhttp://localhost:2772/applications/{app}/environments/{env}/configurations/{config}using nativefetchwith a configurable timeout (default 3000ms)jsonandbinarytransforms by reusing the existingtransformValueutility; nomaxAge/forceFetchoptions since caching is handled by the agentundefinedwhen not running in a Lambda environment (local development/testing)AWS_APPCONFIG_EXTENSION_HTTP_PORTenvironment variable and fall back toPOWERTOOLS_SERVICE_NAMEwhenapplicationis not provided./appconfig-agentand./appconfig-agent/typessubpath exports with typed return values (string,JSONValue, or explicit generic)Issue number: closes #5312
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.