Amazon DynamoDB stores permissions for each Slack user to ensure they only have access to resources you designate.Amazon EventBridge serves as a pub-sub integration between a request and the request processor.A Lambda Function invokes Slack-specific authentication functionality and sends responses to the Slack UI.Step Functions coordinates request activities such as user validation, configuration retrieval, request routing, and response formatting. Amazon API Gateway receives all incoming requests from Slack.The code included in this post creates a Slack app built with a variety of AWS serverless services: It demonstrates the example and discusses constraints discovered during development. This post explains the serverless example architecture, and walks through how to deploy the example in your AWS account. Visit the documentation for more information on integrations with other AWS resources. This example supports integration with other AWS resources via Step Functions. It can process thousands of concurrent requests for Slack users without the burden of managing operational overhead. Serverless architecture is ideal for a Slack app because of its ability to scale. This blog covers how serverless architecture lets Slack users invoke AWS resources such as AWS Lambda functions and Step Functions via the Slack Desktop UI and Mobile UI using Slack apps. Instead of granting the user direct access to the Step Functions workflow in the AWS Management Console or AWS CLI, you can provide access to invoke the workflow from within a designated Slack channel. ![]() One such opportunity is to expose existing AWS resources to your organization without your employees needing AWS Management Console or AWS CLI access.įor example, a member of your data analytics team needs to trigger an AWS Step Functions workflow to reprocess a batch data job. Slack, as an enterprise collaboration and communication service, presents opportunities for builders to improve efficiency through implementing custom-written Slack Applications (apps). This blog was written by Sam Wilson, Cloud Application Architect and John Lopez, Cloud Application Architect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |