search

lifegadget / aws-pusher

An automated deployment tool for static assets to AWS
0 stars 0 forks source link

Monitoring EC2 origin status is out of scope #2

Open BryanCrotaz opened 9 years ago

BryanCrotaz commented 9 years ago

I'd suggest monitoring status is best left to the Amazon CloudWatch free service. It's a really complex subject - add VPCs, firewall rules, load balancers, internal DNS - loads of reasons why the EC2 instance might be up but it's not responding to requests from cloud front

yankeeinlondon commented 9 years ago

Hmmm. Ok well let's talk about it. What I'm looking for is easy CLI availability of "readiness" and CloudWatch by itself doesn't give me that although it would be perfectly fine to have the CLI pull its status from Cloudwatch.

BryanCrotaz commented 9 years ago

I wonder if monitoring the back end server is out of scope in its entirety as this is about the static files?

On 23 April 2015 at 10:56, Ken Snyder notifications@github.com wrote:

Hmmm. Ok well let's talk about it. What I'm looking for is easy CLI availability of "readiness" and CloudWatch by itself doesn't give me that although it would be perfectly fine to have the CLI pull its status from Cloudwatch.

— Reply to this email directly or view it on GitHub https://github.com/lifegadget/aws-pusher/issues/2#issuecomment-95518865.

Bryan Crotaz Managing Director Silver Curve