Skip to content

fix: Construct Hub fails with CDK v2.268.0 and higher - #1924

Merged
cdklabs-automation merged 2 commits into
mainfrom
huijbers/remove-layer
Sep 8, 2026
Merged

cdklabs-automation merged 2 commits into
mainfrom
huijbers/remove-layer

Conversation

@rix0rrr

@rix0rrr rix0rrr commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

In aws/aws-cdk#37174, the architecture of S3BucketDeployment was switched to arm64.

In ConstructHub, we add in the Lambda Insights Extension Layer, but the version we added was for x86. This means the S3BucketDeployment Lambda now fails to start up.

Since there is no easy way for the construct to pick the correct ARN to automatically switch between x86 and ARM depending on the architecture of the Lambda, and wholesale switching to ARM will break consumers that are on an old version of aws-cdk-lib where the platform is still x86, we opt for the next best solution: remove the layer altogether.

When it was introduced it was stated that it was in order to track memory consumption. Since nothing much is changing here and the memory is already 512 MB, seems safe enough to remove this if and until we see problems with the custom resource again.


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

@rix0rrr
rix0rrr requested a review from a team September 8, 2026 10:47
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

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

Scanned Files

None

In aws/aws-cdk#37174, the architecture
of `S3BucketDeployment` was switched to `arm64`.

In ConstructHub, we add in the [Lambda Insights Extension
Layer](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Lambda-Insights-extension-versions.html),
but the version we added was for x86. This means the S3BucketDeployment
Lambda now fails to start up.

Since there is no easy way for the construct to pick the correct ARN to
automatically switch between x86 and ARM depending on the architecture
of the Lambda, and wholesale switching to ARM will break consumers that
are on an old version of `aws-cdk-lib` where the platform is still x86,
we opt for the next best solution: remove the layer altogether.

When it was introduced it was stated that it was in order to track memory
consumption. Since nothing much is changing here and the memory is
already 512 MB, seems safe enough to remove this if and until we see
problems with the custom resource again.
@rix0rrr
rix0rrr force-pushed the huijbers/remove-layer branch from dd0daf3 to 78961db Compare September 8, 2026 10:49
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@cdklabs-automation
cdklabs-automation added this pull request to the merge queue Sep 8, 2026
Merged via the queue into main with commit fa6b306 Sep 8, 2026
8 checks passed
@cdklabs-automation
cdklabs-automation deleted the huijbers/remove-layer branch September 8, 2026 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants