Documentation

Write data with third-party technologies

Configure third-party technologies to send line protocol directly to InfluxDB.

AWS Lambda via CloudFormation template

Write to InfluxDB with AWS Lambda, Amazon Web Services’ serverless offering. This example provides a CloudFormation template that collects earthquake from the United States Geological Survey (USGS) every hour and outputs it as line protocol into an InfluxDB bucket.

The template contains the following sections:

  • Lines 1-20: Define variables that the template asks for when it’s installed.
  • Lines 21-120: Handle a quirk of Lambda deployments that requires the Lambda assets to be in your region before deployment. As there is no elegant workaround, these 100 lines create an S3 bucket in your account in the region you’re creating the stack and copies in these resources.
  • Lines 121-132: Define a role with basic permission to run the Lambda.
  • Lines 133-144: Define a Python library layer. This layer packages the Python HTTP library, a Python S2 Geometry library, and the InfluxDB Python client library.
  • Lines 145-165: Define the Lambda function, a short Python script zipped up in a file called geo_lambda.zip.
  • Lines 166-188: Define an event rule with permission to run the Lambda every hour.

Deploy the template

  1. Log into your free AWS account and search for the CloudFormation service. Make sure you’re in the AWS region you want to deploy the Lambda to⁠.
  2. Click Create Stack.
  3. In the Prerequisite - Prepare Template section, select Template is ready.
  4. In the Specify template section:
  • Under Template source, select Amazon S3 URL.
  • In the Amazon S3 URL field, enter the CloudFormation template URL: https://influxdata-lambda.s3.amazonaws.com/GeoLambda.yml
  1. Click Next.
  2. Enter a name in the Stack name field.
  3. Enter the following InfluxDB details:
  • Organization ID
  • Bucket ID of the bucket the Lambda writes to
  • Token with permission to write to the bucket
  • InfluxDB URL
  1. Do not alter or add to any other fields. Click Next.
  2. Select the I acknowledge that AWS CloudFormation might create IAM resources check box.
  3. Click Create Stack.

After a few minutes, the stack deploys to your region. To view the new Lambda, select Services > AWS Lambda. On the Lambda functions page, you should see your new Lambda. The CopyZipsFunction is the helper copy function, and the GeoPythonLambda does the data collection and writing work:

GeoPythonLambda data in InfluxDB

Verify your setup

GeoPythonLambda should run every hour based on the AWS Rule we set up, but you should test and confirm it works.

  1. Click GeoPythonLambda, and then click Test.
  2. The test requires an input definition, but this Lambda has no input requirements, so click through and save the default dataset.
  3. If the test is successful, a green Execution result: succeeded message appears.

With the data points written, when you log into your InfluxDB UI, you’ll be able to explore the geolocation earthquake data:

GeoPythonLambda data in InfluxDB

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: