Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Failure to add Cloudwatch Datasource on Amazon Managed Grafana.

0

I am currently trying to access my Cloudwatch logs from sa-east-1, but when I try to create my datasource I get the following: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->

I have tried using Workspace IAM Role and Access key & Secret key for Auth (both with admin priviledges). Neither of them work. Also enabled 443 inbound on the security group.

Topics
Management & Governance
Tags
Amazon GrafanaAmazon CloudWatch LogsSecurity GroupIAM Policies
Language
English

asked 2 years ago768 views

1 Answer
1
Accepted Answer

Try accessing the logs directly using the AWS CLI to see if it's a problem with the AWS service or your environment.

aws logs describe-log-groups --region sa-east-1

If possible, try setting up the same configuration in a different AWS region. This can help determine if the issue is region-specific.

Ensure, Security Groups: Port 443 (HTTPS) is open for outbound traffic in the security group attached to your instance or environment.

VPC/Subnet Configuration: If your instance is within a VPC, ensure that your VPC routing table is configured correctly to allow outbound internet access (via an Internet Gateway or NAT Gateway).

AWS
EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

  • Esteban
    2 years ago

    VPC routing table was not configured correctly, thank you Deekshitha Urs.

  • sshd
    a year ago

    Hi Deeksha, I have the same issue

    • aws logs describe-log-groups works for me
    • all outbound traffic is allowed in the SG attached to the Grafana instance
    • my VPC is using the internet gateway and other instances in that VPC can access the internet (and the routing table looks good) what else can be the problem? thanks
  • sshd
    a year ago

    I think I understand the root of the issue, but I can't fix it: Under data sources - IAM permission access settings, I set the checkbox for cloudwatch, and it updates the workspace. But when I open the access settings again, I don't see the checkbox

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content