Whats the deal with blogs and shit?

The main reason I wanted this blog is that running a normal website requires hosting a server, keeping it online, updating it and all the other jazz that I dont really care to manage

So how is this blog made?

  1. We use hugo to build the source and write all the articles in markdown format, which makes things so damn easy
  2. The source code is stored on github, and we leverage github actions to automatically post new changes to AWS
  3. We leverage AWS S3 and a CloudFront Distribution to handle the CDN and certificates

How do you get the automatic deployment working

Well github actions are pretty sweet and it allows us to run builds directly from github, which is a great feature. Heres the example of our yml file

name: Build and Deploy

on: push

    name: Build and Deploy
    runs-on: ubuntu-latest
      - uses: actions/checkout@v1
      - name: Install Hugo
        run: |
          wget https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/${HUGO_DOWNLOAD}
          tar xvzf ${HUGO_DOWNLOAD} hugo
          mv hugo $HOME/hugo
          HUGO_VERSION: 0.59.1
      - name: Hugo Build
        run: $HOME/hugo -v
      - name: Deploy to S3
        if: github.ref == 'refs/heads/master'
        run: $HOME/hugo -v deploy --maxDeletes -1
          AWS_ACCESS_KEY_ID: ${{ secrets.HUGO_S3_KEY }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.HUGO_S3_SECRET }}

Wait, how do I pass in the credentials securely

Well before we pass in any credentials, lets make sure we create an IAM user on your account that is only locked down to that bucket. This way, if these credentials get compromised, the scope will only be to that bucket and not your AWS account.

  1. Create an IAM User
  2. Create a IAM Policy that only allows access to that bucket
    "Version": "2012-10-17",
    "Statement": [
            "Action": [
            "Resource": [
            "Effect": "Allow"
            "Action": [
            "Resource": [
            "Effect": "Allow"
  1. Apply that policy to the user.
  2. Save the Access Key and Secret Key and copy them to your git settings https://github.com/getsec/YOURREPO/settings/secrets
  3. Add the keys and then reference them in your main.yml config file.
  4. Thats it


  1. GitHub Actions
  2. Hugo Getting Started
  3. Hugo + Github Actions + AWS S3 Deployment