AWS peers into soul of Load Balancers for DNS failover Amazon Web Services now lets users apply automated DNS failover policies to data fronted by load balancers rather than just IPs. As El Reg predicted, Amazon has now added Elastic Load Balancer (ELB) failover to Route 53 just three months after launching a new auto-redirect feature. This means Amazon's "dead man switch" …
Not trying to be elitist, but if you can't find that out for yourself, AWS isn't designed for you. It's just the way it's set up, there's almost zero support, it's designed with technical people who can look at numbers and find references on Amazon's *extensive* docs in mind.
That being said do a google search for "Amazon Web Services Simple Monthly Calculator" - should get you the answer to the question.
This post has been deleted by its author
This post has been deleted by its author
I'm wondering just how useful this really is.
Are competent admins willing to put their services behind something like this?
Unless you can control the clients, changing DNS isn't really a viable way of redirecting traffic. Many clients don't respect TTL's, and often cache DNS records for much longer than they should, making DNS based load balancing particularly unsuitable for public websites.
If on the other hand, you do control the client, and can either ensure that TTLs are honoured, or that DNS lookups aren't cached at all, this could be a useful addition.
"changing DNS isn't really a viable way of redirecting traffic"
It is if you're smart about it. You have to build extra redundancy in your zones to handle failures, the point is mostly about getting you out of total failure for the portion of your traffic that has already hit that region ASAP. For everything else it's fine.
It's the best solution to the problem put it this way, which is why companies like Google and Microsoft use similar systems to direct traffic. But sure it's a compromise.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
