It's time for the #reInvent keynote about that most magical of scams: selling digital pickaxes into a data gold rush: Machine Learning®
Remember, Lambda has 100x more customers than its ML services, based upon statements made in two different keynotes earlier this week. That'd indicate that a lot of the talk around these services is likely hype-driven.
"Undifferentiated heavy lifting." DRINK! #reinvent
Honestly I really want to talk to the 6% of @awscloud largest customers who managed to avoid using any of these. What have you seen?! What can we learn from you!?
Another Spark plug!
(I do like Athena except for the part where I am very bad with SQL.)
Today's #reinvent keynote by @SwamiSivasubram has a narrative arc to it. That's a welcome change from yesterday's main keynote.
Ooh, reference customers for Amazon Basics MongoDB.
Also wait--did they rename it to "Amazon DocumentDB" from its former (and no I am not kidding) "Amazon DocumentDB (with MongoDB compatibility)"?
New: Amazon DocumentDB Elastic Clusters.
Okay, so is this DocumentDB (with @elastic compatibility) now?
Guest speaker from Expedia. I'm legit surprised that Expedia is not only still around, but big enough to be a featured #reinvent keynote speaker. TIL...
SageMaker removes some heavy lifting and also fixed my heavy wallet.
This is the key problem @awscloud has in Machine Learning®.
They offer things like this that you get to assemble yourself.
Meanwhile, @Azure has an API that my Twitter client hits to (completely automatically) handle the alt text for this image.
Customers want solutions.
New! Coming soon to a cross-AZ data transfer bill near you...
A new open source project that... *checks notes* makes it easier to use AWS's paid services for more workloads.
Yup, that's very "open source project at Amazon" on-brand.
Security sprawl meets Machine Learning® sprawl...
Hell yes another permissions management system.
♪ ♫ ♬ HIIIIIIIIGHWAY to the Data Zone ♪ ♫ ♬ @SwamiSivasubram'll take you right into the Data Zone ♪ ♫ ♬
Is this another bite at the Redshift Spectrum apple?
Potential correction for a comment upthread. I haven't had time to dive into the details any, but @_msw_ has a habit of being frustratingly correct basically all the time.
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