I have two separate apps in serverless (app1, app2).
Both apps have about 20 services.
If app1 has a service called “config” and app2 also has a service called “config”, I get a heap of “resource already exists” errors when trying to deploy either service. This is because things like the cloudWatchLogGroup simply use {org}-{service} when naming resources.
Right now my issue is the cloudWatchLogGroup:
An error occurred: ApiGatewayLogGroup - /aws/api-gateway/config-dev already exists in stack
Is there a way to force serverless to include the app name when it generates the resource names?
How does everyone else deal with this?