timestream-influxdb

Provides guidance for provisioning, configuring, and operating Amazon Timestream for InfluxDB instances and clusters.

2.5k|282|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill timestream-influxdb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timestream-influxdb
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/database-skills/timestream-influxdb
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill timestream-influxdb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Working with Amazon Timestream for InfluxDB involves navigating three distinct engine variants (InfluxDB 2, V2 Read Replica Clusters, and InfluxDB 3) with different ports, APIs, IAM requirements, and monitoring coverage, where mistakes like mixing V2 and V3 APIs or missing Marketplace subscriptions cause provisioning failures.

Core Features & Use Cases

  • Engine Selection & Provisioning: Guides selection between InfluxDB 2, V2 Read Replica Clusters, and InfluxDB 3 Core/Enterprise, including Marketplace subscription, IAM policy, and VPC/security group prerequisites.
  • Schema Design & Migration: Advises on tag vs field decisions, cardinality management, partition templates, and migration from Timestream for LiveAnalytics using the certified migration plugin.
  • Operations & Troubleshooting: Covers CloudWatch alarm setup, maintenance windows, Processing Engine plugins, and diagnosis of connection, write, and query errors.
  • Use Case: A user wants to deploy a new time-series workload on AWS. The skill recommends InfluxDB 3, walks through Marketplace subscription and cluster creation with correct tagging, retrieves the Bearer token from Secrets Manager, and configures security groups for port 8181.

Quick Start

Ask the assistant to help you create a new Amazon Timestream for InfluxDB 3 cluster in your VPC, including the required IAM policies, security group rules, and token retrieval.

Frequently Asked Questions about timestream-influxdb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Amazon Timestream for InfluxDB cluster?

Use aws timestream-influxdb create-db-cluster with a name, instance type, parameter group identifier, VPC subnets, and security groups. For InfluxDB 3, do not pass username, password, organization, or bucket parameters, and subscribe to the AWS Marketplace offering first.

InfluxDB 2 vs InfluxDB 3 on AWS Timestream, which should I choose?

Choose InfluxDB 3 for new workloads since it supports SQL and InfluxQL, handles high cardinality natively, and offers the Processing Engine. Stay on InfluxDB 2 for existing V2 deployments that rely on Flux queries and org/bucket data models.

Why does my InfluxDB 3 connection get refused on port 8086?

InfluxDB 3 uses port 8181, while port 8086 is for InfluxDB 2. Update your client to port 8181 and add a security group inbound rule allowing 8181 from your client CIDR. Private instances also require the client to be in the same VPC or connected via VPN or Direct Connect.

How do I migrate from Timestream for LiveAnalytics to InfluxDB 3?

Use the certified LiveAnalytics Migration plugin with its migration client for datasets under 1 billion records or 125GB. It exports data to S3 in Parquet format and re-ingests it into InfluxDB 3. Larger migrations require contacting your AWS account team.

What CloudWatch metrics are available for InfluxDB 3 on Timestream?

InfluxDB 3 publishes only CPUUtilization and MemoryUtilization to CloudWatch. All other metrics, such as write throughput and query duration, must be collected by scraping the Prometheus /metrics endpoint with a Bearer token.

Can I write custom Processing Engine plugins for InfluxDB 3?

No, the Processing Engine supports only InfluxData certified plugins: Downsampler, Basic Transformation, MAD Anomaly Detection, State Change Monitor, System Metrics Collector, and LiveAnalytics Migration. Custom user-written plugins and custom Python packages are not supported.