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