You can use one of the following authentication methods. All of these methods are enabled by default. You can disable them if necessary if you have server configuration access. For more information, refer to allowed_auth_providers documentation.
AWS SDK Defaultperforms no custom configuration and instead uses the default provider as specified by the AWS SDK for Go. It requires you to configure your AWS credentials separately, such as if you’ve configured the CLI, if you’re running on an EC2 instance, in an ECS task, or for a Service Account in a Kubernetes cluster.
Credentials filecorresponds directly to the SharedCredentialsProvider provider in the Go SDK. It reads the AWS shared credentials file to find a given profile. While
AWS SDK Defaultwill also find the shared credentials file, this option allows you to specify which profile to use without using environment variables. This option doesn’t have any implicit fallbacks to other credential providers, and it fails if the credentials provided from the file aren’t correct.
Access and secret keycorresponds to the StaticProvider and uses the given access key ID and secret key to authenticate. This method doesn’t have any fallbacks, and will fail if the provided key pair doesn’t work.
Note: Grafana also supports the
Workspace IAM rolemethod. We will be add documentation for this authentication method soon.
Currently all access to CloudWatch is done server side by the Grafana backend using the official AWS SDK. If you are using the AWS SDK Default authentication method, and your Grafana server is running on AWS, use IAM Roles to handle authentication automatically.
For more information, refer to the AWS documentation on IAM Roles.
Note: IAM policies are data source specific. Refer to Authentication section of the Cloudwatch topic for more information.
Assuming a role
Assume Role ARN field allows you to specify which IAM role to assume. When left blank, the provided credentials are used directly and the associated role or user should have the required permissions. If this field is non-blank, on the other hand, the provided credentials are used to perform an sts:AssumeRole call.
If you set this field to
false then AWS authentication no longer uses an assumed role. For more information, refer to assume_role_enabled documentation.
Endpoint field allows you to specify a custom endpoint URL that overrides the default generated endpoint for the CloudWatch API. Leave this field blank if you want to use the default generated endpoint. For more information on why and how to use Service endpoints, refer to the AWS service endpoints documentation.
EKS IAM roles for service accounts
The Grafana process in the container runs as user 472 (called “grafana”). When Kubernetes mounts your projected credentials, they will by default only be available to the root user. To allow user 472 to access the credentials (and avoid falling back to the IAM role attached to the EC2 instance), you need to provide a security context for your pod.
securityContext: fsGroup: 472 runAsUser: 472 runAsGroup: 472
AWS credentials file
Create a file at
~/.aws/credentials. That is the
HOME path for user running grafana-server.
Note: If you think you have the credentials file in the right place and it is still not working, you might try moving your .aws file to ‘/usr/share/grafana/’ and make sure your credentials file has at most 0644 permissions.
[default] aws_access_key_id = asdsadasdasdasd aws_secret_access_key = dasdasdsadasdasdasdsa region = us-west-2
Related Grafana resources
Unify your data with Grafana plugins: Splunk, MongoDB, Datadog, and more
Show how Grafana can be used to take data from multiple different sources and unify it, without disrupting the investments that are working today.
Demo: Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.