AWS Kinesis Firehose

Send Sym logs to Kinesis Firehose, and from there, anywhere else!

Overview

With the Kinesis Firehose Log Destination, you can send the full stream of Reporting events from Sym to any destination supported by Kinesis Firehose.

This is a powerful integration that can sit upstream of any number of logging destinations, including:

  • AWS S3
  • DataDog
  • New Relic
  • Redshift
  • Splunk

🚧

Did you connect the Sym Runtime with your AWS Account?

If you have not yet, follow the Connect the Sym Runtime with your AWS Account tutorial on the main AWS page to set up your Runtime Connector module and Runtime Permission Context before continuing.

Add the Kinesis Firehose Add-on to your Runtime Connector

The aws/kinesis-firehose add-on gives your Sym Runtime the permissions to push to AWS Kinesis Firehose.

module "runtime_connector" {
  source  = "symopsio/runtime-connector/aws"
  version = ">= 1.0.0"

  environment = "main"

    # This add-on is required for Reporting via Kinesis Firehose
  addons = ["aws/kinesis-firehose"]
}

Downstream logging destinations

Once you've set up a basic Kinesis Firehose, you will be able to pipe your Sym logs downstream to a number of destinations. The simplest approach is to send logs to an S3 bucket, but the combination of Kinesis + Terraform's mutual support for sending logs to HTTP endpoints makes most downstream integrations a breeze.

Downstream configurations for AWS Kinesis Firehose will usually take one of three types: Kinesis firehose built-in support, support via HTTP endpoint, or abstracted support via Sym module.

Further reading

For more information on sending logs downstream from AWS Kinesis Firehose, see the HashiCorp AWS Provider docs here.


What’s Next