Amazon Timestream for InfluxDB 3 now supports customer plugins
Amazon Timestream for InfluxDB now lets you run your own Python plugins on the managed InfluxDB 3 processing engine, on both Core and Enterprise editions. You host your plugin code in a repository you control — public or private — and the engine fetches and runs it in response to triggers, so you can implement logic specific to your workload without standing up separate external infrastructure.
Plugins run on the trigger types the processing engine already supports: data writes, schedules, and HTTP requests. This lets you build custom data transformations, alerting, aggregation, and integrations with your own services, running close to your data. Plugins execute in a managed Python environment that includes the standard library and Amazon-vetted packages such as numpy, pandas, and many others.
To use custom plugins, you set a plugin repository on a DB parameter group, apply that parameter group to your cluster, and create triggers that reference your plugin using the influxdb3 CLI or HTTP API. Private repositories are authenticated with a token stored in Amazon Secrets Manager.
Custom plugins are available in the Amazon Web Services China (Beijing) Region, operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, operated by NWCD. There is no additional Timestream for InfluxDB charge for using customer managed keys. Standard KMS charges apply. To get started, open the Amazon Timestream console. For setup requirements and supported resources, see the Amazon Timestream for InfluxDB documentation. For service pricing, see the Amazon Timestream pricing page.