Coralogix provides a predefined Lambda function to forward your Cloudwatch logs straight to Coralogix.
The preferred and easiest integration method will be to use our aws Serverless Application Repository. Search for ‘coralogix’. Don’t forget to check the ‘Show apps that create custom IAM roles or resource policies’ box located just under the search field to see all available applications. Select your application of choice and click on it. You will see detailed instructions in the readme section on the left.
You can include SAM (Serverless Application Model) in your automation frameworks. If you need access to the latest and greatest Lambda code go to https://github.com/coralogix/coralogix-aws-serverless/tree/master/src.
The rest of this document describes a manual configuration of this integration and the Lambda associated with it and should be used if there is a need for special customization.
Follow the following 7 steps to get your Cloudwatch logs streaming into Coralogix:
This document includes cluster dependent URL’s. Each URL has a variable part (in Italic). Please match this part with a row entry within the following table. Copy the table row entry located under the column that matches the top level domain of your Coralogix account (.com, .in etc.). Replace the variable part of the URL with this entry.
1. Create an “author from scratch” Node.js 10.x runtime lambda with basic permissions:
2. At “Code entry type” choose “Edit code inline” and paste the function code.
3. Add the mandatory environment variables
Private Key – A unique ID that represents your company, this Id will be sent to your mail once you register to Coralogix.
Application Name – Used to separate your environment, e.g. SuperApp-test/SuperApp-prod.
SubSystem Name – Your application probably has multiple subsystems, for example, Backend servers, Middleware, Frontend servers, etc. If the Subsystem name environment variable is left empty, The Lambda function will assign the appropriate log group name as the Subsystem name value.
If your Coralogix account top level domain is not ‘.com’ add the following environment variables:
4. Go to “Add triggers” and add “CloudWatch logs”: