# Single LogGroup for All Services & Reducing Resource Count

**URL:** <https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887>\
**Category:** Serverless Framework\
**Tags:** aws, lambda\
**Created:** [February 27, 2018, 5:49am UTC](https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887 "2018-02-27T05:49:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lypheus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/lypheus/32/1694_2.png) [@Lypheus](https://forum.serverless.com/u/Lypheus)\
**Post date:** [February 27, 2018, 5:49am UTC](https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887/1 "2018-02-27T05:49:57Z")

</div>

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 😄

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

---

<div class="post-metadata">

**Author:** ![DavidWells](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/davidwells/32/201_2.png) [@DavidWells](https://forum.serverless.com/u/DavidWells)\
**Post date:** [February 27, 2018, 11:36pm UTC](https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887/2 "2018-02-27T23:36:54Z")

</div>

How many functions in your service? 25?

---

<div class="post-metadata">

**Author:** ![Lypheus](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/lypheus/32/1694_2.png) [@Lypheus](https://forum.serverless.com/u/Lypheus)\
**Post date:** [February 28, 2018, 1:15am UTC](https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887/3 "2018-02-28T01:15:54Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![daniel-ciaglia](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@daniel-ciaglia](https://forum.serverless.com/u/daniel-ciaglia)\
**Post date:** [December 20, 2018, 8:04am UTC](https://forum.serverless.com/t/single-loggroup-for-all-services-reducing-resource-count/3887/4 "2018-12-20T08:04:54Z")

</div>

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

> [@Lypheus](#):
>
> If there is a way to have _all_ services share the same LogGroup … instead of having a LogGroup for each service?