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.

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

LOG-9925 - Update lambda code to the latest version in AWS blueprint #3

Merged
merged 2 commits into from Sep 21, 2020
Merged
Changes from 1 commit
Commits
File filter...
Filter file types
Jump to…
Jump to file
Failed to load files.

Always

Just for now

Prev

Fixed README

  • Loading branch information
Jiri Tomek
Jiri Tomek committed Sep 21, 2020
commit 8da9a39d21530dbfc23be718f7bc87f740c42185
@@ -59,70 +59,3 @@ article](https://docs.aws.amazon.com/lambda/latest/dg/getting-started.html). The
**NOTE**: Always use latest version of **AWSCLI**. Some features like KMS may not work on older versions of AWSCLI. To upgrade, use the command given below

`pip install --upgrade awscli`











## Get the code and prepare it for the uploading to AWS
* Clone the git repo
```bash
git clone https://github.com/loggly/cloudwatch2loggly.git
cd cloudwatch2loggly
```
* Install required npm packages.
```
npm install
```

* zip up your code
```bash
zip -r cloudwatch2loggly.zip index.js node_modules
```

The resulting zip (cloudwatch2loggly.zip) is what you will upload to AWS.

## Setting up AWS
For all of the AWS setup, I used the AWS console following [this
example](http://docs.aws.amazon.com/lambda/latest/dg/getting-started-amazons3-events.html). Below, you will find a high-level
description of how to do this. I also found [this blog post](http://alestic.com/2014/11/aws-lambda-cli) on how to set things up
using the command line tools.

### Create and upload the cloudwatch2loggly function in the AWS Console
1. Create Role
1. Sign in to your AWS account and open IAM console https://console.aws.amazon.com/iam/
2. In your IAM console create a new Role say, 'cloudwatch-full-access'
3. Select Role Type as 'AWS Lambda'
4. Apply policy 'CloudWatchFullAccess' and save.
2. Create KMS Key
1. Create a KMS key - http://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html
2. Encrypt the Loggly Customer Token using the AWS CLI - **aws kms encrypt --key-id alias/<your KMS key arn> --plaintext "<your loggly customer token>"**
3. Copy the base-64 encoded, encrypted token from step 2's CLI output (CiphertextBlob attribute) and replace it with the "your KMS encypted key" in the script at line no 22
3. Create lambda function
1. https://console.aws.amazon.com/lambda/home
2. Click "Create a Lambda function" button. *(Choose "Upload a .ZIP file")*
* **Name:** *cloudwatch2loggly*
* Upload lambda function (zip file you made above.)
* **Handler*:** *index.handler*
* Set Role : *cloudwatch-full-access*
* Set Timeout to 2 minutes
3. Go to your Lamda function and select the "Event sources" tab
* Click on **Add Event Source**
* Event Source Type : *CloudWatch Logs*
* Log Group : Select your log group whose logs you want to send to Loggly.
* Filter Name: Provide your filter name.
* Filter Pattern: This is not a mandatory field. You can keep it empty.
* Enable Event Source : *Enable Now*
Now click on submit and wait for the events to occur in Loggly

**NOTE**: Always use latest version of **AWSCLI**. Some features like KMS may not work on older versions of AWSCLI. To upgrade, use the command given below

`pip install --upgrade awscli`


ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.