akenza.io
WebsiteAPI DocumentationWhat's newLogin
  • Overview
  • Getting Started
    • Connect a Device
  • Changelog
  • General
    • Applications
    • Organization context
    • Workspace Context
    • Users
      • User Roles
  • Device Management
    • Managing an organization
      • API keys
      • Users (Organization)
        • Add & removing users from your organization
    • Managing a workspace
      • General Settings
        • Device Lifecycle Reports
        • Workspace properties
        • Occupancy settings
        • Device Setup Assistant
      • Custom fields
      • Tags
      • Users (Workspace)
    • Devices
      • Device
      • Device Simulator
      • Bulk actions
      • Bulk import CSV templates
    • Rules
      • Input
      • Logic blocks
        • Comparison
        • Custom Logic
          • Logic Block Scripting
      • Timed Rules
      • Rule Actions
        • Downlink
    • Data Flows
      • Device Connectors
        • Device Security
          • Using Device Credentials
            • Creating Public/Private Key Pairs
            • Using JSON Web Tokens (JWTs)
              • Python
              • Java
        • HTTP
        • MQTT
        • CoAP
        • LoRaWAN
          • Connectivity Management
          • Swisscom LoRaWAN
          • The Things Network
          • Loriot
          • Actility’s ThingPark Wireless
          • EWZ
          • Cibicom
          • Helium
          • ChirpStack
        • NB-IoT
        • mioty
        • Disruptive Technologies
        • VergeSense
        • Spaceti
        • Haltian
      • Device Types
        • Custom Device Types
          • Uplink
          • Downlink
          • Scripting
        • Library
      • Output Connectors
        • Databases
          • akenza DB
          • InfluxDB
          • SQL Databases
        • Streaming
          • Webhook
          • Azure IoT Hub
          • AWS Kinesis
          • Google Cloud Pub/Sub
          • Apache Kafka
        • Notifications
          • E-Mail
          • SMS
          • Microsoft Teams
          • Slack
    • Custom Components
    • Integrations
    • Reference
      • REST API
        • Filtering
        • Querying Device Data
      • WebSocket API
      • Scripting
        • Stateful Operations
        • Utility Functions
      • Payload Templating
  • Reference
  • Dashboard Builder
    • Managing Dashboards
      • Embedding dashboards
    • Components
      • Map
      • Floorplan
  • Device Setup Assistant
    • Device Setup Assistant - Overview
  • Tutorials
    • BI Tools
      • Grafana Data Source Plugin
      • How to build a dashboard with Retool
      • How to analyze data with AWS QuickSight
    • Devices
      • How to integrate the XDK device from Legic via MQTT on akenza
      • How to connect the Disruptive Technologies-cloud on akenza
      • How to send Downlinks to the Kuando Busylight device
      • How to integrate an Arduino device via MQTT on akenza
      • Integrate a MClimate Vicki LoRaWAN Radiator Thermostat on akenza
      • How to integrate an ERS Elsys device with Loriot on akenza
      • How to integrate the IAM Decentlab device with TTN on akenza
      • How to integrate the Seeed SenseCAP T1000 tracker on akenza
      • How to integrate a Swisscom Multisense device on akenza
    • Notifications
      • How to send SMS notifications
      • How to send notifications to Slack
      • How to send notifications to Microsoft Teams
    • Enterprise solutions
      • How to send data to Azure IoT Hub
      • How to send data to the Google Cloud Pub/Sub
      • How to send data to InfluxDB
      • How to send data to AWS Kinesis
      • How to send data to Azure Event Hubs with Apache Kafka
    • IoT Starter Kits
      • How to integrate the IAQ Kit with Actility on akenza
      • How to integrate the CoWork Kit with Actility on akenza
      • How to integrate the Smart Building Kit with Actility on akenza
      • How to integrate the Pepperl+Fuchs Kit with Actility on akenza
  • Support Center
    • FAQ
    • Status Page
    • Service Desk
    • Request a feature
  • Deprecated
    • SIM-Cards
    • Everynet
    • Sigfox
    • How to connect the Yanzi Lifecycle cloud on akenza
Powered by GitBook
On this page
  • 1. Setup an AWS Kinesis stream
  • 2. Setup a Data Flow in akenza
  • 3. Monitor Events
  • 4. Use of further AWS services
  • 5. Useful Links

Was this helpful?

  1. Tutorials
  2. Enterprise solutions

How to send data to AWS Kinesis

In this tutorial you will learn how to send data to AWS Kinesis

PreviousHow to send data to InfluxDBNextHow to send data to Azure Event Hubs with Apache Kafka

Last updated 4 months ago

Was this helpful?

Benefits of the AWS Kinesis output connector:

  • Easily process low-power device data e.g. LoRaWAN device data in a AWS Kinesis

In this tutorial, you will learn, how to send data to AWS Kinesis. The following steps are explained in more detail:

1. Setup an AWS Kinesis stream

First, you will need to set up AWS kinesis in order to successfully process data from akenza in AWS services.

  • Create a new AWS Kinesis stream resource, by searching for Kinesis and creating a data stream

    • copy the stream ARN for later use

  • Create a new API user by searching for IAM

    • create a new policy with access to the Kinesis service

    • Expand the tab Write and select

      • PutRecord

      • PutRecords

      • ListShards

    • Add the ARN of the newly created kinesis stream as resources

    • create a new user which uses access key as the credentials type and the previously created policy

2. Setup a Data Flow in akenza

In akenza, create a new Data Flow with AWS Kinesis as Output Connector. Define a Connector Name, enter the IAM user id and key as well as the Kinesis data stream ARN. Save the connector and Data Flow accordingly.

Optionally: The custom payload can be selected for making use of templated payload in the desired structure. If the custom payload is not selected, the whole data sample will be forwarded.

3. Monitor Events

aws kinesis get-shard-iterator --shard-id shardId-000000000000 --shard-iterator-type LATEST --stream-name {streamName} --query 'ShardIterator'

Send data to your device and execute the following command accordingly.

aws kinesis get-records --shard-iterator {shardIterator}

You should now see your base64 encoded records as well as the next shard iterator. If there is no data repeat the previous command with the next shard iterator.

4. Use of further AWS services

Once a device is connected to the kinesis, device data can be further used on various AWS services:

Possible services are:

  • Real-time data stream processing

  • Object storage is built to retrieve any amount of data from anywhere

  • Run code without thinking about servers or clusters

5. Useful Links

Directly stream device data from akenza to AWS Kinesis and subsequently process it in

Sign in to the

using the Data Flow and start sending data.

In order to monitor uplinks that are sent to AWS Kinesis, you can use . To check if the uplinks arrived execute as a first step the following command and copy the return value. This value is the shard iterator used in the following commands.

AWS Kinesis
Amazon portal
Create a new device
AWS cli
AWS kinesis firehouse
AWS S3
AWS Lambda
Setup an AWS Kinesis stream
Setup a Data Flow in akenza
Monitor events
Use of further AWS services
Useful Links
Logohttps://eu-central-1.console.aws.amazon.com/kinesis/home?region=eu-central-1#/home
LogoCloud Object Storage – Amazon S3 – Amazon Web ServicesAmazon Web Services, Inc.
AWS Kinesis Output Connector
Kinesis Policy
New AWS Kinesis Data Flow
LogoServerless Computing - AWS Lambda - Amazon Web ServicesAmazon Web Services, Inc.