Back to Skills

timestream-influxdb

Retrieves authoritative guidance on Amazon Timestream for InfluxDB (managed InfluxDB 2, InfluxDB 2 Read Replica Clusters, InfluxDB 3 Core and Enterprise). Applicable to any InfluxDB-on-AWS request including engine selection, provisioning (Marketplace + AmazonTimestreamInfluxDBFullAccess/ConsoleFullAccess IAM), schema design (tags vs fields, cardinality, HTTP/sensor/metric data modeling), migration from LiveAnalytics, Processing Engine plugins, connectivity (port 8086 V2, port 8181 V3, VPC-only b

2,362stars245forksUpdated 8/16/2026

Security Assessment

Safe(93/100)
Security Score93/100

About timestream-influxdb

Timestream for InfluxDB provides authoritative, advisory guidance for Amazon Timestream for InfluxDB across its engine variants: managed InfluxDB 2 single-node, InfluxDB 2 Read Replica Clusters, and InfluxDB 3 Core and Enterprise. It solves the problem of navigating a service with materially different APIs, ports, and defaults per engine by supplying correct, non-hallucinated guidance and the standard aws CLI commands to carry out actions. It is explicitly advisory and executes mutations only in response to an explicit user request, never autonomously.

It covers engine selection (recommending InfluxDB 3 for new workloads), dependency verification, and provisioning prerequisites — including the AWS Marketplace subscription, the two required IAM managed policies, VPC-only-by-default networking with opt-in public access, and correct ports (8086 for V2, 8181 for V3). It documents schema design (low-cardinality tags versus fields), migration from LiveAnalytics, Processing Engine plugins, monitoring, and troubleshooting, with bundled reference docs and helper scripts for VPC endpoint checks, token retrieval, health checks, and input validation. A notable section lists authoritative facts that override the model's training data (upgrade paths, token storage in Secrets Manager, reboot commands, S3 log delivery) and forbids inventing metric names or nonexistent features.

It targets AWS engineers, DevOps teams, and database administrators deploying or operating InfluxDB on AWS. The skill is security-conscious defensive tooling: it runs read-only aws describe/list commands freely and performs mutations only on explicit user request, and it actively promotes secure configuration — scoped IAM over FullAccess for production, restricting security-group ingress to known CIDRs, and never using an open 0.0.0.0/0 rule.

FAQ

Which engine should I choose?

It recommends InfluxDB 3 Core for new workloads (Enterprise for HA multi-node), InfluxDB 2 or a Read Replica Cluster for existing V2 workloads migrating to AWS, and InfluxDB 3 for high cardinality above 10M series, SQL queries, or the Processing Engine.

What are the provisioning prerequisites?

For InfluxDB 3 and V2 Read Replica Clusters you need an AWS Marketplace subscription and two IAM managed policies (AmazonTimestreamInfluxDBFullAccess and AmazonTimestreamConsoleFullAccess). Instances are VPC-only by default with opt-in public access, and ports are 8086 for V2 and 8181 for V3.

Does it change my AWS resources on its own?

No. It is advisory: it recommends actions and provides the aws CLI commands, and it executes mutations such as instance or cluster creation only in response to an explicit user request, never autonomously.

How does it handle security for network access?

It requires restricting security-group inbound rules to known CIDR ranges or security group IDs, explicitly forbids using 0.0.0.0/0, and recommends replacing the FullAccess policies with a scoped custom IAM policy for production workloads.

How does it avoid giving wrong answers?

It includes a set of authoritative facts that override training data (such as the Core-to-Enterprise upgrade path, token storage in Secrets Manager, and the reboot-db-cluster command), and instructs against inventing CloudWatch metric names or nonexistent features, deferring to bundled reference docs.

All Files

14 files
scripts/instance_types.py2.5 KB
View
SKILL.md16.9 KB
View
references/getting-started/instructions.md12.8 KB
View
references/migration/instructions.md4.0 KB
View
references/monitoring/instructions.md6.6 KB
View
references/monitoring/metrics.md8.8 KB
View
references/processing-engine/instructions.md6.5 KB
View
references/schema-design/instructions.md4.4 KB
View
references/troubleshooting/instructions.md5.4 KB
View
references/troubleshooting/s3-vpc-endpoint.md1.0 KB
View
scripts/check_vpc_endpoints.sh1.7 KB
View
scripts/get_token.sh1.9 KB
View
scripts/health_check.sh3.1 KB
View
scripts/input_validator.py1.7 KB
View

Install timestream-influxdb

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill