Coralogix provides an easy way to collect your CloudWatch Logs. Use AWS Serverless Application Repository for seamless integration.
STEP 1. Navigate to the application page associated with your Coralogix domain and AWS region:
STEP 2. Fill in the required parameters.
STEP 3. Click DEPLOY.
Notes:
Variable | Description |
---|---|
ApplicationName | Application name as it appears in your Coralogix UI |
CloudWatchLogGroupName | Must contain a list of log group names separated by a comma (log-group1,log-group2,log-group3). |
CoralogixRegion | Region [Europe, Europe2, India, Singapore, or US] associated with your Coralogix account domain. If you want to use a custom domain, leave this as default and write the Custom domain in the CustomDomain field. |
CustomDomain | Coralogix custom domain. Leave empty if you do not use a custom domain. |
FunctionArchitecture | Function supports x86_64 or arm64 |
FunctionMemorySize | Max memory for the function itself. Default is 1024. Do not change. |
FunctionTimeout | Maximum time in seconds the function may be allowed to run. Default is 300. Do not change. |
NewlinePattern | Pattern for lines splitting. Default is (?:\r\n|\r|\n) . Do not change. |
PrivateKey | Your Coralogix ‘Send Your Data’ API Key |
NotificationEmail | [Optional] If the Lambda fails, a notification email will be sent to this address via SNS. Requires a working SNS with a validated domain. |
SubsystemName | Subsystem name as it appears in your Coralogix UI |
SsmEnabled | Set this to True to use AWS Secrets. When enabled, it creates the secret in with the following pattern: “lambda/coralogix/<AWS_REGION>/<Cloudwatch_lambda_name>”) – optional. The field receives ‘True’ or ‘False’. Note: Both layers and Lambda need to be in the same AWS Region. |
Notes:
FunctionMemorySize
, FunctionTimeout
, and NewlinePattern
parameters. Application/Subsystem
names with the following syntax: $.my_log.field
.To use AWS Secrets Manager to store your Coralogix PrivateKey, deploy Coralogix SecretLayer form AWS Serverless Repository. You are required to use the parameters below in your deployment.
Variable | Description |
---|---|
ApplicationName | Application name as it appears in your Coralogix UI |
CustomDomain | Coralogix custom domain. Leave empty if you do not use a custom domain. |
CloudWatchLogGroupName | Must contain a list of log group names separated by a comma (log-group1,log-group2,log-group3). |
CoralogixRegion | Region [Europe, Europe2, India, Singapore, or US] associated with your Coralogix account domain. If you want to use a custom domain, leave this as default and write the Custom domain in the CustomDomain field. |
PrivateKey | Your Coralogix ‘Send Your Data’ API Key |
SsmEnabled | Set this to True to use AWS Secrets. When enabled, it creates the secret in with the following pattern: “lambda/coralogix/<AWS_REGION>/<Cloudwatch_lambda_name>”) – optional. The field receives ‘True’ or ‘False’. Note: Both layers and Lambda need to be in the same AWS Region. |
SubsystemName | Subsystem name as it appears in your Coralogix UI |
FunctionArchitecture | Function supports x86_64 or arm64 |
FunctionMemorySize | Max memory for the function itself. Default is 1024. Do not change. |
FunctionTimeout | Maximum time in seconds the function may be allowed to run. Default is 300. Do not change. |
NewlinePattern | Pattern for line splitting. Default is (?:\r\n|\r|\n) . Do not change. |
NotificationEmail | [Optional] If the Lambda fails, a notification email will be sent to this address via SNS. Requires a working SNS with a validated domain. |
LayerARN | ARN for the Coralogix SecurityLayer. Copy the ARN that was installed on the AWS account from the SSM serverless application. |
Notes:
FunctionMemorySize
, FunctionTimeout
, and NewlinePattern
parameters. Application/Subsystem
names with the following syntax: $.my_log.field
.Github | Github documentation |
Need help?
Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.
Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].