Hello from the Los Angeles #awssummit of Anaheim; it's livetweeting time.
In the summit app, the @awscloud billing services once again get snubbed. Sad!
And we're starting with an Intel processor video. Surely there will be nothing @awscloud says later in this presentation that could possibly imply that Intel processors were anything other than the absolute best option for all of your workloads.
And @mndoci takes the stage. He's the @awscloud VP of Containers and Serverless. So "basically every AWS service if you squint hard enough."
Talking about the Amazonian Leadership Principle of "Invent & Simplify (and then make it run containers)" and how it drives innovation company-wide.
Talking now about how the Space Shuttle's boosters are determined by the size of horse butts in ancient Rome; we've heard this before in previous keynotes that I've livetwote.
More interesting fact: the @casciencecenter is 26 miles away and has "Endeavor" there for viewing.
Getting the space shuttle maneuvered through the streets was an absolutely massive undertaking. They didn't let the horse asses contribute to the project: theatlantic.com/photo/2012/10/…
"With over 500 EC2 instance types, you almost certainly want to run containers to normalize them, right?"
Sorry, I kinda view the "Apple Silicon" processor option as something of a technicality here.
I confess I'm starting to build something new (more to come!) that unfortunately will live in Kubernetes. Early testing has been positive, and the entire thing is Arm architecture start to finish so far.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Step 1: spam the living crap out of everyone on LinkedIn
I too have problems hiring due to running into population limits of certain towns.
There are a LOT of people at the #AWSSummit watching this talk. If she doesn’t drop her email at the end with a “reach out if you’re looking to make a change” call to action then it’s a massive missed opportunity to hire.
It starts, as does basically everything, with a Jenkins job. A user clicks the button, and the Jenkins job makes an API call.
"What API?" you ask? Taskrabbit's. It hires a person on TaskRabbit to go to the bank downtown and retrieve the secret from its secure storage, which is a safety deposit box.
"Tell us your demographic information or there will be no Honeycode for you. We are not kidding."
Yes, there are "Prefer Not to Say" options for all three options, but if I wanted to be gated by a bunch of pointless mouse clicks I'd go spin up an @awscloud SNS topic in the console instead.
If I were completely amoral I'd simply set up a bunch of open source AMIs on the @awscloud Marketplace, charge more for "support" than the instance cost, and call myself something innocuous like "Supported Images."
That's such a good scam that of course someone beat me to it.
I see a bunch of replies attempting to reinvent my old scam: