influxdata/telegraf

Support Timestream for InfluxDB Endpoints in Telegraf Timestream Output Plugin

Open

#18045 opened on Nov 21, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (9,892 stars) (4,161 forks)batch import
feature requesthelp wantedsize/l

Description

Use Case

The current Telegraf Timestream output plugin only supports the Timestream LiveAnalytics (Write API) endpoints.

However, AWS has deprecated/limited access to Timestream LiveAnalytics, and is now promoting Timestream for InfluxDB as the recommended ingestion path.

Ideally, the plugin would:

  • detect and support the timestream-influxdb ingestion API
  • allow configuration of the InfluxDB-compatible endpoints
  • fall back gracefully when LiveAnalytics is unavailable

This would ensure Telegraf remains compatible with the current direction of Amazon Timestream and newer AWS regions.

Expected behavior

Add support for the timestream-influxdb service endpoints exposed by AWS:

AWS CLI reference: https://docs.aws.amazon.com/cli/latest/reference/timestream-influxdb/

This would enable Telegraf users to write metrics into AWS Timestream even in regions where LiveAnalytics is not deployed or available to new customers.

Actual behavior

In supported regions, accounts receive:

aws timestream-write describe-endpoints --region eu-central-1

An error occurred (AccessDeniedException) when calling the DescribeEndpoints operation:
Only existing Timestream for LiveAnalytics customers can access the service.
Reach out to AWS support, for more information.

Trying to use the plugin in regions where LiveAnalytics is not available leads to errors:

aws timestream-write describe-endpoints --region me-central-1

Could not connect to the endpoint URL: "https://ingest.timestream.me-central-1.amazonaws.com/"

The current implementation uses the AWS SDK’s Timestream Write client: https://github.com/influxdata/telegraf/blob/467473bdb7087e42a5c1c11e63d64731883eb079/plugins/outputs/timestream/timestream.go#L17

Additional info

Telegraf 1.36.4 (git: HEAD@467473bd)

Contributor guide

Tech stack
goaws
Domain
backendclouddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GoAWS SDK for GoTelegraf plugin developmentTimestream concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Start by examining the existing Timestream output plugin at plugins/outputs/timestream/timestream.go, specifically the AWS SDK client initialization using timestreamwrite.New (line 17). Create a new client for the timestream influxdb service using the AWS SDK's timestreaminfluxdb package. Modify the plugin configuration to allow users to specify which service endpoint to use, with fallback logic. Refer to the AWS CLI reference for timestream influxdb to understand the API endpoints.