cloudfalcon

What was the submission process like? You're a small startup so I'm curious to learn about what Open AI saw in your team to put you in the early batch of plugins

What's the risk to your business of other data security companies (like BigID) offering this kind of functionality?

The release clearly states: "that people should be able to speak freely on the platform within the bounds of the law."

Your bulk-label idea is definitely interesting.

Hi Kaveh, congratulations on the launch. Is filtering by tag currently available (cost allocation and non-cost tag)? I definitely think you should add support for tracking other AWS services ASAP, as long as one can drill-down to the request level (e.g., GetObject).

I'm following good form. No silent edits were made. There has been an Author's Note in that paragraph the entire time since the change acknowledging the miscalculation.

Cloudflare R2 is topical right now - that was the motivation. Not saying it was the right strategy to do so (clearly not given the mistake).

They are right. We addressed the comment and fixed the article.

You're right. This is a silly mistake on my part in rushing out this piece. I apologize. Thanks for pointing this out -I've since taken out the paragraph.

Hi, I'm LV, I wrote this post. I co-founded Taloflow to make choosing cloud vendors transparent and easy.

I'm curious to hear what factors HN readers think I missed and if you think Cloudflare R2 will be a threat in the cloud object storage market place.

Having done hundreds of TCO analyses for customers moving object storage providers, this seems like it carves out a very interesting niche for Cloudflare. R2's higher storage costs (roughly triple) also make it a more manageable threat to specialized solutions like Storj DCS, Wasabi and Backblaze B2.

At Taloflow (https://www.taloflow.ai), (disclosure: I'm the CEO/Cofounder) we provide buying insights for cloud object storage (and soon other IaaS/PaaS). We will definitely be adding Cloudflare R2 to the mix.

Hey HN, we had this question pop up about how we moved our AWS glue jobs from Fargate to ECS on our last post, so wanted to follow up to answer that question.

This might be helpful for anyone thinking about a similar migration. If you have any questions / comments let us know.

Hi Corey! I'm the author of the blog post - I definitely agree with you. 9 times out of 10 engineering teams underestimate cost of engineering work as well as opportunity cost lost due to managing non-core functionality internally or moving away from managed services.

For us our pipeline was actually easier to work with Flink than Glue because of the restrictions that Amazon placed on it and so that factored into our decision.