- Newest
- Most votes
- Most comments
Hello, Based on the scenario that you have outlined, It seems that you have IAM authorization configured on the User model like
@auth(rules: [{ allow: private, provider: iam }])
In this case, IAM-based @auth rules are scoped down to only work with Amplify-generated IAM roles. To allow-list a custom role (for e.g. PreSignUp Lambda trigger's execution role), you'd need to update the existing or create amplify/backend/api/<your-api-name>/custom-roles.json
and include the custom role name. Kindly ensure that you push the changes to the backend once you have updated the custom-roles.json
. Please find the reference documentation for the same here.
Having said that, if you are still facing the challenges, please feel free to reach out to us via Support Center with the resources information like schema.graphql
, local amplify
folder contents, code snippets of Lambda function that are making these requests.
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago