chore(lambda): fix integration tests #36938

aemada-aws · 2026-02-10T22:24:05Z

Issue # (if applicable)

N/A - Remediation of 8 failing aws-lambda integration tests.

Reason for this change

Eight aws-lambda integration tests were failing due to a combination of issues: hardcoded physical names causing collisions, a non-existent IAM managed policy reference, an unsupported EC2 instance type for Lambda CapacityProvider, regional availability constraints for AWS::Lambda::CapacityProvider, API response size exceeding CloudFormation custom resource limits, a corrupt test asset (handler.zip), and the Lambda runtime SDK (3.895.0) not yet including capacity provider APIs (introduced in SDK 3.942.0).

Description of changes

integ.capacity-provider-all-fields.ts:

Removed hardcoded capacityProviderName to avoid name collisions
Fixed managed policy from AmazonLambdaCapacityProviderOperatorRolePolicy (does not exist) to AWSLambdaManagedEC2ResourceOperator
Changed instance type from t2.micro to m5.large (t2.micro not supported by Lambda CapacityProvider for x86_64)
Added region constraint (10 regions where AWS::Lambda::CapacityProvider is available)
Commented out GetCapacityProvider assertions (runtime SDK too old)

integ.capacity-provider-defaults.ts:

Added region constraint
Commented out GetCapacityProvider assertions (runtime SDK too old)

integ.function-capacity-provider-all-fields.ts:

Set @aws-cdk/aws-lambda:useCdkManagedLogGroup: false to avoid race condition where Lambda auto-creates the log group before CloudFormation can create the explicit AWS::Logs::LogGroup resource
Added outputPaths to GetFunction API call to stay within 4KB custom resource response limit
Added region constraint
Commented out capacity-provider-specific assertions (runtime SDK too old)

integ.function-capacity-provider-minimal.ts:

Same LogGroup race condition fix
Same outputPaths fix
Added region constraint
Commented out capacity-provider-specific assertions (runtime SDK too old)

integ.version-scaling-config-all-fields.ts:

Same LogGroup race condition fix
Changed version.functionArn to fn.functionName for listVersionsByFunction (API rejects version-qualified ARNs)
Added region constraint
Commented out FunctionScalingConfig assertions (runtime SDK too old)

integ.lambda-sourceKMSKeyArn.ts:

Removed hardcoded bucketName: 's3sourcekmskeyarnbucket' to avoid global name collisions

integ.assets.file.ts:

No code changes; recreated corrupt handler.zip (was truncated to 313 bytes)

integ.durable-config.ts:

No changes needed; passes as-is

Why assertions are commented out:
The integ-test assertion Lambda runs on nodejs22.x, which ships with AWS SDK 3.895.0. The Lambda capacity provider APIs (GetCapacityProviderCommand, CapacityProviderConfig in GetFunction, FunctionScalingConfig in listVersionsByFunction) were introduced in SDK 3.942.0. The runtime SDK strips these fields from responses. Assertions are preserved as commented code with TODO markers and can be uncommented when the runtime SDK is updated. See runtime SDK version docs.

Describe any new or updated permissions being added

No new permissions. The managed policy fix corrects AmazonLambdaCapacityProviderOperatorRolePolicy (non-existent) to AWSLambdaManagedEC2ResourceOperator (the actual AWS managed policy for Lambda capacity provider operator roles).

Description of how you validated changes

All 8 integration tests were deployed and validated via integ-runner with --update-on-failed across multiple parallel regions:

yarn integ \
  test/aws-lambda/test/integ.assets.file.js \
  test/aws-lambda/test/integ.capacity-provider-all-fields.js \
  test/aws-lambda/test/integ.capacity-provider-defaults.js \
  test/aws-lambda/test/integ.durable-config.js \
  test/aws-lambda/test/integ.function-capacity-provider-all-fields.js \
  test/aws-lambda/test/integ.function-capacity-provider-minimal.js \
  test/aws-lambda/test/integ.lambda-sourceKMSKeyArn.js \
  test/aws-lambda/test/integ.version-scaling-config-all-fields.js \
  --disable-update-workflow \
  --update-on-failed \
  --parallel-regions us-east-1 us-east-2 us-west-2 eu-west-1 eu-central-1 eu-north-1 ap-south-1 ap-southeast-1 ap-southeast-2 ap-northeast-1

All 8 tests pass. Snapshots updated via integ-runner only.

Checklist

My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Fix integration test failures for aws-lambda capacity provider, durable config, sourceKMSKeyArn, version scaling, and assets tests. Fixes include removing hardcoded physical names, correcting managed policy references, adding region constraints for CapacityProvider availability, fixing response size limits, resolving LogGroup race conditions, and recreating a corrupt test asset.

aws-cdk-automation

(This review is outdated)

github-actions · 2026-02-10T22:26:33Z

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	288 ran	288 passed

Test	Result
No test annotations available

View Security Guardian Results

github-actions · 2026-02-10T22:26:36Z

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	288 ran	288 passed

Test	Result
No test annotations available

View Security Guardian Results with resolved templates

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

kumvprat · 2026-02-11T13:53:19Z

.../@aws-cdk-testing/framework-integ/test/aws-lambda/test/integ.capacity-provider-all-fields.ts

-  },
-}));
+// TODO: Uncomment when the Lambda runtime SDK is updated to >= 3.942.0.
+// The nodejs22.x Lambda runtime currently ships SDK 3.895.0, which does not


Is it feasible to have the test setup work with node 20.x? Or are the assertion checks deployed on node 22.x and that is causing the limitations ?

I think if we dont want this code we can remove it completely as it's not useful to test that CFN template is passing the correct config to Lambda(outside of cdk scope)

The limitation is that the latest Node.js lambda (22) does not come the SDK with the new Lambda APIs. The integ test assertions lambda uses node js 22.

We can keep the assertions for future reference for when the SDK is updated.

kumvprat · 2026-02-11T13:53:38Z

...es/@aws-cdk-testing/framework-integ/test/aws-lambda/test/integ.capacity-provider-defaults.ts

-    SecurityGroupIds: [securityGroup.securityGroupId],
-  },
-}));
+// TODO: Uncomment when the Lambda runtime SDK is updated to >= 3.942.0.


Same comment as the above test case

kumvprat · 2026-02-11T13:54:01Z

...-testing/framework-integ/test/aws-lambda/test/integ.function-capacity-provider-all-fields.ts

+getFunction.assertAtPath('Configuration.State', integ.ExpectedResult.stringLikeRegexp('Active'));
+
+// TODO: Uncomment when the Lambda runtime SDK is updated to >= 3.942.0.
+// The nodejs22.x Lambda runtime currently ships SDK 3.895.0, which strips


Same comment as above test case

kumvprat · 2026-02-11T13:54:15Z

...cdk-testing/framework-integ/test/aws-lambda/test/integ.function-capacity-provider-minimal.ts

+getFunction.assertAtPath('Configuration.State', integ.ExpectedResult.stringLikeRegexp('Active'));
+
+// TODO: Uncomment when the Lambda runtime SDK is updated to >= 3.942.0.
+// The nodejs22.x Lambda runtime currently ships SDK 3.895.0, which strips


Same as above test case

kumvprat · 2026-02-11T13:54:54Z

...-cdk-testing/framework-integ/test/aws-lambda/test/integ.version-scaling-config-all-fields.ts


-const version = fn.currentVersion;
+// Access currentVersion to trigger Version resource creation with scaling config
+fn.currentVersion;


Why do we keep this line ?
If we are not assigning it or using it then we can totally remove it

It is a lazy initialiser, accessing it creates the version if none exist.

But isn't there a better way to do this, like asserting on the version ?
There seems to be an older version to the sdk command : https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/lambda/command/ListVersionsByFunctionCommand/

Maybe we can use that in our assertions?

kumvprat · 2026-02-11T13:55:04Z

...-cdk-testing/framework-integ/test/aws-lambda/test/integ.version-scaling-config-all-fields.ts

-  ],
-}));
+// TODO: Uncomment when the Lambda runtime SDK is updated to >= 3.942.0.
+// The nodejs22.x Lambda runtime currently ships SDK 3.895.0, which does not


Same comment as above test cases

Remove commented assertions that were waiting for Lambda runtime SDK >= 3.942.0. These assertions cannot be tested with the current nodejs22.x runtime (SDK 3.895.0) and are not needed for the integration tests to pass.

aws-cdk-automation requested a review from a team February 10, 2026 22:24

github-actions bot added the p2 label Feb 10, 2026

mergify bot added the contribution/core This is a PR that came from AWS. label Feb 10, 2026

aemada-aws force-pushed the fix/lambda-integ-tests-remediation branch from a74f4dd to e1d0bd7 Compare February 10, 2026 22:25

aws-cdk-automation previously requested changes Feb 10, 2026

View reviewed changes

aemada-aws changed the title ~~fix(aws-lambda): remediate 8 integration tests~~ chore(lambda): fix integration tests Feb 10, 2026

aemada-aws marked this pull request as ready for review February 11, 2026 09:23

aemada-aws added the pr/needs-integration-tests-deployment Requires the PR to deploy the integration test snapshots. label Feb 11, 2026

aemada-aws had a problem deploying to deployment-integ-test February 11, 2026 09:23 — with GitHub Actions Error

aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Feb 11, 2026

aws-cdk-automation deployed to deployment-integ-test February 11, 2026 09:25 — with GitHub Actions Active

kumvprat reviewed Feb 11, 2026

View reviewed changes

aemada-aws had a problem deploying to deployment-integ-test February 11, 2026 14:41 — with GitHub Actions Error

aemada-aws force-pushed the fix/lambda-integ-tests-remediation branch from b3ef1cc to 3c1dd06 Compare February 11, 2026 14:48

aemada-aws had a problem deploying to deployment-integ-test February 11, 2026 14:48 — with GitHub Actions Error

aemada-aws force-pushed the fix/lambda-integ-tests-remediation branch from 3c1dd06 to 7102132 Compare February 11, 2026 14:56

aemada-aws had a problem deploying to deployment-integ-test February 11, 2026 14:56 — with GitHub Actions Error

chore(lambda): remove commented out assertions from integ tests

556b46a

Remove commented assertions that were waiting for Lambda runtime SDK >= 3.942.0. These assertions cannot be tested with the current nodejs22.x runtime (SDK 3.895.0) and are not needed for the integration tests to pass.

aemada-aws force-pushed the fix/lambda-integ-tests-remediation branch from 7102132 to 556b46a Compare February 11, 2026 15:03

aemada-aws requested a deployment to deployment-integ-test February 11, 2026 15:04 — with GitHub Actions Queued

kumvprat approved these changes Feb 11, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(lambda): fix integration tests #36938

chore(lambda): fix integration tests #36938

aemada-aws commented Feb 10, 2026 •

edited

Loading

Uh oh!

aws-cdk-automation left a comment •

edited

Loading

Uh oh!

github-actions bot commented Feb 10, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Feb 10, 2026 •

edited

Loading

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

aemada-aws Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

aemada-aws Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

kumvprat Feb 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

chore(lambda): fix integration tests #36938

Are you sure you want to change the base?

chore(lambda): fix integration tests #36938

Conversation

aemada-aws commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue # (if applicable)

Reason for this change

Description of changes

Describe any new or updated permissions being added

Description of how you validated changes

Checklist

Uh oh!

aws-cdk-automation left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

aemada-aws commented Feb 10, 2026 •

edited

Loading

aws-cdk-automation left a comment •

edited

Loading

github-actions bot commented Feb 10, 2026 •

edited

Loading

github-actions bot commented Feb 10, 2026 •

edited

Loading