12 messages in ru.sysoev.nginxRe: nginx and self-healing S3 static ...
FromSent OnAttachments
jeff emmingerJul 25, 2008 2:21 pm 
mikeJul 25, 2008 7:33 pm 
Ian M. EvansJul 25, 2008 11:41 pm 
ThomasJul 26, 2008 2:22 am 
Ian M. EvansJul 26, 2008 2:48 am 
Jean-PhilippeJul 26, 2008 3:04 am 
Ian M. EvansJul 26, 2008 3:20 am 
Jean-PhilippeJul 29, 2008 1:41 pm 
jeff emmingerJul 29, 2008 2:05 pm 
Ian M. EvansJul 29, 2008 5:28 pm 
Jonathan VanascoJul 29, 2008 7:19 pm 
mikeJul 29, 2008 7:46 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: nginx and self-healing S3 static hostingActions...
From:mike (mike@public.gmane.org)
Date:Jul 29, 2008 7:46:07 pm
List:ru.sysoev.nginx

Freedns.afraid.org has a free service and an api.

On Jul 29, 2008, at 5:28 PM, "Ian M. Evans"
<ianevans-H/XkN3sKs41m/Kok3h1/6Q@public.gmane.org> wrote:

your s3 bucket. dnsmadeeasy (or similar) monitors your s3 bucket, and switches DNS to your backup if it goes down. Your app only ever

Someone else mentioned dnsmadeeasy and I contacted their tech people. They said:

"The manner in which S3 is implemented makes it difficult to monitor using our toolset."

There was one DNS company (http://dynect.com/) that mentioned having an API for allowing remote changes. So I guess the cron method from the non-static server could work. If it can't reach your S3 bucket, it could run a script to change the DNS to your backup choice.

As Dave Winer pointed out, there's some cash to be made for the companies who step up to find a way to help spooked S3 users...or potential users like me.