A Serverless, Event Driven Architecture for Chatbots

Chatbot credentials (app id, secret, page tokens, etc…) can be saved to lambda env vars and retrieved when necessary. Whenever your endpoint gets a correctly signed data from a chat provider and it should return immediately one of the 200(ok), 201(created), or 202(accepted) HTTP status codes. If data is not signed correctly or signature is missing, good to return 403(forbidden) and do not move the data to SNS topic. On every event, the event should be published to an SNS topic with the event inputs and outputs. Appropriate lambda functions should subscribe to the predefined SNS topics and process the data.