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
I'm at the AWS Summit in NYC, where I believe that nicknames are for friends--and Gennifer Artificial Intelligence is no friend of mine.
Good morning.
Thirsty much?
A game / challenge at the AWS Startups booth: how long can an AWS employee go without mentioning GenAI? Someone just made it all the way to one minute, ten seconds!
Okay. Let's do Networking Specialty. Practice question 1:
Correct answer is B.
"Wrong!" says the answer key, "it's B because network load balancers don't support client IP preservation."
Except that they do. They absolutely do. They have for the past year. I'm just a boy, standing in front of an AWS Cert team, asking them to do their damn jobs.
Today's cloud marketing story is called "The Tale of Hot Rebecca," and is a truthful recounting of dinner last night.
Strap in; it's a fun ride.
Back in my early 20s, I had a number of friends / acquaintances in my (primarily Jewish) social circle named "Rebecca." It was kind of a problem.
("Can't we spray for them?"
"…not since the 1940s.")
So every Rebecca got an adjective, much like the seven dwarves. One of them asked me once what her adjective was, and I responded in a fit of unadulterated honesty, "you're Hot Rebecca" because honestly? Damn.
Made it to the #GoogleCloudNext keynote seating finally. Let's see how this goes now that the world is starting to wake up to a "much of the AI hype is unwarranted" reality.
Boeing: "HOW ARE THEY DOING IT?!"
Airbus: "We bought a torque wrench?"
Boeing: "No, how are you being a featured customer testimonial at #GoogleCloudNext?"
Airbus: "Oh, that? We made a strategic decision to not be walking poster children for corporate negligence."
And now, some DevOps / SRE / Sysadmin / Ops / ENOUGH already tips I learned from early in my career--brought to us by our friends at Chex™ Mix. All of these are great ideas that you should implement immediately...
DNS is notoriously unreliable, so use configuration management to sync all of the servers' /etc/hosts files. Boom, no more single point of failure.
Future-proofing is an early optimization, so don't do it. Every network should be a /24 because that's how developers think. I mean come on, what are the odds you'll ever have more than 253 hosts in a network?
And the Amazon earnings are out for Q4. A miss on @awscloud revenue by $20 million because analysts didn't expect one of you to turn off a single Managed NAT Gateway.
Let's explore deeper into their press release.
For 2023, AWS sold $90.8 billion of services, most of which were oversized EC2 instances because you all refuse to believe Compute Optimizer when it tells you there are savings to be had if you're just a smidgen more reasonable.
Word frequency in the earnings release:
Customer: 87
Employee: 11
Generative: 16
Cloud: 24
Serverless: 3
DynamoDB: 2
Union: 0