Getting started documentation for AWS lambda can be found in [this
article](https://docs.aws.amazon.com/lambda/latest/dg/getting-started.html). There is also [this blog post](http://alestic.com/2014/11/aws-lambda-cli) on how to set things up using the command line tools.
* zip up your code
```bash
zip -r cloudwatchMetrics2Loggly.zip index.js node_modules
```
The resulting zip (cloudwatchMetrics2Loggly.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 cloudwatchMetrics2Loggly function in the AWS Console
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 13
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:***cloudwatchMetrics2Loggly*
* 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 Events - Schedule*
* Name : Provide any customized name. e.g. cloudwatchMetrics2Loggly Event Source
* Description: Invokes Lambda function in every 5 minutes
* Schedule expression : *rate(5 minutes)*
* Enable Event Source : *Enable Now*
Now click on submit and wait for the events to occur in Loggly
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.
1. Create KMS Key
1. Create a KMS key - http://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html
1. Encrypt the Loggly Customer Token using the AWS CLI
1. Copy or keep `CiphertextBlob` attribute for furhter usage in the next step.
1. Create lambda function
1. Go to https://console.aws.amazon.com/lambda/home
1. Click **Create a Lambda function** button.
1. Select **Author from scratch** option
1. Set **Function name** for example to `cloudwatchMetrics2Loggly`
1. Set **Runtime** to `Node.js 10.x`
1. Under **Permissions** click on **Choose or create an execution role**
1. Select **Use an existing role** and select **cloudwatch-full-access** role created above in step 1
1. Click on **Create function** button
1. Scroll to **Function code** section
1. Select **Upload a .zip file** in **Code entry type** dropdown
1. Upload lambda function (zip file `cloudwatchMetrics2Loggly.zip` you made above)
1. Go to **Environment variables** section
1. Define new environment variable **kmsEncryptedCustomerToken** and set it to `CiphertextBlob` value from step 3 above (Create KMS Key)
1. Scroll to **Basic settings** section
1. Set **Memory (MB)** to **512 MB**
1. Set Timeout to **2** minutes
1. Scroll up to **Designer** section (expand if it's collapsed)
1. Click on **CloudWatch Events** in **Add triggers** section to add the trigger item
1. Click on added **CloudWatch Events** trigger and scroll down to trigger settings
1. Select **Create a new rule** in **Rule** dropdown
1.**Name:** Provide any customized name. e.g. cloudwatchMetrics2Loggly Event Source
1.**Description:** Invokes Lambda function in every 5 minutes
1.**Schedule expression:** rate(5 minutes)
1. Make sure the checkbox **Enable trigger** is checked
1. Click on **Add**
1. Click on **Save** to save the whole lambda function.
1. 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
ProTip!
Use n and p to navigate between commits in a pull request.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
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-4540 - Rewritten lambda to use more efficient API calls #2
LOG-4540 - Rewritten lambda to use more efficient API calls #2
Changes from 1 commit
d25abdb382d253e16d192File filter...
Jump to…
Updated script to use environment variable to get customer token, upd…