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 年前
相关内容
- AWS 官方已更新 2 年前