Thread by @QuinnyPig

It's been a while since I gave @awscloud a livethread exploration.

For novelty based upon today's Amazon Linux issues, let's focus on Amazon Linux 2022, in the new EC2 Launch Wizard, in the Northern California region. Like the instance name, this is a 💩📬🧵.

There is something ever-so-slightly-screwy when a search for a full AMI ID returns over 5K results.

With only a slight bit of whining about needing to manually set IOPS for a gp3 volume, we're in. Yay.

lsmod shows only a few things loaded, which is good for a minimal install. rpm -qa | wc -l shows 287 packages installed, 1.1GB taken up on disk.

The version of python that would be installed could best be described as "unsettlingly modern for an enterprise distribution."

Let's see what's going on here. 'yum provides' tells me that the tools I want live within the "pcp-system-tools" package; the "pcp" portion is because I'm about to cause incredible amounts of mayhem at this rate.

This system is, like an AWS corporate comms person without a looming crisis to worry about, bored out of its mind.

Not super thrilled that IMDSv2 isn't mandated for new instance spin-ups, (I'd love an SCP to that effect-- #awswishlist) but at least it's enabled.

Retrieving tags from IMDS needs to be explicitly enabled for the instance. Okay, fair.

AL2022 is based upon @fedora, which targets a lifecycle of roughly 13 months. Y'know, twice the lifetime of a Google consumer product.

@awscloud is committing to support each AL2022 release for five years.

*DING* goes @bitintegrity's email with a Career Opportunity.

"You were involved with the CentOS project, so you either know how to support a distro for a decade, or alternately rug-pull your customers with a year's notice, depending upon your preference and era. Wanna come be sad all the time again?"

"Can I use Extras, or EPEL, or RPMforge?"

"No," says @awscloud, "but you can create your own RPMs."

"Got it, I can use Docker and npm," responds anyone with half a lick of sense.

This screenshot will upset almost everyone, and will likely be the tweet that causes people to finally snap and come for me.

I have absolutely not forgotten that sudo's logo is a horrifying anthropomorphic sandwich, so let's fix that real quick.

And this basically kills the crab, so the experiment ends here. I'm turning it off, as a t2.micro in us-west-1 is roughly 16% more expensive because everything here in San Francisco is.

So far, so good, @awscloud Linux team.

Remember to install npm and Docker!