1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
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.
respondido hace 2 años
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años