- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
When using Telegraf with Amazon Timestream for InfluxDB, you'll need to manage certificate files on the system where Telegraf is running, not within the InfluxDB instance itself.
Amazon Timestream for InfluxDB is a managed service that provides access to InfluxDB capabilities, but it doesn't provide direct file system access for uploading certificate files. The certificates needed by Telegraf plugins should be stored on the host system where your Telegraf agent is running.
For Telegraf configuration with Timestream for InfluxDB, you would:
- Install Telegraf on your host system (server, EC2 instance, etc.)
- Store any required certificates on that host's file system
- Configure Telegraf to reference those local certificate paths in your configuration file
- Connect Telegraf to your Timestream for InfluxDB instance using the endpoint, organization, and authentication details
When configuring Telegraf to write to Timestream for InfluxDB, you'll need to provide connection details like the endpoint URL, organization name, and authentication token, but certificate files remain on the Telegraf host system.
Sources
Simplify Industrial IoT: Use InfluxDB edge replication for centralized time series analytics with Amazon Timestream | AWS Database Blog
What is Timestream for InfluxDB? - Amazon Timestream
Run and manage open source InfluxDB databases with Amazon Timestream | AWS News Blog
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
