Welcome aboard Bill Lumbot

Every morning I try to follow a checklist that I wrote.

I read over resumes, check out PRs, check my email accounts, etc… One critical thing I do (or did) was checked to see who forgot to log their hours from the day before (or who left the timer running). Since we are a consultancy, it’s important not only that we log our hours, but that we log them correctly, and if we catch ourselves forgetting at the end of the month there’s no way we’re gonna remember what we worked on that day. So, it’s an important task. Unfortunately, it’s a thankless one, I don’t enjoy doing it and it makes me feel like Bill Lumbergh from office space, asking people to fill out their TPS reports.

One of our core values at RunAsCloud is automation. When building out cloud infrastructure, automation ensures that we can push something out quickly and consistently. When helping clients push code we build an automated pipeline to ensure that deployments happen easily and without the worry of someone accidentally fat fingering something.

As such, I’d like to introduce our newest addition to RunAsCloud, Lumbot. Lumbot is a slackbot that runs in AWS lambda toward the end of every workday. He is alerted via a Cloudwatch Scheduled event and proceeds to check our engineer’s timesheets, look up anyone who may have forgotten to update via slack and send them a polite reminder so that I no longer have to.

Unlike his namesake however, Lumbot won’t be asking you to come in on Saturday (his cron is only scheduled to run on weekdays).

Jake Berkowsky

Leave a Comment


Capital One and EC2 Hack – an Overview

By Nate Aiman-Smith | August 5, 2019 |

There’s been a ton of coverage of the recently discovered Capital One breach. I’m generally very skeptical when AWS security makes the news; so far, most “breaches” have been a result of the customer implementing AWS services in an insecure manner, usually by allowing unrestricted internet access and often overriding defaults to remove safeguards (I’m looking at you, NICE and Accenture and Dow Jones!).  Occasionally, a discovered “AWS vulnerability” impacts a large number of applications in AWS – and it also impacts any similarly-configured applications that are *not* in AWS (see, for example, this PR piece…um,…

Read More