Timestream for InfluxDB

In the previous lesson, you explored LiveAnalytics advanced features such as scheduled queries, rollups, and pre-aggregation patterns that power operational analytics at scale. Now the focus shifts to the other branch of the Amazon Timestream family, which takes a fundamentally different approach to running time-series workloads on AWS. Instead of a serverless, AWS-native analytics engine, Amazon Timestream for InfluxDB delivers a fully managed service that runs the InfluxDB engine on AWS infrastructure, preserving the open-source ecosystem that many teams already depend on.

This distinction matters more than it might seem at first glance. Organizations that have invested in Telegraf agents for metric collection, Flux queries for data transformation, line protocol for high-throughput writes, and InfluxDB dashboards for operational visibility can adopt Timestream for InfluxDB without rewriting application code or replacing tooling. AWS provisions, patches, and backs up actual DB instanceA cloud-hosted database environment that runs a specific database engine (in this case, InfluxDB) on compute and storage resources managed by AWS. resources running the InfluxDB engine, so the operational burden of OS maintenance, storage management, and backup orchestration shifts entirely to the platform.

Note: Timestream for InfluxDB is a managed-engine model, not a serverless abstraction. You select and size DB instances explicitly, which means capacity planning is part of the operational workflow.

Throughout this lesson, you will unpack the key concepts that define this service: DB instances and instance classes, the Influx API and InfluxDB UI as the sole interaction surfaces, VPC-based private networking, read replica clusters for scale and availability, and automated backups for durability. Each of these concepts maps directly to design decisions you will encounter in both real-world architecture and exam scenarios.

With this high-level structure in mind, the next step is to understand the fundamental operational unit that underpins the entire service.

DB instances and instance classes

The fundamental operational unit in Timestream for InfluxDB is the DB instance, a cloud-hosted environment running the InfluxDB engine on AWS-managed compute and storage. Unlike LiveAnalytics, where capacity is fully abstracted behind a serverless model and you pay per query and ingest volume, Timestream for InfluxDB requires you to choose an instance classA predefined combination of CPU, memory, and network capacity that determines the performance characteristics of a DB instance, similar to selecting an instance type in Amazon RDS. that determines the compute, memory, and network resources available to the engine. ...