The @LastWeekinAWS annual charity t-shirt fundraiser wrapped up yesterday. You wonderful, amazing people helped us raise $15,225 for @826National with exactly 500 shirts sold. The check is on the way, 826 folks.
I was out on parental leave for most of this. Some amazing people stepped up to help make this possible. Their work happened behind the scenes, though you clearly saw the results of it.
First, our delightful copywriter Lianna (@punchlinecopy). She's the only writer I've ever worked with where I have to say "that's HILARIOUS, but it's a bit TOO edgy." She's incredible.
Next, Corey Tiani of ptpx.works created the artwork for this year's shirt, as he did for last year's. He also does all of our design work for The Duckbill Group. Get yourself a platypus guy worth the namespace collisions.
Next, @kaisdavis is our go-to fixer--anything we need solved, whether it's email funnels, project management, brainstorming new content ideas, fighting a wolverine, he's on it. Kai oversaw the logistics of our campaign this year from start to finish, ensuring it went smoothly.
We can't forget @whiteleydesigns, our web designer. He's fantastic. He often takes the wild ideas we have from just designs and makes them a reality. We all know how frustrating CSS is but Matt makes it look way too easy.
I also want to thank the folks at @ConvertKit were (as always) a pleasure to work with for some of our more esoteric requests. It's been a weird year, and as always, we waited until the last minute to do this nonsense.
But most of all, thanks to each and every one of you who donated during this very strange annual t-shirt drive. The cause is great, and I'm excited to have been able to use my snark powers for good. We're already planning the 2021 drive. Start worrying, @awscloud!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Middle of the night alert from my @Synology. "Security risk found!"
The risk in question: I haven't bound SSH to a non-standard port.
Security myth: binding SSH to a non-standard port is somehow safer.
In practice, use keypair auth only; then the only benefit of a non-standard port is that your logs don't fill up with brute force attempts.
Security myth: rotate your @awscloud IAM credentials frequently so your console doesn't yell at you.
In practice, compromised keys are exploited in less time than it takes to microwave a burrito. Use role assumption if you can, but rotating keys is busywork.
Anomaly Detection for @awscloud bills is stupidly hard to get right. I’m optimistic about what they’ve built—now let’s see how it works in the wild! aws.amazon.com/blogs/aws-cost…
Me: “How hard could it possibly be?!” @mike_julian, monitoring wizard: “Oh my sweet summer child.”
...there might be some @awscloud UX teething issues.