-
Notifications
You must be signed in to change notification settings - Fork 77
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
Custom mutation not accessible with IAM #2837
Comments
Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂 |
Hi @VincentvdE, Apologies for the delay. Thanks for bringing this up. We’re able to reproduce the issue by following the steps outlined in the description, so we’re marking it as a bug for the team to investigate further. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Reopening pending release of fix |
We have released this in @aws-amplify/[email protected], @aws-amplify/[email protected]. Update your project dependencies with an |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Environment information
Describe the bug
A custom mutation ("increment") is not accessible by a Lambda function. Upon checking the generated schema in AppSync, the mutation is missing the @aws_iam directive, which is likely causing the access issue.
Reproduction steps
amplify/data/resource.ts:
amplify/data/increment.js
The generated schema looks like this:
The increment is missing the "@aws_iam". After manually adding it, it works. Shouldn't the
.authorization((allow) => [allow.resource(postConfirmation)]);
add that?The text was updated successfully, but these errors were encountered: