Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#1

Post by jtblin » Mon, Sep 29, 2014, 10:49 PM UTC

Why Loggly Chose AWS Route 53 Over Elastic Load Balancing
loggly.com

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#2

Post by mey » Tue, Sep 30, 2014, 12:16 AM UTC

Why would you allow your clients to transmit potentially sensitive data to you as clear text over the internet?

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#3

Post by lpgauth » Tue, Sep 30, 2014, 12:26 AM UTC

What kind of time granularity can you get for health checks on ELB vs Route 53?

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#4

Post by zimbatm » Tue, Sep 30, 2014, 12:31 AM UTC

> If there is an issue with a collector, Route 53 automatically takes it out of the service; our customers won’t see any impact.

Except when for example rsyslog caches DNS resolution forever. Or the log forwarded doesn't have a buffer and logs get lost.

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#5

Post by hobs » Tue, Sep 30, 2014, 12:33 AM UTC

>Amazon Route 53 DNS Round Robin Was a Win

>If you’ve ever used the Internet, you’ve used the Domain Name System, or DNS, weather you realize it or not.

Interesting article, wrong weather used in this sentence.

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#6

Post by kfnic » Tue, Sep 30, 2014, 12:34 AM UTC

What kind of TTL value would they use for these records? Should something happen to one of the collectors, couldn't that value still be cached by an endpoint or an intermediary?

Even with a short TTL, are there still servers out there that don't respect all TTLs, or has that been eliminated by now?

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#7

Post by jcampbell1 » Tue, Sep 30, 2014, 12:36 AM UTC

It seems odd to leave off any discussion about DNS TTLs, and the risk that something like 8.8.8.8 could end up sending them a thundering herd.

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#8

Post by general_failure » Tue, Sep 30, 2014, 12:44 AM UTC

zimbatm wrote: post #4

> If there is an issue with a collector, Route 53 automatically takes it out of the service; our customers won’t see any impact. Except when for example rsyslog caches DNS resolution forever. Or the log forwarded doesn't have a buffer and logs get lost.

How does this work regardless? Isn't route53 a DNS system? How does it know whether a service went up/down?

EDIT: To reply to myself http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hea... http://docs.aws.amazon.com/Route53/latest/APIReference/API_C...

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#9

Post by mbell » Tue, Sep 30, 2014, 12:49 AM UTC

There is a rather large technical divide between 'no logs left behind' and relying on DNS lookup to provide that guarantee.

Re: Why Loggly Chose AWS Route 53 Over Elastic Load Balancing

#10

Post by KarenS » Tue, Sep 30, 2014, 1:01 AM UTC

hobs wrote: post #5

>Amazon Route 53 DNS Round Robin Was a Win >If you’ve ever used the Internet, you’ve used the Domain Name System, or DNS, weather you realize it or not. Interesting article, wrong weather used in this sentence.

Thanks for noticing this! It's fixed now.