Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve oauth lambda deploy instructs #621

Merged
merged 6 commits into from
Mar 22, 2022
Merged

Improve oauth lambda deploy instructs #621

Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
23fdc16
Improve oauth lambda deploy instructs
srajiang Mar 21, 2022
a42dc68
Fix
srajiang Mar 21, 2022
d04a80d
fix indent
srajiang Mar 21, 2022
a9186ed
Tweak
srajiang Mar 21, 2022
75397ed
Update examples/aws_lambda/README.md
srajiang Mar 22, 2022
32ce59c
Update examples/aws_lambda/README.md
srajiang Mar 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
202 changes: 118 additions & 84 deletions examples/aws_lambda/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,87 +85,121 @@ Instructions on how to set up and deploy each example are provided below.

## OAuth Lambda Listener Example Bolt App

1. You need an AWS account and your AWS credentials set up on your machine.
2. Make sure you have an AWS IAM Role defined with the needed permissions for
your Lambda function powering your Slack app:
- Head to the AWS IAM section of AWS Console
- Click Roles from the menu
- Click the Create Role button
- Under "Select type of trusted entity", choose "AWS service"
- Under "Choose a use case", select "Common use cases: Lambda"
- Click "Next: Permissions"
- Under "Attach permission policies", enter "lambda" in the Filter input
- Check the "AWSLambdaBasicExecutionRole" and "AWSLambdaExecute" policies
- Under "Attach permission policies", enter "s3" in the Filter input
- Check the "AWSS3FullAccess" policy
- Click "Next: tags"
- Click "Next: review"
- Enter `bolt_python_s3_storage` as the Role name. You can change this
if you want, but then make sure to update the role name in
`aws_lambda_oauth_config.yaml`
- Optionally enter a description for the role, such as "Bolt Python with S3
access role"
3. Ensure you have created an app on api.slack.com/apps as per the [Getting
Started Guide](https://slack.dev/bolt-python/tutorial/getting-started).
You do not need to ensure you have installed it to a workspace, as the OAuth
flow will provide your app the ability to be installed by anyone.
4. You will need to create two S3 buckets: one to store installation credentials
(when a new Slack workspace installs your app) and one to store state
variables during the OAuth flow. You will need the names of these buckets in
the next step.
5. You need many environment variables exported! Specifically the following from
api.slack.com/apps:
- `SLACK_SIGNING_SECRET`: Signing Secret from Basic Information page
- `SLACK_CLIENT_ID`: Client ID from Basic Information page
- `SLACK_CLIENT_SECRET`: Client Secret from Basic Information page
- `SLACK_SCOPES="app_mentions:read,chat:write"`: Which scopes this application
needs
- `SLACK_INSTALLATION_S3_BUCKET_NAME`: The name of one of the S3 buckets you
created
- `SLACK_STATE_S3_BUCKET_NAME`: The name of the other S3 bucket you created
6. Let's deploy the Lambda! Run `./deploy_oauth.sh`. By default it deploys to the
us-east-1 region in AWS - you can change this at the top of `aws_lambda_oauth_config.yaml` if you wish.
7. Load up AWS Lambda inside the AWS Console - make sure you are in the correct
region that you deployed your app to. You should see a `bolt_py_oauth_function`
Lambda there.
8. While your Lambda exists, it is not accessible to the internet, so Slack
cannot send events happening in your Slack workspace to your Lambda. Let's
fix that by adding an AWS API Gateway in front of your Lambda so that your
Lambda can accept HTTP requests:
- Click on your `bolt_py_oauth_function` Lambda
- In the Function Overview, on the left side, click "+ Add Trigger"
- Select API Gateway from the trigger list
- Make sure "Create an API" is selected in the dropdown, and choose "HTTP API"
as the API Type
- Under Security, select "Open"
- Click "Add"
9. Congrats! Your Slack app is now accessible to the public. On the left side of
your `bolt_py_oauth_function` Function Overview you should see a purple API Gateway
icon. Click it.
10. Click Details to expand the details section.
11. Copy the API Endpoint - this is the URL your Lambda function is accessible
at publicly.
12. We will now inform Slack that this example app can accept Slash Commands.
- Back on api.slack.com/apps, select your app and choose Slash Commands from the left menu.
- Click Create New Command
- By default, the `aws_lambda_oauth.py` function has logic for a
`/hello-bolt-python-lambda` command. Enter `/hello-bolt-python-lambda` as
the Command.
- Under Request URL, paste in the previously-copied API Endpoint from API
Gateway.
- Click Save
13. We also need to register the API Endpoint as the OAuth redirect URL:
- Load up the "OAuth & Permissions" page on api.slack.com/apps
- Scroll down to Redirect URLs
- Copy the API endpoint in - but remove the path portion. The Redirect URL
needs to only _partially_ match where we will send users.
14. You can now install the app to any workspace!
15. Test it out! Once installed to a Slack workspace, try typing
`/hello-bolt-python-lambda hello`.
16. If you have issues, here are some debugging options:
- Check the Monitor tab under your Lambda. Did the Lambda get invoked? Did it
respond with an error? Investigate the graphs to see how your Lambda is
behaving.
- From this same Monitor tab, you can also click "View Logs in CloudWatch" to
see the execution logs for your Lambda. This can be helpful to see what
errors are being raised.
### Setup your AWS Account + Credentials
You need an AWS account and your AWS credentials set up on your machine.

Once you’ve done that you should have access to AWS Console, which is what we’ll use for the rest of this tutorial.

### Create S3 Buckets to store Installations and State

1. Start by creating two S3 buckets:
1. One to store installation credentials for each Slack workspace that installs your app.
2. One to store state variables during the OAuth flow.
2. Head over to **Amazon S3** in the AWS Console
3. Give your bucket a name, region, and set access controls. If you’re doing this for the first time, it’s easiest to keep the defaults and edit them later as necessary. We'll be using the names:
1. slack-installations-s3
2. slack-state-store-s3
4. After your buckets are created, in each bucket’s page head over to “Properties” and save the Amazon Resource Name (ARN). It should look something like `arn:aws:s3:::slack-installations-s3`.

### Create a Policy to Enable Actions on S3 Buckets
Now let's create a policy that will allow the holder of the policy to take actions in your S3 buckets.

1. Head over to Identity and Access Management (IAM) in the AWS Console via Search Bar
2. Head to **Access Management > Policies** and select “Create Policy”
3. Click the JSON tab and copy this in:
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:Get*",
"s3:Put*",
"s3:Delete*",
"s3-object-lambda:*"
],
"Resource": [
"<your-first-bucket-arn>/*", // don't forget the `/*`
"<your-second-bucket-arn>/*"
]
}
]
}
```
4. Edit “Resource” to include the ARNs of the two buckets you created in the earlier step. These need to exactly match the ARNS you copied earlier and end with a `/*`
5. Hit "Next:Tags" and "Next:Review"
6. Review policy
1. Name your policy something memorable enough that you won’t have forgotten it 5 minutes from now when we’ll need to look it up from a list. (e.g. AmazonS3-FullAccess-SlackBuckets)
2. Review the summary, and hit “Create Policy”. Once the policy is created you should be redirected to the Policies page and see your new policy show up as Customer managed policy.
srajiang marked this conversation as resolved.
Show resolved Hide resolved

### Setup an AWS IAM Role with Policies for Executing Your Lambda
Let’s create a user role that will use the custom policy we created as well as other policies to let us execute our lambda, write output logs to CloudWatch.

1. Head to the **Identity and Access Management (IAM)** section of AWS Console
2. Select **Access Management > Roles** from the menu
3. Click "Create Role"
4. Step 1 - Select trusted entity
1. Under "Select type of trusted entity", choose "AWS service"
2. Under "Choose a use case", select "Common use cases: Lambda"
3. Click "Next: Permissions”
5. Step 2 - Add permissions
1. Add the following policies to the role we’re creating that will allow the user with the role permission to execute Lambda, make changes to their S3 Buckets, log output to CloudWatch
1. `AWSLambdaExecute`
2. `AWSLambdaBasicExecutionRole`
3. `<NameOfRoleYouCreatedEarlier>`
6. Step 3 - Name, review, create
1. Enter `bolt_python_s3_storage` as your role name. To use a different name, make sure to update the role name in `aws_lambda_oauth_config.yaml`
2. Optionally enter a description for the role, such as "Bolt Python with S3 access role”
3. “Create Role”
srajiang marked this conversation as resolved.
Show resolved Hide resolved

### Create Slack App and Loaded your Lambda to AWS
Ensure you have created an app on [api.slack.com/apps](https://api.slack.com/apps) as per the Getting Started Guide. You do not need to ensure you have installed it to a workspace, as the OAuth flow will provide your app the ability to be installed by anyone.

1. Remember those S3 buckets we made? You will need the names of these buckets again in the next step.
2. You need many environment variables exported! Specifically the following from api.slack.com/apps

```bash
SLACK_SIGNING_SECRET= # Signing Secret from Basic Information page
SLACK_CLIENT_ID= # Client ID from Basic Information page
SLACK_CLIENT_SECRET # Client Secret from Basic Information page
SLACK_SCOPES= "app_mentions:read,chat:write"
SLACK_INSTALLATION_S3_BUCKET_NAME: # The name of installations bucket
SLACK_STATE_S3_BUCKET_NAME: # The name of the state store bucket
export
```
6. Let's deploy the Lambda! Run `./deploy_oauth.sh`. By default it deploys to the us-east-1 region in AWS - you can customize this in `aws_lambda_oauth_config.yaml`.
7. Load up AWS Lambda inside the AWS Console - make sure you are in the correct region that you deployed your app to. You should see a `bolt_py_oauth_function` Lambda there.

### Set up AWS API Gateway
Your Lambda exists, but it is not accessible to the internet, so Slack cannot yet send events happening in your Slack workspace to your Lambda. Let's fix that by adding an AWS API Gateway in front of your Lambda so that your Lambda can accept HTTP requests

1. Click on your `bolt_py_oauth_function` Lambda
2. In the **Function Overview**, on the left side, click "+ Add Trigger"
3. Select "API Gateway" from the trigger list
4. Make sure "Create an API" is selected in the dropdown, and choose "HTTP API" as the API Type
5. Under Security, select "Open"
6. Click "Add"

Phew, congrats! Your Slack app is now accessible to the public. On the left side of your bolt_py_oauth_function Function Overview you should see a purple API Gateway icon. Click it.

1. Click Details to expand the details section.
2. Copy the API Endpoint - this is the URL your Lambda function is accessible at publicly.
3. We will now inform Slack that this example app can accept Slash Commands.
4. Back on [api.slack.com/apps](https://api.slack.com/apps), select your app and choose "Slash Commands" from the left menu.
5. Click "Create New Command"
1. By default, the `aws_lambda_oauth.py` function has logic for a /hello-bolt-python-lambda command. Enter `/hello-bolt-python-lambda` as the Command.
* Under Request URL, paste in the previously-copied API Endpoint from API Gateway.
* Click Save
6. We also need to register the API Endpoint as the OAuth redirect URL:
1. Load up the "OAuth & Permissions" page on[api.slack.com/apps](https://api.slack.com/apps)
2. Scroll down to "Redirect URLs"
3. Copy the API endpoint in - but remove the path portion. The Redirect URL needs to only partially match where we will send users.

You can now install the app to any workspace!

### Test it out!
1. Once installed to a Slack workspace, try typing `/hello-bolt-python-lambda` hello.
2. If you have issues, here are some debugging options:
1. _View lambda activity_: Head to the Monitor tab under your Lambda. Did the Lambda get invoked? Did it respond with an error? Investigate the graphs to see how your Lambda is behaving.
2. _Check out the logs_: From this same Monitor tab, you can also click "View Logs in CloudWatch" to see the execution logs for your Lambda. This can be helpful to see what errors are being raised.