All Integrations / HTTP and AWS Timestream Integration

HTTP and AWS Timestream Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

Get This Integration for Free
info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider <a href="/integrations/http-influxdb/">HTTP and InfluxDB</a>.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

<p>The HTTP plugin allows for the collection of metrics from specified HTTP endpoints, handling various data formats and authentication methods.</p>

<p>The AWS Timestream Telegraf plugin enables users to send metrics directly to Amazon’s Timestream service, which is designed for time series data management. This plugin offers a variety of configuration options for authentication, data organization, and retention settings.</p> <p>With the coming End of Life of AWS Timestream for LiveAnalytics, you can easily switch to AWS Timestream for InfluxDB or other verions of InfluxDB hosted on AWS by using the <a href="https://www.influxdata.com/integrations/influxdb/">InfluxDB Telegraf plugin</a>. Learn more about <a href="https://www.influxdata.com/influxdb-cloud-on-aws/">AWS and InfluxDB</a></p>

Integration details

HTTP

<p>The HTTP plugin collects metrics from one or more HTTP(S) endpoints, which should have metrics formatted in one of the supported input data formats. It also supports secrets from secret-stores for various authentication options and includes globally supported configuration settings.</p>

AWS Timestream

<p>This plugin is designed to efficiently write metrics to Amazon’s Timestream for LiveAnalytics service. With AWS no longer accepting new users for their LiveAnalytics service, consider using the <a href="https://www.influxdata.com/integrations/influxdb/">InfluxDB plugin</a> with AWS Timestream for InfluxDB or other <a href="https://www.influxdata.com/influxdb-cloud-on-aws/">InfluxDB options available on AWS</a>. This plugin Telegraf can send data collected from various sources and supports a flexible configuration for authentication, data organization, and retention management. It utilizes a credential chain for authentication, allowing various methods such as web identity, assumed roles, and shared profiles. Users can define how metrics are organized in Timestream—whether to use a single table or multiple tables, alongside control over aspect such as retention periods for both magnetic and memory stores. A key feature is its ability to handle multi-measure records, enabling efficient data ingestion and helping to reduce the overhead of multiple writes. In terms of error handling, the plugin includes mechanisms for addressing common issues related to AWS errors during data writes, such as retry logic for throttling and the ability to create tables as needed.</p>

Configuration

HTTP

<pre><code class="language-toml">[[inputs.http]] ## One or more URLs from which to read formatted metrics. urls = [ "http://localhost/metrics", "http+unix:///run/user/420/podman/podman.sock:/d/v4.0.0/libpod/pods/json" ] ## HTTP method # method = "GET" ## Optional HTTP headers # headers = {"X-Special-Header" = "Special-Value"} ## HTTP entity-body to send with POST/PUT requests. # body = "" ## HTTP Content-Encoding for write request body, can be set to "gzip" to ## compress body or "identity" to apply no encoding. # content_encoding = "identity" ## Optional Bearer token settings to use for the API calls. ## Use either the token itself or the token file if you need a token. # token = "eyJhbGc...Qssw5c" # token_file = "/path/to/file" ## Optional HTTP Basic Auth Credentials # username = "username" # password = "pa$$word" ## OAuth2 Client Credentials. The options 'client_id', 'client_secret', and 'token_url' are required to use OAuth2. # client_id = "clientid" # client_secret = "secret" # token_url = "https://indentityprovider/oauth2/v1/token" # scopes = ["urn:opc:idm:__myscopes__"] ## HTTP Proxy support # use_system_proxy = false # http_proxy_url = "" ## Optional TLS Config ## Set to true/false to enforce TLS being enabled/disabled. If not set, ## enable TLS only if any of the other options are specified. # tls_enable = ## Trusted root certificates for server # tls_ca = "/path/to/cafile" ## Used for TLS client certificate authentication # tls_cert = "/path/to/certfile" ## Used for TLS client certificate authentication # tls_key = "/path/to/keyfile" ## Password for the key file if it is encrypted # tls_key_pwd = "" ## Send the specified TLS server name via SNI # tls_server_name = "kubernetes.example.com" ## Minimal TLS version to accept by the client # tls_min_version = "TLS12" ## List of ciphers to accept, by default all secure ciphers will be accepted ## See https://pkg.go.dev/crypto/tls#pkg-constants for supported values. ## Use "all", "secure" and "insecure" to add all support ciphers, secure ## suites or insecure suites respectively. # tls_cipher_suites = ["secure"] ## Renegotiation method, "never", "once" or "freely" # tls_renegotiation_method = "never" ## Use TLS but skip chain &amp; host verification # insecure_skip_verify = false ## Optional Cookie authentication # cookie_auth_url = "https://localhost/authMe" # cookie_auth_method = "POST" # cookie_auth_username = "username" # cookie_auth_password = "pa$$word" # cookie_auth_headers = { Content-Type = "application/json", X-MY-HEADER = "hello" } # cookie_auth_body = '{"username": "user", "password": "pa$$word", "authenticate": "me"}' ## cookie_auth_renewal not set or set to "0" will auth once and never renew the cookie # cookie_auth_renewal = "5m" ## Amount of time allowed to complete the HTTP request # timeout = "5s" ## List of success status codes # success_status_codes = [200] ## Data format to consume. ## Each data format has its own unique set of configuration options, read ## more about them here: ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md # data_format = "influx" </code></pre>

AWS Timestream

<pre><code class="language-toml">[[outputs.timestream]] ## Amazon Region region = "us-east-1" ## Amazon Credentials ## Credentials are loaded in the following order: ## 1) Web identity provider credentials via STS if role_arn and web_identity_token_file are specified ## 2) Assumed credentials via STS if role_arn is specified ## 3) explicit credentials from 'access_key' and 'secret_key' ## 4) shared profile from 'profile' ## 5) environment variables ## 6) shared credentials file ## 7) EC2 Instance Profile #access_key = "" #secret_key = "" #token = "" #role_arn = "" #web_identity_token_file = "" #role_session_name = "" #profile = "" #shared_credential_file = "" ## Endpoint to make request against, the correct endpoint is automatically ## determined and this option should only be set if you wish to override the ## default. ## ex: endpoint_url = "http://localhost:8000" # endpoint_url = "" ## Timestream database where the metrics will be inserted. ## The database must exist prior to starting Telegraf. database_name = "yourDatabaseNameHere" ## Specifies if the plugin should describe the Timestream database upon starting ## to validate if it has access necessary permissions, connection, etc., as a safety check. ## If the describe operation fails, the plugin will not start ## and therefore the Telegraf agent will not start. describe_database_on_start = false ## Specifies how the data is organized in Timestream. ## Valid values are: single-table, multi-table. ## When mapping_mode is set to single-table, all of the data is stored in a single table. ## When mapping_mode is set to multi-table, the data is organized and stored in multiple tables. ## The default is multi-table. mapping_mode = "multi-table" ## Specifies if the plugin should create the table, if the table does not exist. create_table_if_not_exists = true ## Specifies the Timestream table magnetic store retention period in days. ## Check Timestream documentation for more details. ## NOTE: This property is valid when create_table_if_not_exists = true. create_table_magnetic_store_retention_period_in_days = 365 ## Specifies the Timestream table memory store retention period in hours. ## Check Timestream documentation for more details. ## NOTE: This property is valid when create_table_if_not_exists = true. create_table_memory_store_retention_period_in_hours = 24 ## Specifies how the data is written into Timestream. ## Valid values are: true, false ## When use_multi_measure_records is set to true, all of the tags and fields are stored ## as a single row in a Timestream table. ## When use_multi_measure_record is set to false, Timestream stores each field in a ## separate table row, thereby storing the tags multiple times (once for each field). ## The recommended setting is true. ## The default is false. use_multi_measure_records = "false" ## Specifies the measure_name to use when sending multi-measure records. ## NOTE: This property is valid when use_multi_measure_records=true and mapping_mode=multi-table measure_name_for_multi_measure_records = "telegraf_measure" ## Specifies the name of the table to write data into ## NOTE: This property is valid when mapping_mode=single-table. # single_table_name = "" ## Specifies the name of dimension when all of the data is being stored in a single table ## and the measurement name is transformed into the dimension value ## (see Mapping data from Influx to Timestream for details) ## NOTE: This property is valid when mapping_mode=single-table. # single_table_dimension_name_for_telegraf_measurement_name = "namespace" ## Only valid and optional if create_table_if_not_exists = true ## Specifies the Timestream table tags. ## Check Timestream documentation for more details # create_table_tags = { "foo" = "bar", "environment" = "dev"} ## Specify the maximum number of parallel go routines to ingest/write data ## If not specified, defaulted to 1 go routines max_write_go_routines = 25 ## Please see README.md to know how line protocol data is mapped to Timestream ## </code></pre>

Input and output integration examples

HTTP

<ol> <li><strong>Collecting Metrics from Localhost:</strong> The plugin can fetch metrics from an HTTP endpoint like <code>http://localhost/metrics</code>, allowing for easy local monitoring.</li> <li><strong>Using Unix Domain Sockets:</strong> You can specify metrics collection from services over Unix domain sockets by using the http+unix scheme, for example, <code>http+unix:///path/to/service.sock:/api/endpoint</code>.</li> </ol>

AWS Timestream

<ol> <li> <p><strong>IoT Data Metrics</strong>: Use the Timestream plugin to send real-time metrics from IoT devices to Timestream, allowing for quick analysis and visualization of sensor data. By organizing device readings into a time series format, users can track trends, identify anomalies, and streamline operational decisions based on device performance.</p> </li> <li> <p><strong>Application Performance Monitoring</strong>: Leverage Timestream alongside application monitoring tools to send metrics about service performance over time. This integration enables engineers to perform historical analysis of application performance, correlate it with business metrics, and optimize resource allocation based on usage patterns viewed over time.</p> </li> <li> <p><strong>Automated Data Archiving</strong>: Configure the Timestream plugin to write data to Timestream while simultaneously managing retention periods. This setup can automate archiving strategies, ensuring that older data is preserved according to predefined criteria. This is especially useful for compliance and historical analysis, allowing businesses to maintain their data lifecycle with minimal manual intervention.</p> </li> <li> <p><strong>Multi-Application Metrics Aggregation</strong>: Utilize the Timestream plugin to aggregate metrics from multiple applications into Timestream. By creating a unified database of performance metrics, organizations can gain holistic insights across various services, improving visibility into system-wide performance and facilitating cross-application troubleshooting.</p> </li> </ol>

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration

Start building now

Download Telegraf today or learn more about InfluxDB.

telegraf Get started with InfluxDB
Product & Solutions
Developers
Company

548 Market St, PMB 77953
San Francisco, California 94104

© 2025 InfluxData Inc. All Rights Reserved.

Legal Security Cookie Policy Comparison