All Services

Database

Amazon Timestream

Amazon Timestream for LiveAnalytics is a serverless time-series database with automatic time-based storage tiering and SQL analytics for operational, IoT, and application telemetry.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Timestream.

Amazon Timestream pricing and cost programs

Pricing model: Serverless time-series usage

On-Demand
Available
Reserved Instances or reserved capacity
Service-specific
Savings Plans
Service-specific
Spot
Not applicable

Billing dimensions: Writes · Queries or compute units · Memory and magnetic storage

Programs and modes: Timestream for LiveAnalytics · Timestream for InfluxDB

LiveAnalytics and InfluxDB are distinct offerings with different capacity and pricing models.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Timestream?

  • Stores time-series records in memory and magnetic tiers without provisioning database servers or manually partitioning by time.
  • Provides SQL queries, interpolation and time-series functions, scheduled queries, retention controls, and integrations for operational analytics.
  • Scales ingestion, storage, and query independently for variable telemetry from applications, infrastructure, and connected devices.

How to implement Amazon Timestream

  1. Model stable dimensions, measure names or multi-measure records, timestamps, units, and expected late-arrival windows before creating the database and tables.
  2. Set memory and magnetic retention from query latency and cost requirements, enable magnetic-store writes for acceptable late data, and grant producers narrowly scoped write access.
  3. Batch records efficiently, create scheduled queries for recurring aggregates, secure consumers, and validate ingestion errors, rejected records, query plans, dashboards, and retention behavior.

Amazon Timestream best practices

  • Use multi-measure records for related metrics at the same timestamp, batch writes with shared dimensions, and avoid unnecessarily high-cardinality dimensions.
  • Keep only latency-sensitive data in memory, move longer history to magnetic storage, and precompute frequently reused rollups with scheduled queries.
  • Handle rejected records and retries explicitly, prevent duplicate or stale version writes, and monitor ingestion, throttling, query bytes, latency, errors, and scheduled-query failures.

Amazon Timestream use cases and server impact

  • IoT sensor and industrial telemetry
  • Application and infrastructure metrics
  • Near-real-time operational dashboards and anomaly features

Replaces time-series database hosts and manual hot/cold tiering, while data modeling, retention, ingestion backpressure, and query efficiency remain workload concerns.

Official implementation resources

Commonly paired AWS services