What problem does it solve?
Working with Amazon Timestream for InfluxDB involves navigating three distinct engine variants (InfluxDB 2, V2 Read Replica Clusters, and InfluxDB 3) with different ports, APIs, IAM requirements, and monitoring coverage, where mistakes like mixing V2 and V3 APIs or missing Marketplace subscriptions cause provisioning failures.
Core Features & Use Cases
- Engine Selection & Provisioning: Guides selection between InfluxDB 2, V2 Read Replica Clusters, and InfluxDB 3 Core/Enterprise, including Marketplace subscription, IAM policy, and VPC/security group prerequisites.
- Schema Design & Migration: Advises on tag vs field decisions, cardinality management, partition templates, and migration from Timestream for LiveAnalytics using the certified migration plugin.
- Operations & Troubleshooting: Covers CloudWatch alarm setup, maintenance windows, Processing Engine plugins, and diagnosis of connection, write, and query errors.
- Use Case: A user wants to deploy a new time-series workload on AWS. The skill recommends InfluxDB 3, walks through Marketplace subscription and cluster creation with correct tagging, retrieves the Bearer token from Secrets Manager, and configures security groups for port 8181.
Quick Start
Ask the assistant to help you create a new Amazon Timestream for InfluxDB 3 cluster in your VPC, including the required IAM policies, security group rules, and token retrieval.