Ask me no questions, I'll tell you no lies--but that's super boring. Instead, ask me your @awscloud questions.
Go!
I don't have any particular roadmap insight, but it's probably something like "Service X now supports Feature-You-Thought-It-Had-Already" and *should* be called AWS Housekeeping.
Because you're mistaking Cognito for an actual service that customers would use instead of what it really is: a brilliantly executed marketing stunt by Auth0.
This is the second time I've heard this complaint today. It's not something dumb like "your perf measurements on gp2 don't account for the burst performance when you first provision it" or something, right?
That's... a hard question. "Stop rolling out new features" is never something customers want--but they also want technical debt cleaned up. The debt is whatever keeps AWS from being able to walk and chew gum at the same time...
False! Step 1 is always "construct an IAM role / user / policy."
This is what happens when you have an interdepartmental meeting to talk about hitting everyone's adoption metrics and forget to invite someone like me to ask "are you out of your tree" at the proper moment.
I would never say I "knew AWS." Nobody has it all in their heads.
That said: for the common use case? EC2, IAM, S3, VPCs and maybe RDS are enough to get started. Anything beyond that, we're all learning together more often than not.
There are way more efficient ways of blowing $10K a month on AWS bills. From a governance perspective? Organizations, yes; Control Tower, only as a counterexample.
I don't think anyone's suggesting you run a Docker container in Lambda. The recent changes mean that you can package and ship Lambda functions the same way you do Docker containers, but that's not the same thing.
Because they want to vacate old hardware, not "buy more of it." The price cuts take the form of improved price/performance numbers on newer generations.
Then they can use the old ones for Lambda, Fargate, groundwater pollution, etc.
Cynically, I'd say they already have. Otherwise it'd be easy to blow away test accounts without a phone call, payment instrument, and a bunch of manual steps.
No matter how you slice it, the answer remains the same: @awscloud's strength is in their employees. Destroy morale, lure their staff away through various means, or limit their ability to be effective.
No clue, but what's "next" is not having to think about underlying infrastructure. "Here's a data structure, hold it somewhere for me. Now, transform it like so..."
Understand the failure modes. Lambda@Edge has to be deployed via us-east-1, but it doesn't live there. If us-east-1 is down, you won't be able to deploy new Lambdas @ Edge, but your existing ones will continue to function.
No, serverless models / principles are the future. Containers are a way for existing workloads to drift in that direction, which is important; if you want to herald in the future, you can't do it by making the present feel ashamed of itself.
Unfortunately the company to yell at is @nvidia. AWS is using their 8-GPU cards for p4d instances. I suspect they'd have a problem making these smaller and still guaranteeing throughput to all tenants, but that's a stab in the dark.
What does it mean to work at IBM? A bunch of things that absolutely don't apply to a corporate comms role. Get any thoughts of being valued right the hell out of your non-coding head immediately.
That said, I will take the beta exam cold and report back if AWS finds a voucher / wants to drum up publicity.
I'll even turn it into a fundraising drive.
If @PearsonVUE decides that an infant or toddler in the next room being noisy voids the exam, I will rain fire and brimstone down upon @awscloud for it.
Sure, it's a Pearson requirement--but it's being done in AWS's name.
Spent the morning setting up @JamfSoftware to manage our company Macs. I've spent so long working with cloud computing that it's unnerving to encounter an interface that doesn't actually hate its users.
Given that I'm a few clickety-pokes away from blowing away a workstation at any point in this thing, I'd want two factor auth to: 1. Support Yubikeys 2. Not be optional 3. Not be buried deep in a sub-menu I had to hunt down.
They all have the red dot in the corner since I haven't enabled app provisioning. I just want to mandate disk encryption, strong passwords, screensaver timings, and remote wipe (AFTER ANOTHER 2FA FOR GOD'S SAKE JAMF)! I can't view those things in the dashboard though.
Screw it, I've got a few minutes. I'm starting a new imaginary corp, "Facebook for Ethics." We're based here in California. I'll walk through many of the ways we'll serve our core mission: absolutely screwing over our staff.
Any resemblance to real companies is coincidental.
We'll start with "unlimited PTO." We very carefully will avoid giving guidance as to what is "appropriate." Is it really unlimited? Try taking six months off and find out!
We need pay none of it out when you leave (voluntarily or otherwise).
We're VC backed and privately held, so we'll pay below market salaries and offer equity. Folks have gotten wise to the "options" game so we're forced to give RSUs to attract talent.