AWS: Centralize aws plugin auth documentation #38112
Closed
sunker
announced in
Data Sources
Replies: 2 comments 2 replies
-
Hi @sunker, creating a single source of truth is a great idea, definitely less maintenance and less weird. With regards to where we should keep this information, it will be best if we create this separate auth-only topic in markdown and keep it in our Grafana docs repository. We can single-source it (I can help with that) to show up in the CloudWatch and or other AWS topics. And we can refer to it from plugins topics living in other repos. Question: For the newer AWS plugins, do you know if they will get classified as data sources? Or will they be similar to the redshift-data source? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, all our AWS data source plugins use the same library for handling authentication. This means they will all have the same authentication options (AWS SDK Default, Secret & keys, Credentials file, Workspace IAM) and the same configuration options.
CloudWatch was our first AWS plugin, so all plugins that have been developed after it just reference the authentication section in the CloudWatch documentation. It's nice to have this documented in one place only, but it's also a bit weird having the CloudWatch data source being the master for this.
What I'd like to do:
Thougts @achatterjee-grafana @aocenas @ryantxu @grafana/cloud-datasources
Beta Was this translation helpful? Give feedback.
All reactions