Hello,

I am wondering if anyone can help me out. I have come across the 500 resource limit, and I am trying to use the serverless plugin split stacks to try and split my current stack into multiple stacks to try and get around this limit.

At current we have a single serverless.yaml file at root which points to all functions, as well as s3, sns topics etc.

I have a simple configuration of:

"
splitStacks:
perType: true
perGroupFunction: false
stackConcurrency: 10
resourceConcurrency: 20
nestedStackCount: 50
categories:
- AWS::ApiGateway::Method
- AWS::Lambda::Function
- AWS::S3::Bucket
"

I am not sure if I am using the plugin correctly. I have tried creating more categories, played around with setting perFunction to true, etc. When I run serverless package it might show various stacks being created per lambda, taking root resources down to 70 in one such configuration.

However, when I try to deploy the service again, it will revert to a cloudformation with 1-3 stacks, and 500 resources at root. I am wondering what may be the solution here, as it seems that whatever configuration I make it will return to 500 resources.

There are about 100 lambda endpoints, various sns topics, an s3 bucket, persmissions, etc. all in this main service. Is it feasible to use the split stacks plugin to create various separate stacks to share the resources amongst them.

If so, can anyone give me any pointers on how this would be achieved?

Much appreciated!