Corey Quinn Profile picture
30 Jan, 26 tweets, 11 min read
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.

This should change. It's 2021.
"Programmatically provision resources as defined in JSON / YAML / #awswishlist XML."

They're wordy, a bit finnicky, and a lot of projects and tools use more human-friendly things that get rendered into CF.

I struggle too.
Because this looks an awful lot like "a bug" or "an abuse vector" to the original designers of CloudFront, unfortunately.

Have you tried this between multiple accounts?

"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.

X-ray is and will remain a "failed product" until it reaches critical mass across sufficient services. This Is Not The Way. I'm sorry.

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

Because some jackwagon tried to use Route 53 as a database once and they're still recovering from it.

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.

Console interfaces? Because they are trying mightily to fix their UI issues, with varying levels of success from team to team.

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.

It is Complex and unintuitive for sure.

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...

I use Amazon Glue for this; that's basically what it's designed to do. Glue v2 is a lot less spendy.

At launch, EKS basically just needed admin rights to provision it. That's improved, but docs.aws.amazon.com/eks/latest/use… is wildly optimistic about what's needed. #awswishlist
Shame, mostly. Slightly more seriously, I think they want to be able to deprecate these if needed; they can't if they're public interfaces.
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.
It sounds like I'm trolling you but I promise I'm not: if it needs to run continuously use Fargate, if it needs to run on a schedule use CodeBuild.

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.

Lambda functions triggered by scheduled CloudWatch Events is the canonical answer.

Personally I prefer to use an ec2 instance with a crontab.

If it exists, I haven't seen it. It's also why I don't use CloudWatch dashboards myself. #awswishlist

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Corey Quinn

Corey Quinn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @QuinnyPig

30 Jan
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.
Read 7 tweets
29 Jan
Ahahahaha oh absolutely not.

aws.amazon.com/blogs/machine-…
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.
Read 4 tweets
28 Jan
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*..."
a16z: "Hah, can you believe we got $8 billion from Microsoft!?"

It's this decade's alternate history of "HELL YES, we sold Google to Yahoo for $1 million!"
Read 8 tweets
26 Jan
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.
Read 13 tweets
26 Jan
My favorite part is the homage it pays to Charlie Chaplin.
Anne Frankly, it's out of Mein Kampfertzone.
Read 5 tweets
26 Jan
How productive have you been lately?

We turn now to @GitHub's VP of Strategy, Research, and Ass-Kicking, Dr. @nicolefv and her report on productivity from last month.

octoverse.github.com
You can get insightful research around data.

You can get awesome graphics.

But only @nicolefv combines the two.
So big pull requests suck, humans suck at repeatable things, open source makes for a fun hobby, and devs are weird.

A bonus fifth item: anything can sound obvious and dumb when I reduce it to something absurd on Twitter.
Read 14 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!