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
Hi! I am not sure if this feature is missing or just not found in docs, but I think it would be very useful if we could define different "authorized" objects - one for UserPool and one for IAM. The idea is to add to the default userpool (front end users) a possibility to define multiple rules for IAM roles (backend services not necessarily related to Amplify)
Describe the solution you'd like
const schema = a
.schema({
Todo: a
.model({
content: a.string(),
})
.authorization((allow) => [
allow.authenticated(),
// plus IAM
allow.iamRoles([env.COPIER_SERVICE_IAM_ROLES]).to(["read"]),
allow.iamRoles([env.UPDATER_SERVICE_IAM_ROLES]).to(["read", "write"]),
]),
Describe alternatives you've considered
Considered altering CF resources, but not sure where to change and what.
Additional context
No response
Is this something that you'd be interested in working on?
👋 I may be able to implement this feature request
⚠️ This feature might incur a breaking change
The text was updated successfully, but these errors were encountered:
Is this related to a new or existing framework?
Next.js
Is this related to a new or existing API?
Authentication
Is this related to another service?
No response
Describe the feature you'd like to request
Hi! I am not sure if this feature is missing or just not found in docs, but I think it would be very useful if we could define different "authorized" objects - one for UserPool and one for IAM. The idea is to add to the default userpool (front end users) a possibility to define multiple rules for IAM roles (backend services not necessarily related to Amplify)
Describe the solution you'd like
Describe alternatives you've considered
Considered altering CF resources, but not sure where to change and what.
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: