chrisbonifacio
commented
1 week ago Hi @gpavlov2016 can you try changing your mutations handler from custom to function?
ex:
const schema = a.schema({
Impression: a
.model({
videoId: a.string().required(),
impressions: a.integer().default(0),
})
.identifier(["videoId"])
.authorization((allow) => [allow.publicApiKey(), allow.authenticated()]),
//Executes atomic increment operation on the impressions field of the Impression model
increaseImpression: a
.mutation()
.arguments({
videoId: a.string(),
count: a.integer(),
})
.returns(a.ref("Impression"))
.authorization((allow) => [allow.authenticated()])
.handler(a.handler.function(incrementImpression)),
});Mutation performed from the AppSync console with IAM:
gpavlov2016
Before opening, please confirm:
JavaScript Framework
Next.js
Amplify APIs
GraphQL API
Amplify Version
v6
Amplify Categories
No response
Backend
Amplify Gen 2 (Preview)
Environment information
Describe the bug
Consider the use case in which a lambda function needs to use a custom mutation. Before v6.2 we could use
allow.authenticated('iam'), however since the upgrade to v6.2 it doesn't work anymore. Neither does the.authorization((allow) => [ allow.resource(...) ])applied to the whole schema, this only works for non-custom queries and mutations.Expected behavior
An authorization mechanism to authorize a lambda function to execute a custom mutation should exist
Reproduction steps
Define the schema:
Define a function:
This results in the following error:
Same problem can be seen by running the mutation from the AppSync console:
Unless the schema is manually edited and the
@aws_iamis added to theincreaseImpressiondeclaration - then it works!Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response