All right, Twitter; time to kick the @awscloud tires on these new Graviton2 Lambda functions.
Now, @alex_casalboni has already done the heavy lifting for me with this dingus.…

It supports the new runtimes even!
I'll deploy it through the Serverless Application Repository, meaning I'm now a full third of that thing's customer base for October.
Now I need a Lambda function to test this on. Fortunately I have one that fires off once a minute, is idempotent, and powers the horrible yet strangely compelling @awscwoud.
Let's give this config a shot. (Somewhere an AWS employee is looking up the account ID and discovering that the globally unique account alias for this @awscloud account is indeed "Shitposting.")
And we're off. Now I wait a smidgen.
There we go. No surprise, "cheap" or "good" are the options here. Now let's see if this asplodes when I kick the Lambda over to use Graviton2.
I use the advanced DevOps IaC approach of "using the @awscloud console, then lying about it" to make the change. Yes, I really did call my handler that.
(Had to repackage and re-upload it just because I'm a sensible person who sets code packages to expire.)
Now we run the thing and see if it melts. Hope with me!
Excellent job hoping. Let's see.
I don't know about you, but looking at five zeros before a number doesn't help me get a sense of cost overly well. Fortunately @alex_casalboni has thought of this with the handy "Compare" button.
It looks like 256MB + Gwaviton2 is the most cost effective answer here unless I misread the admittedly complex chart. Am I right?
John is completely correct, but remember that this is a backend job. The latency absolutely does not matter; @awscwoud doesn't need to respond THAT quickly.

An update on my Graviton2 Lambda conversion. The most obnoxious part was getting the tooling updated to support the new configuration. The wrapt library by default compiles a C extension; you can override it to use pure python, but that's not straightforward.

• • •

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

Keep Current with Corey🎃Managed NAT Gateway 🤡 Quinn

Corey🎃Managed NAT Gateway 🤡 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!


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

27 Oct
Hello, and welcome to our company's oh-so-very-shitty Security Awareness Training. I'm Chief Cloud Economist Corey Quinn of the Duckbill Group, and I'll be delivering this training for you because I was absolutely NOT the lowest bidder for a change.
The whole point of security awareness is to protect company information. That's what they say, anyway. Here in reality we're going to reference back to the things I spew at you rapid fire and blame you for our institutional shortcomings once we get breached.
Confidentiality is important. Assume that people will read what you write. I know, it's a heavy lift for some of you who haven't figured out that the failure mode of "clever on Twitter" is "being a huge asshole," but pretend it'll be read.
Read 33 tweets
26 Oct
A second CloudTrail management trail that you never look at.
A developer advocate who can't pass PR certification.
Read 4 tweets
26 Oct
So it's probably time I pick this back up.

Let me begin by saying I'm *pretty* sure that this isn't sour grapes; I left ten years ago as of six weeks from now. I have no financial stake in Expensify, but I do have stories. I was the "Director of TechOps" for a year.
Let me further disclaim that my information is thus a decade old. I hope it's all ancient history, but these stories have a way of helping people out. I hope and trust that as we all have, the culture there has evolved significantly.
First, the good parts. I've never seen a place that was as good as Expensify was about onboarding junior engineers and training them basically from scratch. "Senior engineers are expensive, so we'll hire them before they get there" is a great philosophy.
Read 29 tweets
26 Oct
Now that I'm back from vacation, this is worth a small thread.

Short answer: Yes but you don't want to do it.
You can fork the SSPL or Elastic license or what have you to only include @awscloud, but it's 1. not Open Source® so people will yell at you for it, and 2. it betrays a significant misunderstanding about how AWS works.
Let's pretend that we're talking about `cowsay`, an open source tool that's been around for decades, is written in Perl, and outputs text in terminals like this.
Read 9 tweets
20 Oct
I’m going to have to talk about this at some point, aren’t I…
The “database” was not the worst thing by far about Expensify.
This may have been. I resigned, but others didn’t. They don’t deserve this kind of shitty character assassination.…
Read 5 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!