Now all they need to do is actually allow a fixed budget instead of possible runaway credit card charges.
Microsoft do it, and IIRC Google, so why not Amazon?
I've been waiting for this for about 20 years too :D
Farewell EC2-Classic, it’s been swell
71–80 of 187 posts
Re: Farewell EC2-Classic, it’s been swell
#72> If you had launched an instance in 2006, an m1.small, you would have gotten a virtual CPU the equivalent of a 1.7 GHz Xeon processor with 1.75 GB of RAM, 160 GB of local disk, and 250 Mb/second of network bandwidth. And it would have cost just $0.10 per clocked hour.
> It’s quite incredible where cloud computing has gone since then, with a P3dn.24xlarge providing 100 Gbps of network throughput, 96 vCPUs, 8 NVIDIA v100 Tensor Core GPUs, 32 GiB of memory, and 1.8 TB of local SSD storage, not to mention an EFA to accelerate ML workloads.
They decided to omit the price but I think it's relatively good - around 31 USD per hour. Just remember to turn it off after you're done otherwise it will cost you over 7 grand.
Re: Farewell EC2-Classic, it’s been swell
#73I haven't spun up anything in the cloud in a while. I used to dabble in both AWS and Digital Ocean. Usually went with DO because it seemed simpler and my projects were super small (and they had a lot of relevant guides to spinning up X, Y, and Z service on their systems). What is the difference between EC2-classic and whatever is available today? Are you still able to just get a linux box with a public IP address?
I think there's Lightsail for such use now - https://aws.amazon.com/free/compute/lightsail-vs-ec2/
Re: Farewell EC2-Classic, it’s been swell
#74> 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.
> 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.
Given no single web hoster has grown to the size of AWS / Azure, it is safe to assume just which complexities the industry is willing to tolerate. I mean, Oracle still rakes in billions, despite everything.
Re: Farewell EC2-Classic, it’s been swell
#75Earlier quoted context omitted.
You have to create at minimum a vpc, internet gateway and at least one subnet/route table pointing to the igw
Oh man, I don't know any of these concepts (rather I've heard of all of them, but don't know how they apply in practice). I'm probably not the target customer for AWS any more haha. Been so long since I did anything web related. Time to find some networking for dummies youtube channels I guess.
Nah, it's just EC2 you are not a target of. Checkout AWS Lightsail
Re: Farewell EC2-Classic, it’s been swell
#76Earlier quoted context omitted.
I see Reader as Google's attack on RSS' popularity. The product was killed off when its job was accomplished.
No because if anything (the effect might have been small) it reduced the power of the open web and many websites (which Google tied togeather) and encouraged people to go to walled gardens ( Facebook, Instagram, twitter, etc ) which are controlled by other companies.
A lot of heavyweight bloggers and aggregators used Reader in their toolchains - it was very good at surfacing trending content. I don't think the effect on the blogging ecosystem was small.
I could believe they were clearing a path for G+ and Discover on Android.
Re: Farewell EC2-Classic, it’s been swell
#77This is something Google Cloud should learn from. It doesn't matter if product XX still makes money or fits in your business model. There are people who rely on it. And they'll remember if the vendor kept it running trouble free for years. They'll also remember if it was arbitrarily shut down or the price was suddenly increased by 4x and they had to spend many man hours migrating to another option. (Google maps api?)…
Google Reader. Never forget.
Obligatory reminder that RSS is alive and well. It remains popular. I both subscribe to RSS, and support it on my blog. You can too.
Re: Farewell EC2-Classic, it’s been swell
#78Earlier quoted context omitted.
Can you explain "minimaxed" in this context, please?
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.
And the content itself is just a reflection of the search. Whole web is turning to rot such that the only few remaining great sites don't even need indexing because well there's so few left.
Re: Farewell EC2-Classic, it’s been swell
#79Off 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! ;)
Re: Farewell EC2-Classic, it’s been swell
#80> If you had launched an instance in 2006, an m1.small, you would have gotten a virtual CPU the equivalent of a 1.7 GHz Xeon processor with 1.75 GB of RAM, 160 GB of local disk, and 250 Mb/second of network bandwidth. And it would have cost just $0.10 per clocked hour. > It’s quite incredible where cloud computing has gone since then, with a P3dn.24xlarge providing 100 Gbps of network throughput, 96 vCPUs, 8 NVIDIA v…
Classic sales maneuver, give numbers but make your numbers as incomparable as possible.