Skip to content

Conversation

eliasbrange
Copy link
Contributor

Issue # (if applicable)

Closes #35696.

Reason for this change

Added support for specifying the role to use to invoke an authorizer.

Description of changes

Added an optional role: iam.IRole to relevant interfaces and passing it down to the L1 construct.

Description of how you validated changes

Added unit tests and updated the integration test.

Checklist


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

@aws-cdk-automation aws-cdk-automation requested a review from a team October 9, 2025 07:54
@github-actions github-actions bot added beginning-contributor [Pilot] contributed between 0-2 PRs to the CDK feature-request A feature should be added or improved. p2 labels Oct 9, 2025
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This review is outdated)

@eliasbrange eliasbrange force-pushed the feat/api-gateway-authorizer-role branch from 328e4b9 to e44073f Compare October 9, 2025 08:53
@eliasbrange eliasbrange force-pushed the feat/api-gateway-authorizer-role branch from e44073f to 2e73226 Compare October 9, 2025 09:01
@aws-cdk-automation aws-cdk-automation dismissed their stale review October 9, 2025 09:03

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

beginning-contributor [Pilot] contributed between 0-2 PRs to the CDK feature-request A feature should be added or improved. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(apigatewayv2): Support cross-account Lambda Authorizers

2 participants