AWS Datasources: Update grafana assume role docs to remove unnecessary flags (#101086)

Co-authored-by: Larissa Wandzura <126723338+lwandz13@users.noreply.github.com>
pull/101884/head^2
Isabella Siu 10 months ago committed by GitHub
parent 85b0b47efd
commit 700f1225df
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 2
      docs/sources/datasources/aws-cloudwatch/aws-authentication/index.md

@ -164,7 +164,7 @@ Grafana Assume Role is currently in [private preview](https://grafana.com/docs/r
It's currently only available for Amazon CloudWatch.
To get early access this feature, reach out to Customer Support and ask for the `awsDatasourcesTempCredentials` feature toggle to be enabled and the `cloudwatchRemoteDatasource` and `athenaRemoteDatasource` feature toggles to be disabled on your account.
To gain early access to this feature, contact Customer Support and ask for the `awsDatasourcesTempCredentials` feature toggle to be enabled on your account.
{{% /admonition %}}
The Grafana Assume Role authentication provider lets you authenticate with AWS without having to create and maintain long term AWS users or rotate their access and secret keys. Instead, you can create an IAM role that has permissions to access CloudWatch and a trust relationship with Grafana's AWS account. Grafana's AWS account then makes an STS request to AWS to create temporary credentials to access your AWS data. It makes this STS request by passing along an `externalID` that's unique per Cloud account, to ensure that Grafana Cloud users can only access their own AWS data. For more information, refer to the [AWS documentation on external ID](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html).

Loading…
Cancel
Save