Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

blog.cloudflare.com

Post reply on HN
Print view View original

161–168 of 168 posts

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#161

Post by solatic »

mxschumacher wrote: post #149
solatic wrote: post #101

Earlier quoted context omitted.

Support and also all-around enterprise readiness. Even on the enterprise tier, their permissions management is a pale shadow of what IAM grants you on AWS or GCP, to the point where you will put your compliance as risk. No documentation on setting up SAML/SSO for their management console. It's very, very clear that their internal growth engines are set to ludicrous growth rates (to try and justify their outrageous st…

please find the docs for SSO setup for the CF dashboard here: https://developers.cloudflare.com/cloudflare-one/application...

Why is this buried deep in the docs for Zero Trust and not part of user management? Why are there no references to it from user management, either in the docs or in the add/remove users screen?

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#162

Post by albert_e »

ericpauley wrote: post #90
albert_e wrote: post #44

Earlier quoted context omitted.

Bulk deletes on S3 should be done using a Life Cycle Policy to avoid the per object delete cost

This (although as others said it’s the list cost, not the delete). If you want to nuke a bucket don’t waste your time with the API and just age the files out. I’ve done this with buckets with tens of millions of files and five minute’s work.

Both list objects and delete object are API actions that incur the standard cost for "requests" ... isn't it?

>>

PUT, COPY, POST, LIST requests (per 1,000 requests) = $0.005

GET, SELECT, and all other requests (per 1,000 requests) = $0.0004

>>

"You pay for requests made against your S3 buckets and objects. S3 request costs are based on the request type, and are charged on the quantity of requests as listed in the table below" https://aws.amazon.com/s3/pricing/#:~:text=You%20pay%20for%2...

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#163

Post by attentive »

kmeisthax wrote: post #160
abcdefg12 wrote: post #154

Earlier quoted context omitted.

Of course it can.

So, the CloudFront setup process only surfaces S3, ELBs, API Gateways, Mediastore, and Mediapackage domains as origin domains. I do notice that it will let me type in an arbitrary domain - is that how you're supposed to stick bare EC2 instances behind CloudFront? Just provide it something like realoriginserverplsdonthack.example.com and use some other method (e.g. VPC configuration) to prevent bypassing CloudFront?

Correct, you can put multiple instances (A records) there, if on route53 you can also use healthchecks, geo etc.

If you want to lock ec2 access to cloudfront only you can do it in SG with "managed prefix list for CloudFront".

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#164

Post by raffraffraff »

solardev wrote: post #64
figassis wrote: post #6

Earlier quoted context omitted.

This, CF is the only service that I find amazing, and that I do not use for anything. Compared to AWS, I think I prefer the "we're your unopinionated infra provider, if you want a WAF we have that too", vs the CF "block the world, especially the developing world, give zero craps about it". I fundamentally would be unhappy as their customer even if their service were stellar because I do not want my apps to be associa…

The geographical blocks are not enforced by Cloudflare as a blanket ban, but are chosen by each account owner (it's a setting you configure). I've worked with a few companies that saw this as a very valuable service (like small domestic companies blocking international traffic, especially from Russia and China, because we had no presence there anyway and that cut down bot traffic by like 95%). Likewise, TOR access is…

Absolutely this. Cloudflare simply provide website owners with the tools. I've used them on a number of sites. For example, someone provides a local service and is sick of hacking attempts from the same 5 countries. Block 'em. Or they sell products that can't be delivered internationally, so why expose yourself to pointless inquiries or hacking attempts?

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#165

Post by ayuhito »

taw1516 wrote: post #120
NicoJuicy wrote: post #106

Earlier quoted context omitted.

Yeah https://developers.cloudflare.com/images/image-resizing/ https://developers.cloudflare.com/images/image-resizing/url-... Example: src="/cdn-cgi/image/width=80,quality=75/uploads/avatar1.jpg About /cdn-cgi/image/ It's a fixed prefix that identifies that this is a special path handled by Cloudflare’s built-in Worker. --- Price at Cloudflare : 50,000 monthly resizing requests included with Pro, Business. $9 per add…

that is a lot cheaper than Vercel in term of store image but egress seems expensive since they charge per cache image served as well. Do you know if Cloudinary is a better option?

[dead]

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#166

Post by orf »

toomuchtodo wrote: post #71
albert_e wrote: post #44

Earlier quoted context omitted.

Bulk deletes on S3 should be done using a Life Cycle Policy to avoid the per object delete cost

Deletes are free, but you have to pay to list to delete if not individually tracking.

Ignore the replies about inventories. $0.005 Per 1k list requests. A list request returns 1k items. 1 million items for $0.005, or 1 billion items for 5 dollars.

Still use lifecycle policies (I visualized how it ages out 1 billion items here[1]), but list request prices are not a factor worth mentioning.

1. https://tomforb.es/visualizing-how-s3-deletes-1-billion-obje...

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#167

Post by ericpauley »

albert_e wrote: post #162
ericpauley wrote: post #90

Earlier quoted context omitted.

This (although as others said it’s the list cost, not the delete). If you want to nuke a bucket don’t waste your time with the API and just age the files out. I’ve done this with buckets with tens of millions of files and five minute’s work.

Both list objects and delete object are API actions that incur the standard cost for "requests" ... isn't it? >> PUT, COPY, POST, LIST requests (per 1,000 requests) = $0.005 GET, SELECT, and all other requests (per 1,000 requests) = $0.0004 >> "You pay for requests made against your S3 buckets and objects. S3 request costs are based on the request type, and are charged on the quantity of requests as listed in the tab…

From the same paragraph:

“DELETE and CANCEL requests are free.”

Re: Cloudflare Sippy: Incrementally Migrate Data from AWS S3 to Reduce Egress Fees

#168

Post by _lvbh »

linsomniac wrote: post #139
_lvbh wrote: post #135

Earlier quoted context omitted.

I’ve reached 500 TB a month at one point but never had any issue. Perhaps an email I ignored but nothing went down.

Is that on the free tier or one of the paid tiers like the $60/mo or $200/mo?

Free tier
Post reply on HN