Cloudwatch SDK using putLogEvents() works locally but 504 Gateway timeout on my server (EC2)

I have a function that uses putLogEvents() method and it works fine locally but not when we push it out to our server (EC2 instance). We are always getting 504. I checked our LB and its allowing all traffic. I am running out of ideas why it is timing out on our server.

rePost-User-0097562
2 年前
Also, when I do aws logs put-log-events ... on my EC2 server, it never responds back and I think that's why I'm getting 504 on my API but I'm not sure how to debug or see why its causing that to not respond.
rePost-User-0097562
2 年前
I noticed that I can't telnet logs.us-west-2.amazonaws.com 443 on my EC2 instance

主題

運算管理與治理網路與內容交付

標籤

Amazon EC2 Amazon CloudWatch 彈性負載平衡 Amazon CloudWatch Logs

語言

English

rePost-User-0097562

已提問 2 年前檢視次數 280 次

1 個回答

最新
最多得票
最多評論

這些答案是否有幫助？支持正確答案，以幫助社區從您的知識中受益。

If it is a timeout, check whether your EC2 has outbound internet access. And after that if the EC2 has sufficient permissions, then it will work.

Manikandan

已回答 2 年前

rePost-User-0097562
2 年前
I can curl within that EC2 which means I have outbound internet access. What permission shall I be looking for on that EC2 instance?

Cloudwatch SDK using putLogEvents() works locally but 504 Gateway timeout on my server (EC2)

相關內容