I would love to be able to set a secret (from Secrets Manager) as the source for the credentials of an Amazon Datasource like RDS or AWS data storage that requires a password/secret/connection string.
According to this documentation it is already available for Redshift. I would like to see it for Aurora Postgres as well. ideally, when a secret is rotated in secret manager, the dashboard/grafana query that uses that data source might fail or receive an error and then the data source would attempt to retrieve the secret again and retry the operation. Or perhaps the secret is retrieved for every query, and thus would be slower but perhaps still effective. Or perhaps there is short lived encrypted cache or other mechanism to prevent high traffic requests to Secrets Manager. I'm sure this could be implemented a number of different ways though would probably follow the Redshift implementation.
Apologies if this is the wrong place for this. I checked the contributing guidelines and did not see an alternative.
I would love to be able to set a secret (from Secrets Manager) as the source for the credentials of an Amazon Datasource like RDS or AWS data storage that requires a password/secret/connection string.
According to this documentation it is already available for Redshift. I would like to see it for Aurora Postgres as well. ideally, when a secret is rotated in secret manager, the dashboard/grafana query that uses that data source might fail or receive an error and then the data source would attempt to retrieve the secret again and retry the operation. Or perhaps the secret is retrieved for every query, and thus would be slower but perhaps still effective. Or perhaps there is short lived encrypted cache or other mechanism to prevent high traffic requests to Secrets Manager. I'm sure this could be implemented a number of different ways though would probably follow the Redshift implementation.
Apologies if this is the wrong place for this. I checked the contributing guidelines and did not see an alternative.