feat(lambda): add logGroup and systemLogLevel to CapacityProvider - #38183
Merged
mergify[bot] merged 8 commits intoJul 22, 2026
Conversation
Adds TelemetryConfig support to the CapacityProvider L2 construct. Customers can specify a log group and system log level for scaling activity logs. The construct wraps these into the CFN TelemetryConfig.LoggingConfig property.
github-actions
Bot
added
beginning-contributor
reedham-aws
approved these changes
Jun 22, 2026
abidhasan-aws
previously requested changes
Jul 13, 2026
abidhasan-aws
left a comment
abidhasan-aws
left a comment
Collaborator
There was a problem hiding this comment.
Hi @vicheey,
Thanks for the PR :)
Left a tiny comment!
mergify
Bot
dismissed
abidhasan-aws’s stale review
July 14, 2026 15:44
Pull request has been modified.
Collaborator
|
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing To prevent automatic closure:
This PR will automatically close in 14 days if no action is taken. |
licjun
reviewed
Jul 15, 2026
licjun
reviewed
Jul 15, 2026
- Migrate logGroup prop from ILogGroup to ILogGroupRef (awslint prefer-ref-interface) - Access log group name via logGroupRef.logGroupName - Add logGroup to integration test for deployment verification - Add logGroup to README CapacityProvider example and props table - Regenerate integ test snapshots
licjun
approved these changes
Jul 21, 2026
abidhasan-aws
added
the
pr/needs-integration-tests-deployment
abidhasan-aws
temporarily deployed
to
deployment-integ-test
July 22, 2026 13:30 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
abidhasan-aws
approved these changes
Jul 22, 2026
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Contributor
Merge Queue Status
This pull request spent 17 seconds in the queue, including 3 seconds running CI. Required conditions to merge
|
Contributor
|
Comments on closed issues and PRs are hard for our team to see. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Issue # (if applicable)
Closes #38182.
Reason for this change
Lambda CapacityProvider now supports
TelemetryConfigin CloudFormation, enabling customers to configure system logging for scaling activity. The L1CfnCapacityProvideralready hastelemetryConfig, but there is no L2 support.Description of changes
Added
logGroupandsystemLogLevelprops toCapacityProviderProps, matching how the Function L2 exposes logging as flat props rather than a nested interface.logGroup?: logs.ILogGroup— CloudWatch log group for system logssystemLogLevel?: SystemLogLevel— log verbosity (DEBUG, INFO, WARN)The construct conditionally renders
telemetryConfig.loggingConfigon the L1 resource only when at least one prop is specified. When neither is provided,TelemetryConfigis absent from the CFN output (service applies defaults).Reuses the existing
SystemLogLevelenum from the Function construct.Describe any new or updated permissions being added
No new permissions. Log delivery permissions are already included in the
AWSLambdaManagedEC2ResourceOperatormanaged policy that the operator role uses.Description of how you validated changes
integ.capacity-provider-all-fields) withsystemLogLevel: DEBUGChecklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license