New Pipelines Data Destination: Amazon Kinesis

A new Pipelines data destination for Amazon Kinesis is now generally available for Golioth users. Amazon Kinesis Data Streams is a massively scalable, highly durable data ingestion and processing service optimized for streaming data.

How It Works

The aws-kinesis data destination is similar to the aws-sqs destination for Amazon Simple Queue Service (SQS). However, besides allowing you take advantage of the unique capabilities of Kinesis Data Streams, the aws-kinesis data destination will pass along the exact data delivered to it regardless of format. This gives you more control on the data that ends up in your data stream, but also means that you’ll need to use a transformer like inject-metadata if you want device ID, project ID, and other metadata included in each message. The device ID is also used as the data stream partition key.

Like other AWS destination, the aws-kinesis data destination accepts access_key, access_secret, and region parameters. It also accepts a stream_arn parameter formatted as an Amazon Resource Name (ARN).

filter:
  path: "*"
steps:
  - name: step0
    destination:
      type: aws-kinesis
      version: v1
      parameters:
        stream_arn: arn:aws:kinesis:us-east-1:123456789:stream/pipelines
        access_key: $AWS_ACCESS_KEY
        access_secret: $AWS_ACCESS_SECRET
        region: us-east-1

Click here to use this pipeline in your Golioth project!

For more details on the aws-kinesis data destination, go to the documentation.

What’s Next

Amazon Kinesis is especially well-suited for high volume data and applications in which there are multiple consumers of the streamed data. It also offers a wide range of integrations with other AWS services, making it a foundational component for customers already leveraging AWS. Reach out to us on the forum if you have any questions on the aws-kinesis data destination or are using an alternative service that does not currently have a native integration in Golioth Pipelines!

Dan Mangum
Dan Mangum
Dan is an experienced engineering leader, having built products and teams at both large companies and small startups. He has a history of leadership in open source communities, and has worked across many layers of the technical stack, giving him unique insight into the constraints faced by Golioth’s customers and the requirements of a platform that enables their success.

Post Comments

No comments yet! Start the discussion at forum.golioth.io

More from this author

Related posts

spot_img

Latest posts

Handling Button Press, Longpress, and Double-Tap with the Zephyr Input Subsystem

Embedded engineers know the joys and pains with button inputs: debouncing them, triggering actions, and more advanced input patterns like long holding the button...

WiFi HaLoW with Morse Micro, Zephyr, and Golioth

Wi-Fi HaLoW enables high throughput, at a long distance using ISM band radios (850-950 MHz, depending on location). This post introduces the concepts behind the demo and shows how to use Morse Micro, Zephyr, and Golioth to send data through walls and up to the cloud.

When Rapid Prototyping becomes Rapid Deployment

Modern IoT teams can move beyond rapid prototyping to rapid deployment. By combining LLM-assisted development with Golioth’s device management, connectivity, and fleet orchestration capabilities, it’s now possible to create IoT fleets with a range of connectivity options in days instead of months.

Want to stay up to date with the latest news?

Subscribe to our newsletter and get updates every 2 weeks. Follow the latest blogs and industry trends.