This integration ships events from AWS Security Hub to Logz.io. It will automatically deploy resources to your AWS Account.

A new event triggers a designated EventBridge rule, which invokes a Lambda function. The function processes the event and sends it to Logz.io.

Your Lambda function needs to run within the AWS Lambda limits, such as memory allocation and timeout. Make sure you understand these limits. If you can’t adjust your settings to stay within the Lambda limits, you can use the AWS Support Center console to request an increase. Learn more about AWS Lambda Limits.

Login to your account

To begin, you need to login to your AWS account.

Create a new stack

Select the button below to create a new stack dedicated to sending events from AWS Security Hub to Logz.io.

AWS Region Launch a stack
us-east-1 Deploy to AWS
eu-west-1 Deploy to AWS

Create stack

Keep the default setting in the Create stack screen and select Next.

Specify the stack details

Specify stack details

Specify the stack details as per the table below and select Next.

Parameter Description
logzioListener Your Logz.io listener url, followed by port 8070 or 8071. For example, https://listener.logz.io:8071
logzioLogLevel Log level for the Lambda function. Defaults to info. Valid options are: debug, info, warn, error, fatal, panic.
logzioOperationsToken Your Logz.io operations token.
Configure the stack options

Configure stack options

Specify the Key and Value parameters for the Tags and select Next.

Review the deployment

Review deployment Confirm deployment

Confirm that you acknowledge that AWS CloudFormation might create IAM resources and select Create stack.

Deployed resources

This deployment will automatically create the following resources:


Check Logz.io for your events

Give the stack some time to deploy and the resources to get created. Once this is finished, the stack sends a security event to Logz.io as soon as the event is created on the security hub. You can then see the data in Kibana.

If you still don’t see your events, see log shipping troubleshooting.