1 Answer
- Newest
- Most votes
- Most comments
0
Never mind. I already found the solution and it seems very obvious. We were using Quicksight instance from another region than our Timestream. After we switched to
https://eu-west-1.quicksight.aws.amazon.com
the datasource was properly found and everything works as expected.
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago