Cloudwatch error

Grafana Configuration
, ,
1

What Grafana version and what operating system are you using?
Grafana version: 11.02 Enterprise
Operating System: ubuntu 22.04.2 aks

What are you trying to achieve?
I am trying to configure AWS CloudWatch as a data source in Grafana to fetch metrics from my AWS environment. However, I am encountering issues related to SIGv4 authentication.

How are you trying to achieve it?
I attempted to add CloudWatch as a data source in Grafana by providing AWS credentials (Access Key, Secret Key) and configuring the appropriate region. I expected the SIGv4 signing process to work automatically during this setup.

What happened?
When trying to connect to AWS CloudWatch as a data source, SIGv4 authentication appears to not function or is not visible in the Grafana interface. As a result, I cannot establish a connection to AWS CloudWatch.

What did you expect to happen?
I expected SIGv4 authentication to automatically sign the API requests to AWS CloudWatch and allow the connection to succeed without additional configurations or manual intervention.

Can you copy/paste the configuration(s) that you are having problems with?
Here is the configuration I used when adding CloudWatch as a data source in Grafana:

Default Region: [Insert region, e.g., us-east-1]
Authentication Provider: Access & secret key
Access Key: [Redacted]
Secret Key: [Redacted]

Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
The Grafana UI does not display any specific SIGv4 error messages, but the data source test fails with a generic connection error. There is no clear indication in the logs that SIGv4 signing is being applied or failing.

Did you follow any online instructions? If so, what is the URL?
I followed the official Grafana documentation for setting up AWS CloudWatch as a data source:

2

I’m sorry to hear that you’re experiencing difficulties.

Grafana can provide valuable information about certain issues through its own debug logs. These logs can help troubleshoot and identify the root cause of problems (especially if they are related to anything that can be configured via Grafana config file).

To enable debug logging edit the configuration file grafana.ini:

[log]
# Either "console", "file", "syslog". Default is console and file
# Use space to separate multiple modes, e.g. "console file"
mode = console file

# Either "debug", "info", "warn", "error", "critical", default is "info"
level = debug

Then restart grafana for the setting to go into effect.

Replicate the problem and check Grafana logs. However, before posting the debug logs on the community forum, it is important to sanitize any private details such as passwords, tokens, IPs, names, … By including properly formatted debug logs (with sanitized information) and details about your installations (e.g. exact Grafana version, how it was installed, OS details, …), you greatly enhance the chances of receiving accurate assistance and solutions.