Timestream Throttling Issue

Thank you for providing details about the Timestream throttling issue you're experiencing. I understand your confusion, especially since you've confirmed that QueryInsights is not enabled in your setup.

While it's true that the 1 query per second (QPS) limit is specifically mentioned for cases when QueryInsights is enabled, it's important to note that Amazon Timestream does have other service quotas and limits that could potentially lead to throttling errors, even when QueryInsights is disabled.

The error message you're receiving (StatusCode: 429, ThrottlingException: Request rate limit exceeded) suggests that you're hitting a rate limit, but it may not be directly related to the QueryInsights feature.

Here are a few possibilities to consider:

1. There might be an overall API request rate limit for Timestream that you're exceeding. While not explicitly stated for the Query action, many AWS services have default limits to protect the service.

2. Your account might have a specific quota set that's lower than the default, possibly due to your account's history or specific settings.

3. The throttling could be related to the complexity or size of your queries, rather than just the number of queries per second.

4. There might be other Timestream operations running concurrently that are contributing to your overall API usage.

To address this issue, I recommend the following steps:

1. Check your AWS account's Timestream quotas in the AWS Management Console to see if there are any unexpected limits set for your account.

2. Consider implementing exponential backoff and retry logic in your application to handle these throttling errors gracefully.

3. If possible, try to optimize your queries to reduce their complexity or the amount of data they're processing.

4. Monitor your Timestream API usage using AWS CloudWatch metrics to get a better understanding of your usage patterns.

5. If the issue persists, you may want to contact AWS Support to investigate if there are any account-specific limits or if they can provide more detailed information about the cause of the throttling.

6. Consider requesting a quota increase if you determine that you genuinely need a higher throughput for your use case.

Remember, even though the documentation doesn't explicitly mention a TPS rate limit for the Query action, AWS services often have various limits in place to ensure fair usage and system stability. The specific limits can sometimes vary based on region, account status, and other factors.

If you continue to face issues after trying these steps, it would be best to engage directly with AWS Support for a more in-depth investigation of your specific use case and account settings.
Sources
QueryInsights - Amazon Timestream
Query - Amazon Timestream
Resolve throttling errors in CloudWatch logs | AWS re:Post
REL05-BP02 Throttle requests - AWS Well-Architected Framework
Resolve service limit or service quota errors in Athena | AWS re:Post