AWS Managed Grafana Query Timeout

In Amazon Managed Grafana, there is a data source timeout limit that applies to all queries, including those to your Timescale database. This timeout limit is a service quota set by AWS Managed Grafana and will override any timeout limit you configure on your data source if the AWS limit is lower.

While you can configure timeout settings in your data source configuration, the Amazon Managed Grafana service quota will take precedence. The lower of the two limits (your configured timeout vs. AWS service quota) will be applied.

To find the specific timeout limit for Amazon Managed Grafana and whether it can be increased to 10 minutes, you would need to check the Amazon Managed Grafana service quotas in the AWS General Reference documentation. If the current limit is less than your desired 10 minutes, you may need to request a quota increase through AWS Support.

As an alternative approach to handle long-running queries, you might consider:

• Optimizing your queries to return fewer data points
• Increasing the minimum interval time in query options
• Using group by functions in your queries to reduce the data volume

These approaches can help improve query performance and potentially avoid hitting the timeout limits altogether.
Sources
Troubleshoot queries - Amazon Managed Grafana
Connect to data sources - Amazon Managed Grafana

I think the limitation you are facing is coming from the database. Check your database configuration if it has a max timeout for queries set to 60 seconds. If you configuration a connection string or connection configuration, check for any timeout settings.