3 ms·

You mean amazing, super-scaled CDN Cloudfront with support for free SSL certificates, S3 bucket origins, API-based invalidations with S3 deployments, and so man

You mean amazing, super-scaled CDN Cloudfront with support for free SSL certificates, S3 bucket origins, API-based invalidations with S3 deployments, and so many more features than I can mention here? I'm sure you meant that. Edit: we host all our sites - main site, engineering blog, press kit, and so on using Cloudfront in front of S3, and not only is it all-the-way fast (which we get comment after comment on) but it's cheap as all getout. https://tech.flyclops.com/posts/2016-04-27-flyclops-sites-static-ssl.html https://tech.flyclops.com/posts/2016-04-27-flyclops-sites-st...

mordocai 10y ago
You mean the awful gatekeeper of the Internet that soft-blocks tor and causes problems with legitimate traffic (tor or otherwise) across the world? Yeah, that one. Edit: As informed, I was confusing cloudfront and cloudflare.
- bbatsell 10y ago
  You are confusing Cloudfront and Cloudflare.
- Tomdarkness 10y ago
  You do realise CloudFront (https://aws.amazon.com/cloudfront/ https://aws.amazon.com/cloudfront/) and CloudFlare (https://www.cloudflare.com/ https://www.cloudflare.com/) are not the same?
calavera 10y ago
CloudFront is good. We use it for large assets. After managing thousands of sites, we realized that it's actually a hassle to manage cache invalidation yourself. We work with several cloud providers to offer a better experience at the CDN level and manage caches for you. Our CDN also allows proxying end-to-end encrypted connections, so you can use it to host front-end apps and redirect requests to backend servers somewhere else.
- themartorana 10y ago
  I put it up on our blog, but many S3 deployment SaaS operations or even self-hosted solutions will invalidate CDN caches automatically based on files deployed to S3. We use http://deploybot.com http://deploybot.com but there are many others.
- base 10y ago
  I use s3_website (https://github.com/laurilehmijoki/s3_website https://github.com/laurilehmijoki/s3_website) to deploy to S3 and invalidate in CloudFront.

mordocai 10y ago

You mean the awful gatekeeper of the Internet that soft-blocks tor and causes problems with legitimate traffic (tor or otherwise) across the world? Yeah, that one. Edit: As informed, I was confusing cloudfront and cloudflare.

bbatsell 10y ago
You are confusing Cloudfront and Cloudflare.
Tomdarkness 10y ago
You do realise CloudFront (https://aws.amazon.com/cloudfront/ https://aws.amazon.com/cloudfront/) and CloudFlare (https://www.cloudflare.com/ https://www.cloudflare.com/) are not the same?

calavera 10y ago

CloudFront is good. We use it for large assets. After managing thousands of sites, we realized that it's actually a hassle to manage cache invalidation yourself. We work with several cloud providers to offer a better experience at the CDN level and manage caches for you. Our CDN also allows proxying end-to-end encrypted connections, so you can use it to host front-end apps and redirect requests to backend servers somewhere else.

themartorana 10y ago
I put it up on our blog, but many S3 deployment SaaS operations or even self-hosted solutions will invalidate CDN caches automatically based on files deployed to S3. We use http://deploybot.com http://deploybot.com but there are many others.
base 10y ago
I use s3_website (https://github.com/laurilehmijoki/s3_website https://github.com/laurilehmijoki/s3_website) to deploy to S3 and invalidate in CloudFront.