Skip to content

Commit

Permalink
Clean up README
Browse files Browse the repository at this point in the history
  • Loading branch information
Tehnix committed May 24, 2022
1 parent 8845dfd commit 09068f3
Showing 1 changed file with 4 additions and 25 deletions.
29 changes: 4 additions & 25 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,36 +6,15 @@ Sends daily breakdowns of AWS costs to a Slack channel.

# Install

1. Install [`serverless`](https://serverless.com/), which I use to configure the AWS Lambda function that runs daily.

```
npm install -g serverless
```

1. Create an [incoming webhook](https://www.slack.com/apps/new/A0F7XDUAZ) that will post to the channel of your choice on your Slack workspace. Grab the URL for use in the next step.

1. Create the service on your local machine. cd to your directory and run this command. Replace path with the path name for the service and app name for the service.

```
serverless create \
--template-url="https://github.com/iandees/aws-billing-to-slack.git" \
--path="app-aws-cost" \
--name="app-aws-cost"
```

1. Install pipenv

```
pip install pipenv
```

1. Install serverless python requirements
2. Install serverless python requirements

```
serverless plugin install -n serverless-python-requirements
SLACK_WEBHOOK=https://hooks.slack... npm run deploy
```

1. Deploy the system into your AWS account, replacing the webhook URL below with the one you generated above.
3. Deploy the system into your AWS account, replacing the webhook URL below with the one you generated above.

```
serverless deploy --stage="prod" --param="slack_url=https://hooks.slack.com/services/xxx/yyy/zzzz"
Expand All @@ -44,7 +23,7 @@ Sends daily breakdowns of AWS costs to a Slack channel.
You can also run it once to verify that it works:

```
serverless invoke --function reportCost --stage="prod" --param="slack_url=https://hooks.slack.com/services/xxx/yyy/zzzz"
npm run invoke
```

## Support for AWS Credits
Expand Down

0 comments on commit 09068f3

Please sign in to comment.