- Newest
- Most votes
- Most comments
For the question 1 .. I guess https://github.com/awslabs/amazon-timestream-tools/tree/mainline/integrations/kafka_connector is not updated. i added some logic to ignore database name & table for influxdb .. then those errors were gone...
But now in kafka connect getting the same error while writing data to influx.. [Worker-0117b930c66704a7f] com.influxdb.exceptions.InfluxException: connect timed out
Although when connector coming up.. it says [Worker-0117b930c66704a7f] [2025-05-19 08:24:24,529] INFO [influxdbconnector21|task-1] INFO::TimeStreamWriter:: influxDB client successfull connected: [https://6fcogbpelo-7gox52bqpwjkez.timestream-influxdb.eu-west-2.on.aws:8086] [databento_kf] [ea] (software.amazon.timestream.utility.TimestreamWriter:124)
issue is while writing it says connect time out.. any idea ? Basically i think withing vpc it is not able to connect to 8086 and getting timeout
answered a year ago
Regarding your questions about setting up Amazon Timestream for InfluxDB with Kafka Connect and Python, I can provide some clarification:
Question 1: For Timestream for InfluxDB, you don't need to specify a database name or table name in the same way as you would for Timestream LiveAnalytics. Instead, you should focus on the InfluxDB-specific parameters:
- timestream.influxdb.bucket: This is the InfluxDB bucket where your data will be stored.
- timestream.influxdb.org: This is your InfluxDB organization.
- timestream.influxdb.url: This should be the endpoint URL for your InfluxDB instance.
- timestream.influxdb.token: This is your InfluxDB authentication token.
You should remove or comment out the Timestream-specific parameters like timestream.database.name and timestream.table.name as they are not applicable for InfluxDB. The error you're seeing about the database not existing is likely because the connector is trying to use Timestream-specific configurations with InfluxDB.
Question 2: The connectivity issue you're facing is related to network configuration. Even though your EC2 instance and InfluxDB are in the same VPC, there are a few things to check:
-
Ensure that the security group attached to your InfluxDB instance allows inbound traffic on port 8086 from the security group of your EC2 instance.
-
Check that your EC2 instance's route table includes a route to the InfluxDB instance's private IP or subnet.
-
Verify that your VPC endpoint for Timestream InfluxDB is correctly configured and associated with the right subnets.
-
Make sure your EC2 instance has the correct DNS settings to resolve the InfluxDB endpoint within the VPC.
The fact that it works with the public IP suggests there might be an issue with internal DNS resolution or routing. To resolve this:
- Double-check your VPC's DNS settings.
- Ensure that your EC2 instance is using the VPC's DNS server.
- Try using the private IP address of the InfluxDB instance instead of its DNS name in your connection string.
If you still can't connect using the private IP, you may need to review your VPC configuration, including route tables and network ACLs, to ensure there are no restrictions preventing internal communication.
Remember, for production use, it's recommended to keep your InfluxDB instance private and use a bastion host or VPN for secure access to the UI, rather than making it publicly accessible.
Sources
Run and manage open source InfluxDB databases with Amazon Timestream | AWS News Blog
Creating and connecting to a Timestream for InfluxDB instance - Amazon Timestream
Use the AWS InfluxDB migration script to migrate your InfluxDB OSS 2.x data to Amazon Timestream for InfluxDB | AWS Database Blog
answered a year ago
Relevant content
asked a year ago
asked 2 years ago
asked 5 months ago
