AWS Database Blog
Timestream for InfluxDB 3 workload analysis and best practices
Selecting the right instance size for your Amazon Timestream for InfluxDB 3 deployment is one of the most impactful decisions you’ll make when architecting your time series infrastructure. An undersized instance can lead to degraded query performance and ingestion bottlenecks, while an oversized instance means paying for unused capacity. In this blog post we will […]
Features and workflows with Amazon Timestream for InfluxDB 3
This technical deep dive into Amazon Timestream for InfluxDB 3 explores the architectural decisions, features, and capabilities that make this release a significant evolution in time series database technology. This next-generation time series database represents is an architectural redesign from the previous engine version; built from the ground up with modern technologies including Rust for core performance, Apache Arrow for columnar data processing, Apache Parquet for efficient storage, and Apache Arrow Flight SQL for high-performance querying.
Monitor Amazon Timestream for InfluxDB performance using the Timestream for InfluxDB Metrics dashboard
The Timestream for InfluxDB Metrics dashboard adds the ability to perform trend analysis, create actionable insights, set up alerts, and automate reporting. You can configure the Timestream for InfluxDB Metrics dashboard to suit your business needs and build a robust and optimized time series workflow. In this post we walk you through how to deploy the Timestream for InfluxDB Metrics dashboard to start monitoring the performance of your fleet of Timestream for InfluxDB databases.
Improve Amazon Timestream for InfluxDB security posture by automating rotation for long-lived credentials
In this post, we walk you through how to make your Amazon Timestream for InfluxDB deployments more secure by offering a mechanism to automatically rotate long-lived credentials. We use AWS Secrets Manager to store your tokens and user credentials as secrets and rotate the secrets using the included AWS Lambda functions.



