7 ms·
AWS (http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.h...), GCE (https://cloud.google
by BenjaminCoe 10y ago
AWS (http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.h...), GCE (https://cloud.google.com/compute/docs/faq#where_can_i_find_short_product_name_ip_ranges https://cloud.google.com/compute/docs/faq#where_can_i_find_s...), and other clouds maintain an up-to-date list of the ip blocks within their data-centers -- providing for more accurate data than a whois lookup.
however! I just added whois as a fallback, this seems like a really good idea:
https://github.com/bcoe/which-cloud/pull/10 https://github.com/bcoe/which-cloud/pull/10
- teddyh 10y agoWhat are you doing to prevent others using you as a whois proxy? Alternately, how are you planning to evade the (rather restrictive) rate limits which whois servers impose?
- BenjaminCoe 10y agoit's a goal to use the advertised IP blocks of cloud providers where possible, with whois simply as a fallback. Will happily accept patches for other providers.
- ugexe 10y agoYou realize that the majority of IPs submitted may not be from a known cloud provider/test suite, and so you're still dealing with the rate limiting from falling back for most requests?
- BenjaminCoe 10y agoI built this library to track signups for an application that has a fairly low request rate. if you need a higher request rate 🤷 ¯\_(ツ)_/¯ pitch in and help add support for a wider variety of cloud providers.