Amazon connect slack8/17/2023 ![]() AWSLambdaBasicExecutionRole (created with the lambda)Īs the last step we need to finish with the SQS configuration.Therefore, we deployed the Lambda Function as a Zip file following the instructions: įinally we need to add some permission policies to the Lambda Function Role: 'body': json.dumps('Code Run Succesfully')īecause this function uses the requests library, it needs to be in the deployment package. You can check the AWS Step Functions API Documentation: Įxample response from the API: CodeMirror Read-only Highlighting Example Step Functions Diagram Lambda Function: GetSFHistory Get Step Functions Logįirst, we need to get detailed information of the Step Functions execution, for that we used the API GetExecutionHistory. Create Slack Hook and Lambda function SendSlackMessage.Create SQS Queue and Lambda function GetSFHistory. ![]() “SendSlackMessage” sends the final message to Slack.SQS runs the lambda function “SendSlackMessage”.Check your connection by attempting to load another website in your browser. “GetSFHistory” gets the Step Functions execution log, builds a slack message and sends it to SQS If you’re having trouble connecting to Slack, the first thing you need to do is check your own connection.EventBridge Rule triggers the lambda function “GetSFHistory”.The Step Functions execute on a daily basis.Our solution sends a Slack notification with the details of each step, the start and end time of the whole process, and the URL for the logs. We were in need to build a notification system that is able to send the Step Functions execution result, right after execution. Send your AWS Step Functions execution result to Slack:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |