Let’s try something different. What @awscloud concept are you struggling with? Let me help explain it or find someone who can.
The way accounts were designed originally. "Hard to delete" and "at no point is there not a way to bill for charges" are fundamental tenets of the architecture.
"Small teams each implementing their own things" is how @awscloud works. Anything that has to touch everything (console, billing, tagging) is a patchwork mess, because "Console Czar" isn't how they do things there.
CDK is the path to provisioning infrastructure for developers who aren't steeped in AWS / ops-land. Make no mistake--it is the future, and it's coming. These are early days, which is why it's so rough.
"Watching it at first to make sure it doesn't run away," then a stop-task scheduled, and/or a billing alarm. It's not ideal yet. I haven't checked whether Copilot has something for this yet.
There really isn't one (short of working with the file as a stream instead of an object via API) until S3 lets you manipulate compressed files directly. This is a good idea. #awswishlist
You can scope down the ListBucket permission to a prefix, but sadly that's about it. Read-after-write consistency means the error should be a lot more predictable now with fewer edge cases; cold comfort.
This one resonates. There's a lot of things to learn up front (EC2 or similar, Lambda, VPC, IAM, "the console," etc.) before you build your first thing. The learning curve flattens out after that, but it's front-loaded.
Oh my stars yes. A great new release is the VPC Reachability Analyzer which will at least tell you why the networking isn't letting the traffic through.
I'll catch hell for this but "the console." It gives you a better sense for how the teams imagine people will interact with their service. You can always tab-complete your way through the CLI, after all...
Build a role for them to assume from their own AWS account. Enable CloudTrail management events so you can keep an eye on what they do. Terminate their access when they're done.
Once upon a time, the tagging team had to support all the services. Then one day that shifted and the burden fell to the service teams. Some got the memo sooner than others.
AWS Organizations is a way of organizing multiple accounts in a hierarchy and breaking apart the "one AWS account" model. Control Tower is in theory aimed at making this easy to manage at scale, and in practice is clearly unloved by its own team.
Because everything that touches IAM is sensitive, scary, and scrutinized to death by very, very smart people. But #awswishlist needs to take a look at this, as does @jim_scharf.
I do this myself, and then visualize it via Tableau.
The blog posts about this are all... kinda limited. @petecheslock / @jesse_derose / @nerdypaws, let's see about putting together a post on this. I like the idea.
Oh my god this interview starts off bad and gets worse. You might want to mute this thread if you don’t like rants / don’t like the sight of @ibmcloud blood.
“@Gartner_inc is paid advertising” may be the dumbest thing I’ve seen all week. You can certainly pay them, but you cannot buy them. Take that as gospel.
Yes, those companies famously just want the basics. Like a cloud that a single third party route announcement can take completely down globally for hours at a time.
As much as I appreciate @awscloud's "spend all of your money to find out why you're spending all of your money" approach here, this is approaching "step 17, overpower the wolf" levels of hilarious complexity for disappointing outcomes.
This blog post has, and I am being completely serious, 56 steps you must undertake to arrive at the disappointing outcome.
The whole premise of the Venture Capital model is that founders perform on command as VCs sit in judgement, only to basically crap on them and decline to invest.
In this thread, let's turn that on its head. Name companies @a16z has invested in, and I will crap on them for it.
When @a16z declined to help Google hire engineers, Google heard that as "well, we can't help you *DIRECTLY*..."
Congrats to @revue on their @twitter acquisition. Now, some thoughts on paid newsletters.
Last Week in AWS (lastweekinaws.com) is my snarky email newsletter. I have ~23000 or so subscribers.
There are some folks (Revue is one, @substack is another) that would urge me to write a paid newsletter, to which subscribers are the revenue source.
Unfortunately for my model it's a complete non-starter. Basically none of you you would pay say, $100 a year for my ridiculous ranting nonsense. I might be wrong on that but I seriously doubt it.