sid88in / sid88in/serverless-appsync-plugin
A recommended way to split up large APIs?
@AlexHladin is already working on this.
Since May 31, 2026.
- Dominant language
- TypeScript
- Stars
- 955
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
Hey, how'd doing? We have upgraded to the new major for some times now, and it's working great until now.
In a recent move, we ported 400 Lambda resolvers into APPSYNC_JS resolvers to avoid cold starts. We subsequently hit a CloudFormation limit of 2500 resource updates per stack operation because pipeline resolvers means 3x more resources count than Direct Lambda.
An extraction of the relevant error message below:
Embedded stack [redacted] was not successfully created: Limit on the number of resources in a single stack operation exceeded
Our AWS support ticket and a related GitHub issue suggests splitting it into multiple batches of UpdateStack actions.
Without a way to specify an existing AppSync API in v2, what would you think is the best way to resolve our issue?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.