I spend my free time trying to be a decent parent, cultivating mindfulness, reading, watching weird and/or terrible streaming, learning Spanish on Duolingo, playing RPG games, and listening to a wide variety of music.
I work in web technology with a passion for learning and adapting. I’ve been building web applications for decades. Now I focus on cloud infrastructure and reliability engineering.
I’m generally more interested in the “why” of things before I start thinking about the “how”.
At the end of 2015 Amazon added support for encrypted EBS boot volumes. EBS storage volumes had offered optional encryption for some time before that. Now it’s possible to encrypt an AMI and bring up EC2 instances with fully encrypted starting volumes. I set out recently to use encrypted EBS boot volumes for a HIPAA compliant project at ReactiveOps. It’s very easy to convert an existing AMI with an unencrypted boot volume to use encryption....
In my post on building a serverless URL shortener I neglected to mention API Gateway models at all. A model defines a JSON schema for data passed in or out of API methods. Models are assigned to method requests/responses. They play a role in data transformations that happen within mapping templates. Models are not used for validating input data. That seems like a logical use for them so perhaps they will serve this role in the future....
In my last post Build a serverless URL shortener with AWS Lambda and API Gateway services I walked through creating a URL shortener service using Amazon’s API Gateway and Lambda services. One of my goals for that project was to use a custom domain instead of the randomized URL provided by API Gateway. This turned out to be trickier than I expected. API Gateway supports custom domains but it requires an SSL certificate....
I’ve had my eye on Amazon’s Lambda and API Gateway services for a few months. Running a web application without the costs or headaches of maintaining servers is attractive. Of course, no platform is without tradeoffs. So to get myself familiar with the finer points of serverless apps I decided to launch a simple project: a URL shortener service. With a few hours of work and a few dollars per month in cost I got a decent prototype working capable of handling millions of requests per month....
No one ever says: “I want to ack PagerDuty alerts when I grow up”. Lost sleep. Diverted focus. Scrambling under pressure. There’s no shortage of downsides to being on the frontline for a business’s technology. Still, a well run on-call rotation is key to the proper care and feeding of any company’s technology stack. A healthy on-call rotation shines a bright light on weaknesses and implements improvements with urgency. It requires a team with sharpened communication practices to do it well....
A little over three years ago Hector Castro brought up an idea he had for starting a DevOps meetup in Philadelphia. We both agreed that existing user groups weren’t covering many topics bridging the gap between developing and operating software. So we organized the first Philly DevOps meetup in July of 2012 and we’ve hosted regular monthly meetups since then. Every so often somebody asks: I want to start a meetup....
Over the past few years I’ve worked on opposite extremes of the remote/on-site workplace spectrum. My current employer maintains top notch office facilities complete with chef prepared lunches, bio-walls, lego murals, and slides. Previously, I worked with a fully distributed company of 75+ people that had a strong culture and no physical office space at all. There are definite trade-off’s to both types of working environments. Whether your team is on-site or on-the-beach, I’ve learned that teams can find serious benefits in adopting remote-first communication patterns....
Running a suite of tests in the same order always can mask unintentional dependencies between tests. You can end up with a test that succeeds in a full run of the suite but fails by itself. One way to shake out these dependencies is to run tests in a random order. RSpec has an –order option that you can use to randomize test order for each run. rspec --order rand...
My team recently setup CI for a few Rails projects using TeamCity at work. When new commits hit a project’s repo if an RSpec test run passes the CI setup deploys the code to a Heroku site used by our QA team. One way or another some specs started failing on a project but the code still deployed to Heroku. That’s not how it’s supposed to work. TeamCity looks at each command’s exit code to determine if a CI step fails or succeeds....