Last month I wrote about the installation script I built for Igor, but as I started writing more Lambda functions recently I realized that I needed that same functionality in a more easily accessible way. So I created Aqua to do this for me.

I wrote about version 2 of the Go SDK for AWS over 3 years ago. At the time it was just available in beta/preview mode and I expected it to become GA a bit quicker than it did. But now it's finally here!

Last week I wrote about AWS SSO's CloudFormation and how (with some assistance) that can be used to manage your permission sets and assignments of those permission sets. Today I want to take a bit more positive look at the actual underlying APIs.

Last month I was lucky enough to be asked back to give a workshop at the Melbourne AWS Programming and Tools Meetup. This meetup is always a lot of fun as it's all about going hands on. My subject this time around was CloudFormation Macros.

In this tutorial we will set up a basic Hugo project and then configure a free tool called Wercker to automatically deploy the generated site any time we add an article.

At the start of the year I mentioned writing a step for Wercker to help with automating deployments for Hugo sites such as this site. In the community forums people requested that I write a tutorial for it, and that has now gone up on the site.

It also works as a general introduction of using Wercker steps, so even if you’re not interested in Hugo itself the tutorial might be useful for that purpose.

I mentioned that I was planning on building a step for making it easier to deploy Hugo sites using Wercker, and I've done so.

A 5 minute introduction about AWS CodeBuild. What is it, how does it work, and what are some of the good and less good things about it.

A 5 minute introduction about AWS Fargate. What is it, how does it work, and what are some of the good and less good things about it.

With the release of the Go runtime for AWS Lambda, I took the opportunity to convert some of my code to run natively instead of through wrappers.

Almost 2 months ago, AWS announced a serverless chatbot competition. As I happen to have one of those lying around I decided to enter this competition.

Over the past couple of weeks I've written several articles about the things that support Igor, from deployments to installation, but I haven't written much about how it actually works yet. This article aims to rectify that.

At the Docker birthday event last week I decided that instead of working on the Birthday Challenge I would make Igor work on Docker as well. That meant I need to deploy two versions from a single build however, and in this article I'll explain how that works.

I gave a short lightning talk about automating the creation of AWS API Gateways at the AWS Meetup. This is based on the work I did for that on Igor.

For the Golang Hackday in Melbourne I gave a short presentation about Igor, my Slack bot written in Go and running on AWS Lambda. The presentation was partially aimed at beginners of Go.

When I set up Igor in Lambda for the first time, I mostly followed the directions as provided in a Lambda template. This template has a description of all the steps that need to be taken, but to be honest it's a bit unwieldy. So I created a script to do this for me.

For Igor I wanted to make sure that there is always a compiled, and up to date, binary ready for download. The obvious way for me to do this was using Wercker, but this turned out to be a bit more work than I expected, so I'm documenting it here.

Over the past weeks I've been working on a new tool. Now, Igor has reached a state where I'm happy with showing it off and so it's time to introduce it to the world.

While Aqua neatly makes the initial setup for my Lambda functions easier, that still left me with the deployments. In order to deal with that, I therefore made a simple deployment step for Wercker. I'll first go over how to use it, before showing how it works.

In my ongoing quest for automating all deployment related matters, I discovered I needed a way to pull in single files from S3 for my Wercker builds. As I couldn't find a step for that, I built one.