Single LogGroup for All Services & Reducing Resource Count

Hey All -

I’m running into the CloudFormation resource limit of 200 pretty easily with serverless, in my case I’m just standing up about 25 services (which from what I can tell map to about 4 resources each).

In an effort to buy myself some room here (and fix the mess of default log groups and logging in AWS), I’m wondering:

  1. If there is a way to have all services share the same LogGroup … instead of having a LogGroup for each service?

  2. What I’m probably doing wrong here to hit this ceiling so quickly … I suspect my config is producing separate services where only one is needed but could use a hand refactoring it to be cleaner.

Here’s a sample snippet of my yaml, any help would be appreciated :smile:

messages-post:
handler: messages/post.handler
events:
- http:
path: api/messages
method: post
messages-get:
handler: messages/get.handler
events:
- http:
path: api/messages/{id}
method: get
- http:
path: api/messages/owner/{owner}
method: get
messages-delete:
handler: messages/delete.handler
events:
- http:
path: api/messages/{id}
method: delete

How many functions in your service? 25?

Ya 25 after that I get hit by the 20p limit. Contacted AWS to see about a limit raise in meantime.

Did you find a solution for that requirement? We are looking into use of CloudWatch Insights but that works best on a single Loggroup.