Amazon Timestream is a fast, scalable database service that helps you store and analyze time-series data for applications like Internet of Things (IoT) and real-time monitoring. With Timestream, you can set up, operate, and scale time-series databases in the cloud in only a few steps. Timestream offers a choice of fully managed, time-series database engines for workloads from low-latency queries to large-scale data ingestion.
Timestream provides both serverless and instance-based configurations, supporting a variety of operational needs. Its pay-for-use and on-demand pricing model provides the maximum flexibility and cost efficiency, allowing you to choose the database engine and configuration that well suits your specific requirements. Whether scaling up for high performance or optimizing for cost reduction, the customizable approach of Timestream allows you to select the ideal time-series database engine for your workload. You only pay for the resources you use, making it an ideal solution for dynamic and efficient data management.
Amazon Timestream for InfluxDB
Amazon Timestream for InfluxDB is a managed, highly available, open source, time-series database that makes it simple to set up, operate, and scale InfluxDB instances in the cloud. On-demand database (DB) instances allow you to pay for compute capacity per hour that your database instance runs with no long-term commitments. This frees you from the costs and complexities of planning, purchasing, and maintaining hardware. Your database instance and storage charges are based on the configurations you choose.
Pricing by database instances
Timestream for InfluxDB supports both Single-AZ and Multi-AZ deployments, optimized instance classes, and storage types that you can choose to match your workload requirements.
- For both Single-AZ and Multi-AZ deployments, pricing is per DB instance-hour consumed from the time a database instance is launched until it is stopped or deleted.
- For Multi-AZ deployments, instance charges apply to both Timestream for InfluxDB primary instances and secondary replicas.
- For partial DB instance-hours, they are billed in 1-second increments with a 10-minute minimum charge after a billable status change, such as creating, starting, or modifying the DB instance class.
Single-AZ | |||||
Instance Class | vCPU | Memory | Network Performance | Price per Hour (Ningxia) | Price per Hour (Beijing) |
db.influx.medium | 1 | 8 GiB | Up to 10 Gigabyte | ¥0.716 | ¥1.214 |
db.influx.large | 2 | 16 GiB | Up to 10 Gigabyte | ¥1.432 | ¥2.428 |
db.influx.xlarge | 4 | 32 GiB | Up to 10 Gigabyte | ¥2.863 | ¥4.857 |
db.influx.2xlarge | 8 | 64 GiB | Up to 10 Gigabyte | ¥5.727 | ¥9.713 |
db.influx.4xlarge | 16 | 128 GiB | Up to 10 Gigabyte | ¥11.454 | ¥19.426 |
db.influx.8xlarge | 32 | 256 GiB | Up to 10 Gigabyte | ¥22.907 | ¥38.852 |
db.influx.12xlarge | 48 | 384 GiB | Up to 10 Gigabyte | ¥34.361 | ¥58.279 |
db.influx.16xlarge | 64 | 512 GiB | Up to 10 Gigabyte | ¥45.814 | ¥77.705 |
Multi-AZ | |||||
Instance Class | vCPU | Memory | Network Performance | Price per Hour (Ningxia) | Price per Hour (Beijing) |
db.influx.medium | 1 | 8 GiB | Up to 10 Gigabyte | ¥1.432 | ¥2.428 |
db.influx.large | 2 | 16 GiB | Up to 10 Gigabyte | ¥2.863 | ¥4.857 |
db.influx.xlarge | 4 | 32 GiB | Up to 10 Gigabyte | ¥5.727 | ¥9.713 |
db.influx.2xlarge | 8 | 64 GiB | Up to 10 Gigabyte | ¥11.454 | ¥19.426 |
db.influx.4xlarge | 16 | 128 GiB | Up to 10 Gigabyte | ¥22.907 | ¥38.852 |
db.influx.8xlarge | 32 | 256 GiB | Up to 10 Gigabyte | ¥45.814 | ¥77.705 |
db.influx.12xlarge | 48 | 384 GiB | Up to 10 Gigabyte | ¥69.985 | ¥116.557 |
db.influx.16xlarge | 64 | 512 GiB | Up to 10 Gigabyte | ¥91.629 | ¥155.410 |
Pricing by database storage
Database storage is billed per gigabyte per month. The amount is determined by the selected storage type and allocated storage volume for the database. Timestream for InfluxDB databases support the following storage types:
Influx I/O-included storage: This storage option is designed to meet the needs of your most I/O-intensive InfluxDB time-series workloads. There are three options to choose from: Influx I/O-included storage with 3K IOPS included (minimum size 20 GiB), Influx I/O-included storage 12K IOPS (minimum size 400 GiB), and Influx I/O-included storage 16K IOPS (minimum size 400 GiB).
Single-AZ | |||
Storage Tier | Included IOPS | Per GB month (Ningxia) | Per GB month (Beijing) |
Influx IO Included (3K) | 3000 | ¥0.695 | ¥1.053 |
Influx IO Included (12K) | 12000 | ¥2.421 | ¥3.579 |
Influx IO Included (16K) | 16000 | ¥3.460 | ¥5.123 |
Multi-AZ | |||
Storage Tier | Included IOPS | Per GB month (Ningxia) | Per GB month (Beijing) |
Influx IO Included (3K) | 3000 | ¥1.404 | ¥2.105 |
Influx IO Included (12K) | 12000 | ¥4.913 | ¥7.159 |
Influx IO Included (16K) | 16000 | ¥7.018 | ¥10.246 |
Data transfer pricing
Data transferred between Timestream for InfluxDB and Amazon EC2 instances in the same Availability Zone:
Free.
Data transferred between Availability Zones for replication of Multi-AZ deployments:
Free.
Timestream for InfluxDB instances outside VPC:
Data transferred between an EC2 instance and Timestream for InfluxDB instance in different Availability Zones of the same Amazon Web Services Region have no data transfer charge for traffic in or out of the Timestream for InfluxDB instance. You are only charged for the data transfer in or out of the EC2 instance and standard EC2 Regional Data Transfer charges apply (¥.070 per GiB in/out).
Timestream for InfluxDB instances inside VPC:
For data transferred between an EC2 instance and a Timestream for InfluxDB instance in different Availability Zones of the same Region, EC2 Regional Data Transfer charges apply on both sides of transfer.
Amazon Web Services China (Ningxia) Region, operated by NWCD | Amazon Web Services China (Beijing) Region, operated by Sinnet | ||
Data Transfer IN to Timestream From | Internet | ¥ 0.000 per GB | ¥ 0.000 per GB |
Amazon S3, Amazon Glacier, Amazon DynamoDB, Amazon SageMaker, Amazon SQS in the same Amazon Web Services Region | ¥ 0.000 per GB | ¥ 0.000 per GB | |
Amazon EC2, Amazon RDS, Amazon Redshift or Amazon ElastiCache instances, Elastic Load Balancing, or Elastic Network Interfaces in the same Availability Zone | see below | see below | |
Using a private IP address | ¥ 0.000 per GB | ¥ 0.000 per GB | |
Using a public or Elastic IP address | ¥ 0.067 per GB | ¥ 0.067 per GB | |
Amazon EC2, Amazon RDS, Amazon Redshift or Amazon ElastiCache instances, Elastic Load Balancing, or Elastic Network Interfaces in another Availability Zone in the same Amazon Web Services Region | ¥ 0.067 per GB | ¥ 0.067 per GB | |
Data Transfer OUT from Timestream To | Internet | ¥ 0.933 per GB (Promotional) | ¥ 0.933 per GB (Promotional) |
Amazon S3, Amazon Glacier, Amazon DynamoDB, Amazon SageMaker, Amazon SQS in the same Amazon Web Services Region | ¥ 0.000 per GB | ¥ 0.000 per GB | |
Amazon EC2, Amazon RDS, Amazon Redshift or Amazon ElastiCache instances, Elastic Load Balancing, or Elastic Network Interfaces in the same Availability Zone | see below | see below | |
Using a private IP address | ¥ 0.000 per GB | ¥ 0.000 per GB | |
Using a public or Elastic IP address | ¥ 0.067 per GB | ¥ 0.067 per GB | |
Amazon EC2, Amazon RDS, Amazon Redshift or Amazon ElastiCache instances, Elastic Load Balancing, or Elastic Network Interfaces in another Availability Zone in the same Amazon Web Services Region | ¥ 0.067 per GB | ¥ 0.067 per GB | |
Inter Region Data Transfer | Data transferred between the China (Beijing) and China (Ningxia) Regions | ¥ 0.6003 per GB | ¥ 0.6003 per GB |
Free Tier
As part of the Amazon Web Services Free Tier, you can get started with Timestream for LiveAnalytics for free. Upon sign-up, new customers receive 50 GB for data ingestion, 100 GB of Magnetic tier storage, 750 GB-hour of Memory tier storage, and 24 TCU-hours for query usage during a 1-month free trial of Timestream for LiveAnalytics.
Pricing examples (Based on Amazon Web Services China (Ningxia) Region, operated by NWCD)
Real-time infrastructure monitoring for uninterruptible power supply systems using Timestream for InfluxDB
Envision a real-time infrastructure monitoring system designed for managing over 5,000 uninterruptible power supply (UPS) devices. This system is geared towards analyzing vital metrics in real time to ensure the reliability and efficiency of these devices.
Each UPS device transmits data every 10 seconds. This data encompasses 5 key fields: input/output voltages, load capacity, temperature, and battery charge level. Alongside these fields, each data packet includes four essential tags—deviceId, deviceModel, location, and manufacturer—adding layers of contextual information to the metrics.
The monitoring process is executed through a sophisticated dashboard system. These dashboards are programmed to refresh every 60 seconds and run a total of 15 queries in each cycle. This setup provides a near real-time view of the status and performance of all connected UPS devices, allowing for timely decisions and actions.
Another important feature of this system is its automated anomaly detection capability. Tasks are set to run every 10 seconds, meticulously scanning the incoming data for any deviations from predefined thresholds. Upon detecting any anomalies, the system promptly triggers alerts, ensuring immediate attention to potential issues.
To support the demands of this extensive data processing and real-time monitoring system, a robust database infrastructure is essential. A db.influx.2xlarge instance equipped with 400 GiB of Influx I/O-included storage and capable of handling 3,000 IOPS would be ideal for this workload.
Single-AZ deployment cost (monthly)
- Compute cost: ¥4,897.83
Based on a db.influx.2xlarge instance
Operating 24 hours for every day in a month
Rate: ¥6.709 per hour
Total hours: 730 (1 month)
- Storage cost: ¥280.726
400 GiB Influx I/O-included storage (3K IOPS)
Rate: ¥0.10 per GB-month
Single-AZ configuration
- Total monthly cost: ¥5,178.553
Multi-AZ deployment cost (monthly)
- Compute cost: ¥9,800.776
Based on Multi-AZ db.influx.2xlarge instance
Operating 24 hours for every day in a month
Rate: ¥13.246 per hour
Total hours: 730 (1 month)
- Storage cost: ¥561.452
400 GiB Influx I/O-included storage (3K IOPS)
Rate: ¥1.404 per GB-month
Multi-AZ setup
- Total monthly cost: ¥10,362.228
Real-time IoT monitoring for home security systems using Timestream for InfluxDB
Consider a real-time security monitoring service designed for a network of over 80,000 IoT home automation and security customers. Every 60 seconds, the home control central unit sends a comprehensive set of data, comprising 6 tags and 15 fields, to an InfluxDB-based database system.
The data received from these central units is aggregated and analyzed at a larger scale to generate insightful trend reports and recommendations. These reports and recommendations are then provided to end users, aiding them in optimizing their home security and automation setups.
Besides the routine data, the home devices also generate a distinct category of real-time events, particularly focused on security aspects. These security events are monitored in real time by a specialized control center. The control center is equipped with advanced dashboards that run approximately 50 queries, refreshing every 30 seconds. This setup offers a near-instantaneous overview of the security status across all connected homes.
Additionally, the system is designed to automatically scrutinize certain types of events at 5-second intervals. This feature allows for the generation of immediate automated notifications to external systems when specific conditions are met, significantly enhancing the system's responsiveness in security matters.
To accommodate these continuous data processing requirements, along with real-time security event monitoring, a robust database infrastructure is necessary. A db.influx.8xlarge instance, outfitted with 600 GiB of Influx I/O-included storage configured with 12,000 IOPS, would be well-suited to handle this workload.
Single-AZ deployment cost (monthly)
- Compute cost: ¥19,596.429
Based on db.influx.8xlarge instance
Operating 24 hours every day for a month
Rate: ¥26.884 per hour
Total hours: 730 (1 month)
- Storage cost: ¥1,473.812
600 GiB of Influx I/O-included storage (12K IOPS)
Rate: ¥2.456 GB-month
Single-AZ configuration
- Total monthly cost: ¥21,070.241
Multi-AZ deployment cost (monthly)
- Compute cost: ¥31,192.241
Based on Multi-AZ db.influx.8xlarge instance
Operating 24 hours every day for a month
Rate: ¥53.689 per hour
Total hours: 730 (1 month)
- Storage cost: ¥2,947.623
600 GiB Influx I/O-included storage (12K IOPS)
Rate: ¥4.913 per GB-month Multi-AZ setup
- Total monthly cost: ¥42,140.482
Ecommerce user behavior analytics using Timestream for InfluxDB
Consider a moderately sized ecommerce platform with a focus on optimizing conversion rates through user behavior analysis. The website boasts a user base of 4 million registered individuals with approximately 200,000 active daily users. This activity translates into approximately 10 million events each day.
The website's telemetry system is designed to capture real-time events, each generating records that consist of 8 tags and 3 fields. User identification is achieved through a combination of user IDs (which can be either known or anonymous), device type, and UTM tags. Meanwhile, each telemetry event is characterized by three main attributes: the type of event, the time it takes to load, and the source of the event (such as ads, reviews, or searches).
This rich time-series dataset is then aggregated and analyzed to enhance various aspects of the user experience including optimizing product recommendations, rotating ads, and strategically placing banners. The system performs over 100 queries every 5 minutes, leading to diverse types of data aggregations. These aggregations are essential for the continuous updating and optimization of machine learning models.
A db.influx.16xlarge instance configured with 800 GiB of Influx I/O-included storage capable of 16,000 IOPS would be suitable to handle the workload.
Single-AZ deployment cost (monthly)
- Compute cost: ¥39,192.859
Based on db.influx.16xlarge instance
Operating 24 hours for every day in a month
Rate: ¥53.689 per hour
Total hours: 730 (1 month)
- Storage cost: ¥2,807.260
800 GiB of Influx I/O-included storage (16K IOPS)
Rate: ¥3.509 per GB-month
Single-AZ configuration
- Total monthly cost: ¥42,000.119
Multi-AZ deployment cost (monthly)
- Compute cost: ¥78,385.717
Based on Multi-AZ db.influx.16xlarge instance
Operating 24 hours for every day in a month
Rate: ¥107.378 per hour
Total hours: 730 (1 month)
- Storage cost: ¥5,614.520
800 GiB Influx I/O-included storage (16K IOPS)
Rate: ¥7.018 per GB-month
Multi-AZ setup
- Total monthly cost: ¥84,000.237
Disclaimer:
Amazon Timestream offers two engines, InfluxDB and LiveAnalytics, both of which are covered in our product page and relevant documentation to provide comprehensive information. Please note: Currently, only Amazon Timestream for InfluxDB is available in the Amazon Web Services China (Beijing) Region, operated by Sinnet and the Amazon Web Services China (Ningxia) Region, operated by NWCD. All content related to LiveAnalytics in the product page and relevant documentation of Amazon Timestream is reserved for future developments, and such content should not be construed as part of the current service content of Amazon Timestream and is not legally binding.