Some are snarky, some are true, and all come from hard-won experience. These are #awsfacts, and for every ten (10) retweets this tweet gets, I will share one of them with you until I either run out or get bored.
S3 "Reduced Redundancy" storage is mostly deprecated; stop using it. In most regions it costs *more* than Standard storage and gets you absolutely nothing but a worse SLA. #awsfacts
It doesn't matter how fast the EBS volume is--you're throttled by some instance limits that vary per instance size and family, so faster volume types are just burning money. docs.aws.amazon.com/AWSEC2/latest/… has the details. #awsfacts
You all know the Rumplestiltskin story, but who the hell named a baby "Rumplestiltskin" in the first place? @awscloud. #awsfacts
S3 Infrequent Access and S3 Infrequent Access One Zone both have the same SLA--because "theoretical loss of an AZ" and other disasters don't factor into SLA calculations. HAPPY DR PLANNING SEASON! #awsfacts
Most emails from AWS employees ask for feedback at the bottom. As an AWS job applicant you will never receive feedback other than "hire," "no hire," or "they called the police to remove you from the building." #awsfacts
Christmas may come once a year, but the AWS bill comes once a month, usually around the third. Larger companies with enterprise contracts usually see them somewhere between the 8th and the 15th historically.
Move 1TB between two availability zones in the same region, and it will cost you $20.48 and show up on the bill as 2TB of data transfer. #awsfacts
Move 1TB between two different regions, and it will cost you $20.48 and show up on the bill as 1TB of data transfer. #awsfacts
Move 1TB between us-east-1 and us-east-2, and it will cost you $10.24 and show up on the bill as 1TB of data transfer. #awsfacts
"F*ck, Marry, Kill" isn't just a sophomoric schoolyard game; it's also the AWS partner strategy. #awsfacts
CloudFront distributions and Lambda Edge functions log to most / all of the public regions; you can't tell them to directly log everything to a central location. Now you know why there are so many log analytics companies. #awsfacts
Many aspects of how @awscloud services work behind the scenes are non-public. Sometimes it's because they don't want to lose a competitive advantage.
Other times it's because they are deeply and profoundly ashamed. #awsfacts
The business tier of @AWSSupport costs you at least $100 a month. Enterprise support costs you at least $15,000 a month--but the latter applies to every account you have whereas the former is per-account. With enough accounts it saves money. #awsfacts
The AWS product strategy is highly confidential, but I've attached it to this tweet anyway. #awsfacts
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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
It's once again the most wonderful time of the year: the newly-renamed @Gartner_inc Magic Quadrant for Strategic Cloud Platform Services!
This year there are no visionaries or challengers, just "cloud" vs. "you pretend to be a cloud." Let's explore together!
We're going to ignore the "niche players" because for three of them I don't speak Mandarin, and for @IBMcloud I don't speak ancient Greek.
That leaves @awscloud, @Azure, @googlecloud, and @OracleCloud.
@IBMcloud @awscloud @Azure @googlecloud @OracleCloud First up is AWS due to its undisputed alphabetical supremacy.
Strengths include its "everything but the kitchen sink" approach, its innovation in hardware design, and its large feeding ground--I mean, partner ecosystem.
Amazon Q / "an AWS spokesmodel" is easily proving incredibly, incredibly helpful at answering the @awscloud questions its human predecessors in corporate comms refused to address.
According to an AWS spokesmodel, EC2, S3, and DynamoDB have all seen price increases. I did not know that!
I was missing a handful of these on my deprecation list; thanks, AWS spokesmodel! You're incredibly helpful!