Live data from Hacker News

Farewell EC2-Classic, it’s been swell

allthingsdistributed.com

101–110 of 187 posts

Re: Farewell EC2-Classic, it’s been swell

#101

Earlier quoted context omitted.

Not bad enough to be outright spam with just enough relevance to be shown in the top ten search results. Try finding product reviews, or product comparison articles. It will likely be LLM garbage that doesn't say anything, but uses the right keywords and enough coherency to be indexed.

> It will likely be LLM garbage that doesn't say anything, but uses the right keywords and enough coherency to be indexed. Or some site that "aggregates" Stackoverflow, Quora and whatnot. Pure hell and I wish everything bad possible on this planet to the people who have implemented this kind of scam.

I block them using uBlacklist in Firefox. My blacklist is growing.

Re: Farewell EC2-Classic, it’s been swell

#102

Earlier quoted context omitted.

The upkeep was apparently 12 engineers and they had tens of millions of users. It doesn't take that many users to justify 12 engineers plus infra, so it sounds like it was more that Google doesn't care to operate any product unless it will have users in the hundreds of millions.

It doesn't take that many users to justify 12 engineers plus infra, Otherwise, those 12 engineers and infra are pure negative on the balance sheet

Having basically all their users (well, as much as for any of their revenue generating products anyway) be revenue generating would require practically no effort for google specifically. It fit their revenue model perfectly. It is trivial to put the exact same ads in there as they already had on search and gmail, and it is stickier than search or gmail.

Re: Farewell EC2-Classic, it’s been swell

#103

Off topic, but I'm confused about the IPv4 notation in this quote: > When we launched EC2 in 2006, it was one giant network of 10.2.0.0/8. In my understanding, /8 means the first octet would be fixed (10.0.0.0-10.255.255.255) and I'm having trouble understanding the significance of the 2 here. If the 2 is significant, wouldn't you write it as /16? Given the source and my confidence on this notation, I feel like there…

Formally it should be 10.0.0.0/8, but you'll often encounter CIDRs written less formally by including set bits outside of the cidr prefix length. Often it is shorthand for "the subnet that includes this IP address", so 192.254.33.12/16, for instance. Or it might be a typo! ;)

I would interpret 192.254.33.12/16 to mean 'host 192.254.33.12 in a /16 subnet'.

That's also the notation `ip` on Linux supports

Re: Farewell EC2-Classic, it’s been swell

#104
post #54

> The complexities of managing infrastructure, buying new hardware, upgrading software, replacing failed disks — had been abstracted away ...and replaced by the complexities of AWS. I mean, even in the pre-AWS days, it's not like you had to buy the hardware or replace the failed disks yourself, web hosters did that for you.

Sure, but it often required a) you to detect and diagnose it on your own and b) a couple hours to a couple of weeks for them to agree and swap it out. Versus the ability to click a few buttons and have a brand new server on separate hardware.

Re: Farewell EC2-Classic, it’s been swell

#105
post #38

Earlier quoted context omitted.

[parent comment was edited, it originally mentioned SimpleDB] Speaking of SimpleDB, we still use it. It's amusing how it's basically swept under a rug at AWS. It's never mentioned, barely documented, but continues to work. It's a pretty good product for what it is - a very simple key/value store where you don't need/want to manage provisioned throughput, costs, keys, etc. The way they handle SimpleDB makes me respect…

They added Python 3.11 last month. Why do you call it close to abandoned?

Re: ElasticBeanstalk - it's just a feeling, and hopefully not correct - it just doesn't feel like it's one of their primary focuses, and seems suspiciously stable overall. There's nothing I particular want them to add, though, so maybe it's "perfect".

I love it, though - it's been a great boon for our small team - allowing for a painless hands-off deployment strategy that's worked great (largely unchanged) for almost a decade.

Re: Farewell EC2-Classic, it’s been swell

#106

Earlier quoted context omitted.

No, migrating did involve intervention from the account holder. More information here: https://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-her... It seems like AWS spent time, people and money to migrate customers off EC2 classic. They made a fairly good effort to automate the process and make it less painful for customers. For example: https://repost.aws/knowledge-center/ssm-migrate-ec2classic-v... The original…

Looking at that blog post, I think AWS could have done the migration for most users with no involvement of the user themselves. In the ideal world, they would have written software to live-migrate VM's to the new platform and emulate the old networking. Emulating old stuff should be pretty easy, because hardware moves on, and an instance back in 2006 probably had far lower performance expectations - and therefore eve…

I wonder why they didn't do that in the 14 years since VPCs were introduced?

Re: Farewell EC2-Classic, it’s been swell

#107
post #18

Earlier quoted context omitted.

It's not really the ads that killed Google search for me. it's more the over agressive minmaxed SEO that makes most of results garbage.

For me it's when they stopped showing results that include your keywords and instead a random smattering of anything broadly related to the topic being searched for.

You can use quotes around keywords.

https://blog.google/products/search/how-were-improving-searc...

Re: Farewell EC2-Classic, it’s been swell

#109

Earlier quoted context omitted.

It's also worth remembering that infrastructure stuck on EC2 Classic would have been built so long ago it may predate modern cloud tooling and even modern best practices around reproducibility and CI/CD. (EC2 user since 2010)

This. Unless a written guarantee could be offered by the cloud provider that migration will be absolutely trouble free, why wouldn't customers just stick to what they know works? And if they're not willing to provide a written guarantee, then that says a lot.

In this scenario, it's nothing to do with the cloud provider. Migrating a live production system is inherently difficult. You can make a reasonable analogy to moving houses – say, with two kids who are in school, and while you and your spouse are both working. No matter what guarantees you're given regarding the condition of the new house, simply moving all of your stuff (while you are using it) is a big hassle.
Post reply on HN