1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten