Hacker News Reader

Comment by manishsharan | Hacker News Reader

A long time ago , I hooked up all my docker images to send logs to AWS Cloudwatch. Now, regardless of which cloud or VPS I am using, all my logs are at AWS Cloudwatch. So that's one less headache for me.

View on HN

My biggest worry with such a solution is a program going crazy and blowing up my bill at the end of the month.

Less a concern for enterprise projects where you can setup cost monitoring, but terrifying for hobby projects running on credits. I can't find the article, but I remember reading something similar happening to someone using GCP not very long ago.

I share your fear ; I am running this on my bootstrap budget. I have taken a couple of precautions -- my debug logs expire within 2 days and others within a month. and I have set alarms to trigger in case of increased or unexpected metrics and I have be tested those alarms . It is a very good idea to first write and test your alarms for AWS before you deploy to AWS . My docker images run on Hetzner cloud and Vultr and they have no network egress costs and there is no AWS network charge for data ingress.

Is there a front end to Cloudwatch that can visualize the results in a way so that we don't need to give AWS account access to the viewer?

I don't think so but there is a solution: you can create a locked down role for user who can only see Cloudwatch metrics and visualization for your log group. I have not implemented this but AWS IAM gives you this ability.

Reply on news.ycombinator.com