1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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.
답변함 2년 전