AWS InfluxDB to AWS managed Grafana connection problem

Question

**Conclusion of my problem:** I have AWS timestream for InfluxDB and AWS managed Grafana. I cannot connect the database to the Grafana. Both of the services are in same VPC and subnets and security groups. The security groups inbound/outbound rules allows all traffic needed. When i am trying to connect to database it gives me this error: **Post "https://(myInfluxDBInstance).timestream-influxdb.eu-central-1.on.aws:8086/api/v2/query?org=kossi-org": dial tcp MyIpAddress:8086: i/o timeout error reading buckets.** When I am trying to connect the AWS InfluxDB to local Grafana, the data source is working. But the goal is to connect the DB to the AWS managed Grafana. InfluxDB bucket name, org-name and Token is correctly configured. **What could be the problem here?** Also i have tried to connect InfluxDB to Grafana Cloud but it won't work either.

Regards,
Jaku

re:Post Agent · Answer

Based on your description, the issue appears to be related to network connectivity between your Amazon Managed Grafana workspace and your Timestream for InfluxDB instance, despite being in the same VPC.

When you see an "i/o timeout" error, it typically indicates that the connection attempt is being blocked or timing out at the network level. Here are some potential causes and solutions:

1. **VPC Configuration**: Even though both services are in the same VPC, Amazon Managed Grafana requires a specific VPC connection setup. Amazon Managed Grafana needs to create connections (using elastic network interfaces) per subnet to connect to your VPC. Make sure you've properly configured the VPC connection for your Grafana workspace.

2. **Security Group Rules**: Although you mentioned security groups allow all needed traffic, double-check that the security group associated with your Managed Grafana workspace's VPC connection allows outbound traffic to port 8086, and the security group for your InfluxDB instance allows inbound traffic from the Grafana security group on port 8086.

3. **Routing Configuration**: Ensure that the route tables in your VPC are correctly configured to allow traffic between the subnets where Grafana and InfluxDB are deployed.

4. **Availability Zone Considerations**: Amazon Managed Grafana requires at least two Availability Zones with one private subnet in each when connecting to a VPC. Verify that your VPC setup meets this requirement.

5. **IP Address Availability**: Each subnet used for the VPC connection must have at least 15 available IP addresses. Check if your subnets have sufficient IP addresses available.

Since your local Grafana can connect to the InfluxDB instance but AWS Managed Grafana cannot, this strongly suggests a network/VPC configuration issue rather than an authentication or configuration problem with InfluxDB itself.

Try reviewing your Amazon Managed Grafana VPC connection settings and ensure that all prerequisites for VPC connectivity are met. You might need to check the VPC connection status in the Amazon Managed Grafana console to verify it's properly established.  
**Sources**  
[Connect to data sources or notification channels in Amazon VPC from Amazon Managed Grafana - Amazon Managed Grafana](https://docs.aws.amazon.com/grafana/latest/userguide/AMG-configure-vpc.html)  
[Grafana - Amazon Timestream](https://docs.aws.amazon.com/timestream/latest/developerguide/other-services-influxdb-grafana.html)  
[Connect to an InfluxDB data source - Amazon Managed Grafana](https://docs.aws.amazon.com/grafana/latest/userguide/using-influxdb-in-AMG.html)

AWS InfluxDB to AWS managed Grafana connection problem

Add your answer

Relevant content