I am deploying via Serverless a lambda function which uses an EventBridge custom bus as trigger. I’ve just noticed that Serverless seems to create 2 lambda functions instead of just mine.
Let’s say if my lambda function is called myLambda, the framework would deploy:
- myLambda-stage-custom-resource-event-bridge (which seems to contain code to set permissions, etc.)
Noteworthy: I am deploying via this action triggered on pushes to my repo.
Is it intended or is it maybe a remain of an intermediate resource created to setup the final lambda which didn’t got removed? (I don’t recall seeing this a few weeks ago)
Thanks in advance!