Closed ericayosh closed 1 year ago
I believe unlike Grafana's other aws datasources, the opensearch datasource does not use https://github.com/grafana/grafana-aws-sdk for backend queries. I'm not sure if this was done intentionally, or as an oversight whenever it was written, but it's something we plan to revisit.
I think for us to support using Workspace IAM Roles in backend queries (such as those used in alerting) we need to use the aws-sdk ideally reusing the grafana-aws-sdk.
Unfortunately I don't have a recommended quick fix or workaround just yet but we'll be sure to prioritize this refactor.
Hi @ericayosh would you be able to test this on the latest version of the plugin? v2.6.1
I was seeing similar issues with the alerts and can verify the fix solved our issues. Thank you!!
What happened: When using the open search plugin in AWS Managed Grafana credentials are provided by specifying the Authorization Provider on the data source configuration as Workspace IAM Role.
Customers are able to successfully connect to and query the open search datasource.
However when attempting to create alerts, they are getting an error:
This error is only occurring when customers are trying to create alerts.
What you expected to happen: The open search plugin should use the same workspace iam role code path for getting credentials when evaluating alerts and querying the data source.
How to reproduce it (as minimally and precisely as possible):
Workspace IAM Role
Save & Test
should show the error mentioned above.Anything else we need to know?:
Environment: AWS Managed Grafana workspace