Timestream stores IoT readings and telemetry as tables of dimensions, measures, and timestamps. DbSchema connects over the official JDBC driver and diagrams those tables, so which dimensions describe each series — and which measures it records — stops being guesswork.
bin() and date_trunc() bucketing in the SQL editor firstTrusted by teams at
A serverless time-series database has no tables to design up front — dimensions and measures simply appear as devices write them. Six months in, the only definition of "the schema" is scattered across the services that ingest telemetry.
DbSchema reads what Timestream actually stores and puts it on a diagram: every table, its dimensions, its measures — visible instead of inferred.
From raw telemetry tables to a schema the whole team reads.
Connect to a Timestream database and DbSchema renders its tables with dimensions and measures laid out — the data model your ingestion pipeline produced, made visible.
Write ago(), bin(), and date_trunc() queries with table and column completion, check the execution time, then carry the working SQL into application code.
Group related tables into layouts per device fleet, dashboard, or metric family, and annotate columns so units and meaning travel with the diagram.
What DbSchema learns about your Timestream tables lands in a design model — a local file that documents the telemetry schema independently of any AWS session.
Open the model in a review meeting or on the train — no credentials, no console.
Commit the model beside the ingestion service, so schema and code travel together.
Comment dimensions and measures with units and meaning right where readers look.
Produce HTML or PDF documentation for engineers who lack AWS access entirely.
Add the Amazon Timestream JDBC driver
(software.amazon.timestream.jdbc.TimestreamDriver) to DbSchema's driver
configuration, then connect with a URL like
jdbc:timestream://Region=us-east-1;Database=mydb. Timestream is region-scoped, so
the region must match where the database was created. Authentication uses an AWS access key pair
entered in the connection dialog, or an IAM role profile configured on the machine; traffic runs
over HTTPS on port 443.
Download free, skip the signup, and try the Architect features for 15 days.
Teams working with Amazon Timestream often use these engines too. Explore dedicated guides and JDBC setup for each.