You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that I want to be able to call from a GitHub action. So far I've been able to set up permissions that allow the IAM account to call that mutation, but I'm getting this error:
I use this on another API I have and get no issue when making calls to it using IAM.
I tested running the action with a full admin access policy attached to the IAM user but it was still denied, so it seems like the API is returning that permission denied error rather than it being a problem with the policy.
It's strange that no error is returned when using getTenantByTenantName, which is just a queryField added to an index, but the registerTenant which is a custom function throws that error.
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
16
Amplify CLI Version
12.10.1
What operating system are you using?
linux
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I have a mutation query in my schema:
that I want to be able to call from a GitHub action. So far I've been able to set up permissions that allow the IAM account to call that mutation, but I'm getting this error:
{ errorType: 'UnauthorizedException', message: 'Permission denied' }
This is the policy I'm using for AppSync:
It seems like it can call the getTenantByTenantName query fine, but gets that error on the registerTenant call.
in
amplify/backend/api/platelet/custom-roles.json
I have the following (with my proper id):I use this on another API I have and get no issue when making calls to it using IAM.
I tested running the action with a full admin access policy attached to the IAM user but it was still denied, so it seems like the API is returning that permission denied error rather than it being a problem with the policy.
It's strange that no error is returned when using getTenantByTenantName, which is just a queryField added to an index, but the registerTenant which is a custom function throws that error.
Expected behavior
I expect the query to complete without a permission denied error.
Reproduction steps
This is the code I use in the GitHub action:
Project Identifier
f97b80f7ee5ceef2a72f107f35e6d453
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: