aws-amplify / aws-amplify/amplify-cli
Reduce number of roles?
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Is this feature request related to a new or existing Amplify category?
api
### Is this related to another service?
_No response_
### Describe the feature you'd like to request
I notice that Amplify creates a lot of roles. My project has already 50 roles. Amplify creates for example a role per function and per graph table with IAM. If we should deploy the app to multiple domains/environments then we could hit the limit of 1000 roles (expandable by request to 5000).
### Describe the solution you'd like
For GraphQL API I can not see the need for a role per table with IAM auth. There should be possible to have a common role with a resource array with each table arn?
Function roles is more tricky, but I think you should see if there is possible to combine them?
### Describe alternatives you've considered
Common role for API with tables with IAM
### Additional context
_No response_
### Is this something that you'd be interested in working on?
- [ ] 👋 I may be able to implement this feature request
### Would this feature include a breaking change?
- [ ] ⚠️ This feature might incur a breaking change
Contributor guide
Research direction
The issue concerns Amplify CLI role generation for GraphQL API tables and functions, but it names no files, tests, or entry points. Start by locating the code that creates those IAM roles and determine whether shared roles preserve each resource's permissions; done means reducing role count without changing required access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, typescript
- Domain
- api, authorization, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100