# Timestream for InfluxDB

- **Docs**: https://docs.aws.amazon.com/timestream/
- **Docs (llms.txt)**: https://docs.aws.amazon.com/timestream/latest/developerguide/llms.txt
- **Data model**: Time-series (measurements, tags, fields, timestamps — line protocol)
- **Query language**: SQL + InfluxQL (v3); Flux + InfluxQL (v2)
- **Compatibility**: InfluxDB wire protocol (Telegraf, Grafana, Flight SQL)
- **Serverless**: No (instance/cluster-based)
- **Scale to zero**: No
- **VPC required**: Yes (private by default; public opt-in)
- **Multi-region**: No
- **Free Tier**: No
- **Min cost**: ~$95/month (db.influx.medium, on-demand)
- **Time to first query**: ~15-25 min (instance provisioning)
- **Engine variants**: InfluxDB 2 (single-node/read replica, Flux, port 8086), InfluxDB 3 Core/Enterprise (multi-node, SQL, port 8181)
- **V2 key features**: Built-in UI, Flux task engine, Telegraf integration, org/bucket multi-tenancy, read replicas for read scaling
- **V2 limitations**: Cardinality degrades above ~10M series, no SQL, no horizontal write scaling, max practical storage ~2TB
- **V3 key features**: Unlimited cardinality, Processing Engine (Python plugins), S3-backed Parquet storage, horizontal scaling up to 15 nodes, open data format (Parquet/Iceberg)
- **V3 limitations**: No Flux (must rewrite), no built-in UI, no scale-to-zero
- **Best for**: High-frequency IoT telemetry, DevOps/infrastructure metrics, industrial sensor data, satellite telemetry, financial time-series, high-cardinality workloads (>10M series) (v3), SQL analytics over time-series (v3), self-hosted InfluxDB migration (v2)
- **Not for**: General-purpose relational data, workloads needing JOINs/transactions, sub-millisecond key-value lookups, workloads needing $0 idle cost