Amazon SSM is a hidden gem. Today we’ll take a look at how you can stop dealing with SSH in order to issue remote commands to fleets of instances using SSM’s SendCommand functionality.
At Reverb we love to use terraform to define all our infrastructure. Not only does it serve as self-documenting, but it can be used as an auditing mechanism to spot any changes that were made by hand and stop accidental or malicious changes to our infrastructure.
We have recently started down the path of revamping our CDN infrastructure, moving away from Cloudfront, which is a nice default in AWS, to Fastly, which is a much more robust, programmable CDN.
Recently we implemented a utility that needed to store a bit of state between runs. This script could run on a number of machines (well, VMs) so relying on local filesystem was not a good idea.
A few months ago I wrote a post about Owning Our Data. In it, I detailed Reverb’s quest to enhance personalization and search relevancy beginning with standardizing our event data and funneling it all through one pipeline. Today, I’d like to follow up on that with a sequel of sorts, focusing on…