Crimes against cloud: an investigation

Also, a newsletter rebrand!

Housekeeping note - as old friends will observe, I’ve rebranded this newsletter from “Cloud Irregular” to “Good Tech Things”.

Two reasons why:

1. Flexibility: I’d like to explore tech topics beyond just cloud! But don’t worry, the “Cloud Irregular” essays will continue.

2. Consolidation: I’ve created a brand-new website called Good Tech Things that finally has all my cartoons, infographics, flowcharts, and tech songs easily searchable, scrollable, and shareable in one place. I am back to regularly creating new cartoons, and I hope you’ll bookmark goodtechthings.com for lots of nonsense about cloud, DevOps, AI, etc.

That’s it! On to today’s Good Tech Thing.

A unified theory of horrifying cloud experiments

On Twitter the other day I asked people to tell me about the most aesthetically horrifying things they’ve built in the cloud. Things that technically fall within the provider’s terms of service, but that no sensible person would ever dream of doing.

Specifically, I wanted to know about crimes people perpetrated against the cloud because they WANTED to, not because they HAD to. We all know the true cloud transgressions are mandated by business constraints and documented on SharePoint with words like “Progress OpenEdge-to-EKS integration” and “The production infrastructure is an IDE running in debug mode”. These stories make everyone sad. I want fun stories.

I was also not looking for projects that are zany, but use the cloud in a fundamentally straightforward way. Plenty of educational projects out there like Lars Klint’s Llama Cam fall into that category.

Instead I was looking for things like … well, here’s Vercel CEO Guillermo Rauch:

Guillermo Rauch @rauchg

@forrestbrazeal Running a Gameboy emulator inside a serverless λ function and sharing state across invocations to make it multiplayer 😆 pokeless.vercel.app

pokeless.vercel.appPokeless: λ plays pokemon

Yep, that’s a serverless function tortured into emulating multiplayer Pokemon on a Gameboy. The immediate question arises: why would someone do this? A Gameboy emulator is fun on its own, so why make things harder on yourself with such a weird infrastructure choice? Nobody who visits the web app will know or care how you hosted it. What’s the point?

Anyway, surely there isn’t a whole hobbyist industry of people smuggling state into AWS Lambda … oh, sorry, what was that?

boyter @boyter

@forrestbrazeal @norootcause A search engine (200 million documents) running entirely in lambda so AWS foots the storage costs.

boyter.orgAbusing AWS Lambda to make an Aussie Search Engine | Ben E. C. Boyter

Aha. We have our first working origin theory of ridiculous cloud experiments: People love to torture cloud services in order to squeeze more out of the free tier.

This practice is apparently not limited to serverless functions:

Glover @nathangloverAUS

@forrestbrazeal I wrote an ActiveDirectory database, that used AD As a key value store - I was annoyed at the cost of cosmosDB and saw there were no costs/limits on the custom attributes in AD objects. It was… pretty slow… but it worked?

(That sound you hear is the squeak of every Microsoft IT Pro’s sphincter clenching at once.)

But parsimoniousness isn’t the whole story! It isn’t even always part of the story! At the opposite end of the spectrum, we have people committing cloud crimes that are nonsensically MORE expensive than they have to be.

The canonical example of this is surely Dyna53. Yes, that is a key-value datastore using AWS DynamoDB semantics … built on top of DNS TXT records. This project is explicitly identified as a joke. But it’s a joke backed, I think, by love for the world’s original highly-available distributed data store. Dyna53 has a message, and the message is “We appreciate you, DNS!”

Similarly, here’s a chat server and a RISC-V emulator somehow implemented on top of a container registry. The point of doing this is maybe a LITTLE bit to show off - but mostly to celebrate the flexibility of the OCI spec.

Or, most horrifying of all, there’s this, a putative love letter to the power of AWS CloudFormation custom resources:

Ian Mckay @iann0036

You can now use @AWSCloudFormer to buy and sell US stock. Now you can reward yourself on a successful CloudFront deployment by buying some $GME within the same stack. 1/

If you are going to deploy that, I would highly suggest enabling drift detection.

All of which leads to theory 2: People abuse the cloud to show their love for the cloud. That probably looks toxic when you write it down, but it’s fine. We’re all fine. Everyone’s normal and well-adjusted here.

Maybe everyone except Aidan Steele.

Aidan W Steele @__steele

What's the silliest use for 281 trillion IP addresses? I made a thing that uses the new-ish AWS EC2 support for assigning IPv6 prefixes to EC2 instances. You can only connect to the instance when the IP ends in a TOTP 6 digit authenticator code. How/why:

github.comGitHub - aidansteele/ipv6-ghost-ship: Silly usage of AWS EC2 IPv6 prefixesSilly usage of AWS EC2 IPv6 prefixes. Contribute to aidansteele/ipv6-ghost-ship development by creating an account on GitHub.

No, Aidan.

Aidan W Steele @__steele

Now that re:Invent 2022 is done, how are people feeling? Impressed with the releases? Underwhelmed? Wishing there was just a little less respect paid to the laws of physics? If it's the latter, I've got you covered with vpcdelorean.

github.comGitHub - aidansteele/vpcdeloreanContribute to aidansteele/vpcdelorean development by creating an account on GitHub.

Why, Aidan?

I have never met Aidan Steele. I don’t know anything about him except that he periodically shows up to cloud Twitter with … an upside-down-ternet, or auth rickrolls, or whatever this is. His shtick goes beyond “I will bend the cloud into a pretzel to prove how clever I am.” He has passed into the realm of performance art, or maybe Zen. Asking why is like listening for the sound of one hand clapping. I hope he never stops.

But Aidan’s chaos points us toward a fundamental motive for cloud crimes, a unifying theory that ties together stock-trades-as-YAML and serverless-golf and Turing-complete container registries and all the rest. Ultimately, we build these things not because they are easy, or because they are sensible, but because they are funny.

You probably can’t understand software engineers until you understand this.

Look, the cloud is enormous and overwhelming and filled with one million services that are billed across one billion incomprehensible dimensions. And I think that inspires in us, as developers, sort of a Kafkaesque spirit. (Franz or Apache, what’s the difference?)

It’s funny to take a very serious enterprise software service and wear it on your head like a hat. It’s funny to imagine some poor PM with a usage-based KPI watching their numbers go up and whispering to themselves: “Not like that.”

It’s funny that we were always warned about vendor lock-in. Hey vendors, it’s time you learned: You’re all locked in here with us.

Again, check out the new comics site!