[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"pattern-lambda-eventbridge-sns-sam":3},{"id":4,"title":5,"architectureURL":6,"cleanup":7,"contributors":12,"deploy":14,"description":17,"extension":18,"framework":19,"gitHub":20,"highlight":6,"introBox":26,"language":31,"level":32,"meta":33,"patternArch":34,"resources":53,"s3URL":6,"services":6,"stem":68,"testing":69,"videoId":6,"__hash__":73},"patterns\u002Fpatterns\u002Flambda-eventbridge-sns-sam.json","AWS Lambda to Amazon EventBridge to Amazon SNS",null,{"headline":8,"text":9},"Cleanup",[10,11],"1. Delete the stack: \u003Ccode>sam delete --stack-name STACK_NAME\u003C\u002Fcode>.","2. Confirm the stack has been deleted: \u003Ccode>aws cloudformation list-stacks --query \"StackSummaries[?contains(StackName,'STACK_NAME')].StackStatus\"\u003C\u002Fcode>",[13],"content\u002Fcontributors\u002Fsylvester-kachi.json",{"text":15},[16],"sam deploy --guided","Route events from EventBridge to multiple SNS topics.","json","AWS SAM",{"template":21},{"projectFolder":22,"repoURL":23,"templateURL":24,"templateFile":25},"lambda-eventbridge-sns-sam","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-patterns\u002Ftree\u002Fmain\u002Flambda-eventbridge-sns-sam","serverless-patterns\u002Flambda-eventbridge-sns-sam","template.yaml",{"headline":27,"text":28},"How it works",[29,30],"The AWS SAM template deploys three EventBridge Buses, six EventBridge Rules (2 per bus),  four SNS Topics, three SQS queues and a Lambda function.  The lambda function is an event generator which sends events to EventBridge Buses that trigger appropriate Rules sending the payload to the appropriate SNS Topic. SQS queues are attached to the Rules as Dead Letter Queues. Appropriate permissions are granted to EventBridge to trigger the SNS Topics and the Lambda function to put events in the EventBridge.","Consider this example: countries report cross-border transactions to their respective central banks. For simplicity, transactions originate from bank branches or ATM (automatic teller machines) as sub-domains (source) from all banks. For simplicity we use three EventBridge Buses - (bluebank, redbank and greenbank). The 'DetailType' is filtering for 'transaction type' and the 'Detail' section filters the 'Yes\u002FNo' reportable field.  Based on these combinations, events trigger different rules and send transaction payloads to SNS Topics of the ReserveBank and\u002For the Transaction Warehouses of the respective bank's SNS topics.","Python","200",{},{"icon1":35,"icon2":40,"icon3":43,"line1":47,"line2":51},{"x":36,"y":37,"service":38,"label":39},20,50,"lambda","AWS Lambda",{"x":37,"y":37,"service":41,"label":42},"eventbridge","EventBridge",{"x":44,"y":37,"service":45,"label":46},80,"sns","SNS",{"from":48,"to":49,"label":50},"icon1","icon2","",{"from":49,"to":52,"label":50},"icon3",{"headline":54,"bullets":55},"Additional resources",[56,59,62,65],{"text":57,"link":58},"Permissions for Amazon EventBridge event buses","https:\u002F\u002Fdocs.amazonaws.cn\u002Fen_us\u002Feventbridge\u002Flatest\u002Fuserguide\u002Feb-event-bus-perms.html#eb-event-bus-example-policy-cross-account",{"text":60,"link":61},"Content filtering in Amazon EventBridge event patterns","https:\u002F\u002Fdocs.aws.amazon.com\u002Feventbridge\u002Flatest\u002Fuserguide\u002Feb-event-patterns-content-based-filtering.html",{"text":63,"link":64},"Integrating Amazon EventBridge into your serverless applications","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fintegrating-amazon-eventbridge-into-your-serverless-applications\u002F",{"text":66,"link":67},"Use Amazon EventBridge to Build Decoupled, Event-Driven Architectures","https:\u002F\u002Fserverlessland.com\u002Flearn\u002Feventbridge","patterns\u002Flambda-eventbridge-sns-sam",{"headline":70,"text":71},"Testing",[72],"See the GitHub repo for detailed testing instructions.","L1EhauWMldBq8Cb9gTsq6PvBd0v6T2gSSly85mc7-Pw",1780742124636]