CODEWITHSUNDEEP
amazon-web-servicesaws-cloudformationserverless-framework
samcorcos
samcorcos

Reputation: 2478

AWS CloudFormation resource limit of 200

I have an app with a lot of resources (a bunch of DynamoDB tables, lambda functions, etc) and apparently I've run into the hard limit of 200 resources. The specific error is:

Template format error: Number of resources, 204, is greater than the maximum allowed, 200

The error message is pretty clear, but I'd like to know what my options are. Worst case, I can split the app into several pieces. Are there any alternative strategies?

Upvotes: 3

Views: 8556

Answers (3)

fileyfood500
fileyfood500

Reputation: 1321

The resource limit is now 500 if that helps!

AWS CloudFormation now supports increased limits on five service quotas

Upvotes: 4

Ashish Kadam
Ashish Kadam

Reputation: 1487

I have to face the same problem in the serverless framework. What I do!

Create microservices for each module like Authentication, User-management, SMS Gateway, Notification etc. that helps to manage code and AWS resources.

At the end expose API to create AWS custom domain and assign cloud formation to it.

I follow this blog, it's help and Serverless also suggest flow link.

Upvotes: 1

John Rotenstein
John Rotenstein

Reputation: 269340

You can create nested stacks that would also have the advantage of simpler testing, improving re-use and using different roles.

Common practice is to separate out different layers into different stacks. For example, build the VPC in one stack, deploy back-end in another stack and the front-end in another stack.

See: Use Nested Stacks to Create Reusable Templates and Support Role Specialization

Upvotes: 7

Related Questions