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年前