feat(cloudfront-origins): use dual-stack ip address type by default for lambda function url origin (under feature flag)#35754
Open
badmintoncryer wants to merge 36 commits intoaws:mainfrom
Conversation
github-actions
bot
added
effort/medium
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
aws-cdk-automation
previously requested changes
Oct 15, 2025
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
aws-cdk-automation
dismissed
their stale review
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
mazyu36
suggested changes
Feb 11, 2026
Contributor
mazyu36
left a comment
mazyu36
left a comment
There was a problem hiding this comment.
LGTM overall.
Could you please address the failing CI checks?
…ns-dualstack-default-35450
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
…igins to dual-stack connectivity
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
aws-cdk-automation
removed
the
pr/needs-community-review
aws-cdk-automation
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
Contributor
Author
|
@mazyu36 Thanks always! I've fixed CI failure. |
Collaborator
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
4 similar comments
Collaborator
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
Collaborator
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
Collaborator
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
Collaborator
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
…ns-dualstack-default-35450
badmintoncryer
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
aws-cdk-automation
added
the
pr/needs-maintainer-review
aws-cdk-automation
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
…ns-dualstack-default-35450
badmintoncryer
temporarily deployed
to
automation
GitHub Actions
Inactive
badmintoncryer
temporarily deployed
to
automation
GitHub Actions
Inactive
badmintoncryer
requested a deployment
to
test-pipeline
GitHub Actions
Waiting
badmintoncryer
temporarily deployed
to
automation
GitHub Actions
Inactive
badmintoncryer
temporarily deployed
to
automation
GitHub Actions
Inactive
badmintoncryer
requested a deployment
to
test-pipeline
GitHub Actions
Waiting
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
3 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 #35450.
Reason for this change
CloudFront recently launched support for IPv6 origins.
Lambda function URL's are by default dual stack.
It is better to update default behavior of IP address type settings from IPV4 to Dualstack.
Description of changes
@aws-cdk/aws-cloudfront-origins:functionUrlOriginDualStackDefaultDescribe any new or updated permissions being added
None
Description of how you validated changes
Add both unit and integ tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license