-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws-lambda: Invalid principal type for Lambda permission statement: CompositePrincipal. #27503
Comments
@peterwoodworth I'll take this. |
@AlJohri This currently isn't supported but you can do this:
@peterwoodworth Is this functionality we want to add? |
I don't see why not @msambol, feel free to take |
@peterwoodworth I don't think it makes sense to change |
Hey @msambol, could you tell me why did you not go for accommodating this in |
@vinayak-kukreja I think it would require updating the function declaration? At the very least the return type. So I thought best to create a new method. I'm open to suggestions though if you think we can do it better. |
Hey @msambol , I agree, thank you for the clarification. |
Add ability to grant function access to `CompositePrincipal`. Closes #27503. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the bug
I am getting an error when trying to use a CompositePrincipal to
grantInvoke
permissions on a lambda.Expected Behavior
I expect it to work and allow all of the account principals to invoke the lambda.
Current Behavior
Currently it errors out and says it is unsupported with the following error:
Reproduction Steps
This code results in the error:
Possible Solution
No response
Additional Information/Context
Possibly related:
CDK CLI Version
2.95.0 (build cfa7e88)
Framework Version
No response
Node.js Version
v18.17.1
OS
macOS Sonoma
Language
TypeScript
Language Version
TypeScript 5.2
Other information
No response
The text was updated successfully, but these errors were encountered: