You know what's hard to get right? That's right-- calendars. I'm in Seattle next week, not this week, for Microsoft Build. I'll be coordinating an event on Sunday evening via Twitter; follow me there for details / depressing levels of snark.

This week's issue of Last Week in AWS is sponsored by a former client of mine, Sharethrough. Their infrastructure (and culture, if I may say so) is awesome; consider helping make it even better!

Sharethrough is hiring our first Site Reliability Engineer. We believe SRE should be integrated into the product execution pipeline. So you’ll be embedded into the core engineering team, which is a team of developers skilled in DevOps. Don’t worry, you won’t be cleaning up a mess brought by no ops. Instead you’ll work collaboratively, paving the way for scaling our already-solid infrastructure to at least 10x its existing throughput. We have 5PB of data and a multi-million dollar AWS bill, so it's safe to say you'll have some interesting challenges! You'll be walking into a welcoming and diverse environment that is built around action, optimism, purpose, and transparency. We have a fun, supportive culture that welcomes being challenged. Read more about what it's like working at Sharethrough and apply via our site.

Community Contributions

Here's one for the business-oriented contingent of my readership: CapitalOne's VP of Cloud Strategy Bernard Golden writes about the CapEx spend strategy of the large cloud providers. His analysis is indeed Golden.

re:Invent registration opens May 15th. There are a lot of good reasons to go, and I'll be there. Other folks strongly disagree. I see where they're coming from; the logistics were a poop carnival, it's spread across too many locations, and you never get to see all of the people you want to see. Then again, where else can you randomly bump into Jeff Barr that isn't Seattle / profoundly creepy of you?

Epsagon takes us on a tour of Lambda Internals; it goes deeper than most of these articles do. I like what they're putting out.

A Cloud Guru has the missing manual for Greengrass, one of AWS's most overlooked services. I still want to put Greengrass inside of a container, schedule it with Fargate, slap it behind an NLB, and boom: I've built a Lambda equivalent without vendor lock-in. Somewhere in Seattle, someone just blacked out as a self-protection mechanism.

When Admiral Kirk finds your platform too complicated, it’s time for some soul-searching.

And finally, I was cornered and coerced into giving my thoughts on hiring engineers last week. Yes, I used to build and run ops teams. I don't miss having to self-censor.

I’m Corey Quinn. I help people significantly reduce and understand their AWS bills and speak broadly on the conference circuit. I advise companies doing interesting things in the cloud space, such as ReactiveOps.

If you've enjoyed reading this, tell your friends to sign up at lastweekinaws.com (or post a link in your company Slack team!) about it. As always, if you've seen a blog post, a tool, or anything else AWS related that you think the rest of the community should hear about, send them my way. You can either hit reply-- or join the #lastweekinaws channel on the og-aws Slack team.