Figuring this out has taken a few hours out of my day.
Your system is comprised of multiple CloudFormation stacks (aka Serverless Framework services aka microservices)
What not to do
functions: dispatcher: handler: dispatcher.dispatch events: - sns: 'demo_submitted'
It is critically important to not create SNS topic subscriptions on the fly as lambda event triggers. The reason is that Serverless framework tries to be helpful by implicitly auto-magically creating resource declarations for those topics, effectively within the boundaries of the consumer service. Unless parts of your microservice are talking amongst themselves using SNS (which would be weird), you usually subscribe to SNS topics that originate in other services, not the one where you are consuming it.
Why not to do it
Let's say you try to subscribe to the same topic with a lambda in another service OR you go down the road of explicitly declaring topics as resources in the services that broadcast to the topics AND you've implicitly created those very same SNS topics already.
Then when you try to deploy you will get an error that looks something like this:
Serverless Error --------------------------------------- An error occurred: DemoSubmittedTopic - demo_submitted already exists in stack arn:aws:cloudformation:us-east-1:423:stack/producers-service-dev/5332a.
Resources must be unique and in this case, you already created that SNS topic in the consumer, not where it belongs and is expected to live.
What to do instead
When you subscribe a lambda to an SNS topic, use the ARN notation as described in https://serverless.com/framework/docs/providers/aws/events/sns#using-a-pre-existing-topic
functions: dispatcher: handler: dispatcher.dispatch events: - sns: arn: arn:xxx
The ARN notation in the subscription prevents the auto-magical undesirable creation of an SNS resource.