Amazon Timestream

Name: Amazon Timestream
Brand: Amazon Web Services (AWS)
Rating: 3.8 (23 reviews)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B|1 Ref Customers

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

MarketsData Warehouses & Lakehouses Cloud Databases

Platform CoversInfrastructure Monitoring

Published Oct 13, 2026

01Common complaints

1. Net-new customers specifically seeking the LiveAnalytics engine - LiveAnalytics closed to new customer access effective June 20, 2025; new deployments should consider alternate engines or services. 2. Workloads that require near-zero idle cost and were relying on an earlier serverless model - Managed InfluxDB deployments involve baseline instance-hour costs; teams that previously benefited from serverless idle cost characteristics should validate cost behavior with InfluxDB deployments. 3. Workloads requiring simple, highly predictable pricing for ad-hoc analytics without compute-unit billing dynamics - Community reports indicate that compute-based query billing can be difficult to forecast for ad-hoc workloads. 4. Use cases requiring strong Postgres compatibility and relational joins - TimescaleDB/Timescale Cloud may simplify architectures where relational joins and Postgres tooling are primary requirements. 5. Requirements for vendor-neutral portability - Both Timestream engines are tied to AWS operational constructs; the InfluxDB engine may introduce Marketplace licensing considerations for some enterprise features.

Deal disqualifiers (poor fit)

New-customer adoption that requires the LiveAnalytics engine (no longer available to new customers since the mid-2020s).
Requirement for a single database combining relational joins and time-series operations without introducing additional systems (Timescale may be simpler in such cases).
Inability to tolerate pricing uncertainty or inability to perform production-like load testing to validate costs.

LiveAnalytics availability limitation (major)

Closed to new customers as of June 20, 2025. Existing workloads remain supported.

Pricing and cost-estimation challenges

Community discussions describe pricing complexity and reported increases after pricing model changes; buyers should perform workload-specific cost validation.

Query/function limitations (example)

Community notes have cited missing functions in certain query contexts; buyers should validate required functions for their workloads.

InfluxDB 3 licensing and billing complexity

InfluxDB 3 Enterprise deployments can include an additional per-vCPU license line item via AWS Marketplace; minimum storage and licensing considerations may apply and should be validated.

Roadmap ambiguity

AWS continues to state investment in security and availability, but the closure of new-customer access for LiveAnalytics introduces uncertainty for greenfield planning.

02Why they buy

Key differentiators supported by documented statements

AWS compliance scope: AWS states that Timestream is in scope for SOC reports and other compliance programs, which can be relevant for regulated buyers.
AWS-native integration patterns: monitoring and integration with AWS services reduce integration work for AWS-centric teams.
Managed InfluxDB option: provides a managed deployment path for the InfluxDB ecosystem on AWS-managed infrastructure.

Areas where competitors have clear advantages

Relational + time-series combinations: Timescale (Postgres) is often a better option when joins and relational integration are important.
SaaS simplicity: InfluxDB Cloud can be simpler for teams not standardized on AWS.
Lifecycle certainty: the LiveAnalytics availability change has created uncertainty for new-customer greenfield adoption; some competitors may be viewed as more stable options for greenfield projects.

Why customers chose Timestream (inferred)

Desire for an AWS-managed time-series store integrated with AWS IAM, VPC, and monitoring.
Requirement for time-series functions and performance compared to DIY approaches (for example, Postgres partitioning).
For the InfluxDB engine: preference for InfluxDB tooling (Telegraf, Flux/InfluxQL depending on version).

03Field reports

Review platform coverage (accessibility limitations)

G2 contains reviews for Amazon Timestream; some reviewers cite pricing concerns.
Gartner Peer Insights and TrustRadius may include AWS-wide pages; access to product-specific review content can be limited for automated crawls.

Community and practitioner sentiment (forums)

Community feedback is notable for Timestream because of LiveAnalytics availability changes and pricing discussions. Positive / value themes (community posts): - Some users appreciated the serverless model for intermittent IoT workloads because it reduced idle costs in certain usage patterns. - Integration with AWS-native pipelines (e.g., IoT Core, CloudWatch) is commonly cited in solution discussions. Negative themes / complaints (community posts): - Pricing unpredictability: threads describe reports of unexpected bill increases in some cases and concern about forecasting compute-based query costs. - Service direction concerns: changes to LiveAnalytics availability for new customers have been interpreted by some as a risk for long-term availability. - Feature and query ergonomics: some practitioners report missing functions or query ergonomics issues. - Operational mismatch for some customers: managed InfluxDB requires instance sizing and operational decisions that differ from a serverless model.

Why some customers left or considered alternatives

Pricing model changes and unpredictability for ad-hoc analytics.
Procurement and strategic risk due to LiveAnalytics availability changes impacting new-customer adoption.

AWS reference architectures (solution-level examples)

AWS reference architecture materials position Timestream as a storage option for telemetry and metering solutions.

Critical evaluation:

These are vendor reference architectures rather than independently audited customer case studies.
They illustrate integration patterns but do not provide independent ROI validation.

Vendor-authored technical content (migration / integration)

AWS technical blog posts describe migration approaches, retention policies, and operational patterns.

Critical evaluation:

Vendor-authored material is useful for operational guidance but should not be treated as independent performance validation.

InfluxDB 3 partnership materials

Vendor and partner announcements highlight performance claims and deployment options for InfluxDB 3 on AWS-managed infrastructure.

Critical evaluation:

Partner press releases provide claimed capabilities; buyers should request benchmarks and workload definitions and perform proof-of-concept testing for specific scale and cardinality needs.

04Best fit

Company size (practical guidance)

Mid-market to enterprise organizations (organizations with hundreds to many thousands of employees) that are standardized on AWS and have platform, SRE, or IoT engineering teams.
Smaller organizations may be suitable if they have AWS expertise and predictable time-series workloads, though cost forecasting should be validated.

Industries / verticals

Industrial IoT and manufacturing telemetry
Utilities and metering
SaaS infrastructure monitoring
E-commerce and clickstream analytics

Roles and personas

Decision makers: Head of Platform, VP Engineering, Data/Analytics leadership, Security and Compliance stakeholders
End users: SRE/DevOps, IoT engineers, data engineers, analytics engineers

Pain points addressed

High-ingest time-series storage and aggregation for analytics
Reducing operational burden for time-series database management (patching, backups, high availability)

Qualification criteria (good fit)

Organizations that are fully standardized on AWS networking and IAM and want to minimize the introduction of additional vendors.
Workloads that require time-series-specific queries (downsampling and aggregations) and where cost can be validated through testing or modeling.

05The pitch

What the product does (core value proposition)

Amazon Timestream is Amazon Web Services' managed time-series database offering. The product is offered as two distinct engines under the Timestream name: - Amazon Timestream for LiveAnalytics: the original AWS-built, serverless time-series database engine that supports SQL querying and is optimized for high ingest and fast analytical queries. - Amazon Timestream for InfluxDB: a managed service that runs InfluxDB (the open-source time-series database) on AWS, with AWS-managed operations and availability options. AWS documentation describes managed time-series ingestion and analytics, low-latency querying, and integration with AWS security and operations features. AWS also states that LiveAnalytics is closed to new customer sign-ups (see AWS availability notices).

Target market and market positioning

Primary users include teams already standardized on AWS that require a time-series datastore for: - IoT telemetry - DevOps / infrastructure metrics - Application and clickstream-like event analytics Positioning: - LiveAnalytics was positioned as a serverless database designed for near-real-time analytics at AWS scale. - Timestream for InfluxDB is positioned as a managed InfluxDB offering for teams that prefer the InfluxDB ecosystem and want AWS-managed operations.

Get a comprehensive analysis of Amazon Timestream including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 13, 2026

01Common complaints

Net-new customers specifically seeking the LiveAnalytics engine

LiveAnalytics closed to new customer access effective June 20, 2025; new deployments should consider alternate engines or services.

Workloads that require near-zero idle cost and were relying on an earlier serverless model

Managed InfluxDB deployments involve baseline instance-hour costs; teams that previously benefited from serverless idle cost characteristics should validate cost behavior with InfluxDB deployments.

Workloads requiring simple, highly predictable pricing for ad-hoc analytics without compute-unit billing dynamics

Community reports indicate that compute-based query billing can be difficult to forecast for ad-hoc workloads.

Use cases requiring strong Postgres compatibility and relational joins

TimescaleDB/Timescale Cloud may simplify architectures where relational joins and Postgres tooling are primary requirements.

Requirements for vendor-neutral portability

Both Timestream engines are tied to AWS operational constructs; the InfluxDB engine may introduce Marketplace licensing considerations for some enterprise features.

Deal disqualifiers (poor fit)

New-customer adoption that requires the LiveAnalytics engine (no longer available to new customers since the mid-2020s).
Requirement for a single database combining relational joins and time-series operations without introducing additional systems (Timescale may be simpler in such cases).
Inability to tolerate pricing uncertainty or inability to perform production-like load testing to validate costs.

LiveAnalytics availability limitation (major)

Closed to new customers as of June 20, 2025. Existing workloads remain supported.

Pricing and cost-estimation challenges

Community discussions describe pricing complexity and reported increases after pricing model changes; buyers should perform workload-specific cost validation.

Query/function limitations (example)

Community notes have cited missing functions in certain query contexts; buyers should validate required functions for their workloads.

InfluxDB 3 licensing and billing complexity

InfluxDB 3 Enterprise deployments can include an additional per-vCPU license line item via AWS Marketplace; minimum storage and licensing considerations may apply and should be validated.

Roadmap ambiguity

AWS continues to state investment in security and availability, but the closure of new-customer access for LiveAnalytics introduces uncertainty for greenfield planning.

02Why they buy

Key differentiators supported by documented statements

AWS compliance scope: AWS states that Timestream is in scope for SOC reports and other compliance programs, which can be relevant for regulated buyers.
AWS-native integration patterns: monitoring and integration with AWS services reduce integration work for AWS-centric teams.
Managed InfluxDB option: provides a managed deployment path for the InfluxDB ecosystem on AWS-managed infrastructure.

Areas where competitors have clear advantages

Relational + time-series combinations: Timescale (Postgres) is often a better option when joins and relational integration are important.
SaaS simplicity: InfluxDB Cloud can be simpler for teams not standardized on AWS.
Lifecycle certainty: the LiveAnalytics availability change has created uncertainty for new-customer greenfield adoption; some competitors may be viewed as more stable options for greenfield projects.

Why customers chose Timestream (inferred)

Desire for an AWS-managed time-series store integrated with AWS IAM, VPC, and monitoring.
Requirement for time-series functions and performance compared to DIY approaches (for example, Postgres partitioning).
For the InfluxDB engine: preference for InfluxDB tooling (Telegraf, Flux/InfluxQL depending on version).

03Field reports

Review platform coverage (accessibility limitations)

G2 contains reviews for Amazon Timestream; some reviewers cite pricing concerns.
Gartner Peer Insights and TrustRadius may include AWS-wide pages; access to product-specific review content can be limited for automated crawls.

Community and practitioner sentiment (forums)

Community feedback is notable for Timestream because of LiveAnalytics availability changes and pricing discussions.

Positive / value themes (community posts):

Some users appreciated the serverless model for intermittent IoT workloads because it reduced idle costs in certain usage patterns.
Integration with AWS-native pipelines (e.g., IoT Core, CloudWatch) is commonly cited in solution discussions.

Negative themes / complaints (community posts):

Pricing unpredictability: threads describe reports of unexpected bill increases in some cases and concern about forecasting compute-based query costs.
Service direction concerns: changes to LiveAnalytics availability for new customers have been interpreted by some as a risk for long-term availability.
Feature and query ergonomics: some practitioners report missing functions or query ergonomics issues.
Operational mismatch for some customers: managed InfluxDB requires instance sizing and operational decisions that differ from a serverless model.

Why some customers left or considered alternatives

Pricing model changes and unpredictability for ad-hoc analytics.
Procurement and strategic risk due to LiveAnalytics availability changes impacting new-customer adoption.

AWS reference architectures (solution-level examples)

AWS reference architecture materials position Timestream as a storage option for telemetry and metering solutions.

Critical evaluation:

These are vendor reference architectures rather than independently audited customer case studies.
They illustrate integration patterns but do not provide independent ROI validation.

Vendor-authored technical content (migration / integration)

AWS technical blog posts describe migration approaches, retention policies, and operational patterns.

Critical evaluation:

Vendor-authored material is useful for operational guidance but should not be treated as independent performance validation.

InfluxDB 3 partnership materials

Vendor and partner announcements highlight performance claims and deployment options for InfluxDB 3 on AWS-managed infrastructure.

Critical evaluation:

Partner press releases provide claimed capabilities; buyers should request benchmarks and workload definitions and perform proof-of-concept testing for specific scale and cardinality needs.

04Best fit

Company size (practical guidance)

Mid-market to enterprise organizations (organizations with hundreds to many thousands of employees) that are standardized on AWS and have platform, SRE, or IoT engineering teams.
Smaller organizations may be suitable if they have AWS expertise and predictable time-series workloads, though cost forecasting should be validated.

Industries / verticals

Industrial IoT and manufacturing telemetry
Utilities and metering
SaaS infrastructure monitoring
E-commerce and clickstream analytics

Roles and personas

Decision makers: Head of Platform, VP Engineering, Data/Analytics leadership, Security and Compliance stakeholders
End users: SRE/DevOps, IoT engineers, data engineers, analytics engineers

Pain points addressed

High-ingest time-series storage and aggregation for analytics
Reducing operational burden for time-series database management (patching, backups, high availability)

Qualification criteria (good fit)

Organizations that are fully standardized on AWS networking and IAM and want to minimize the introduction of additional vendors.
Workloads that require time-series-specific queries (downsampling and aggregations) and where cost can be validated through testing or modeling.

05The pitch

What the product does (core value proposition)

Amazon Timestream is Amazon Web Services' managed time-series database offering. The product is offered as two distinct engines under the Timestream name:

Amazon Timestream for LiveAnalytics: the original AWS-built, serverless time-series database engine that supports SQL querying and is optimized for high ingest and fast analytical queries.
Amazon Timestream for InfluxDB: a managed service that runs InfluxDB (the open-source time-series database) on AWS, with AWS-managed operations and availability options.

AWS documentation describes managed time-series ingestion and analytics, low-latency querying, and integration with AWS security and operations features. AWS also states that LiveAnalytics is closed to new customer sign-ups (see AWS availability notices).

Target market and market positioning

Primary users include teams already standardized on AWS that require a time-series datastore for:

IoT telemetry
DevOps / infrastructure metrics
Application and clickstream-like event analytics

Positioning:

LiveAnalytics was positioned as a serverless database designed for near-real-time analytics at AWS scale.
Timestream for InfluxDB is positioned as a managed InfluxDB offering for teams that prefer the InfluxDB ecosystem and want AWS-managed operations.

Get a comprehensive analysis of Amazon Timestream including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →