ARCHIVED, NO LONGER IN DEVELOPMENT

I wrote this a long time ago as I was beginning to explore how to manage infrastructure-as-code environments, particularly on AWS. A lot has changed since then and I would do things a lot differently now. For that reason, this repo is archived. Thanks for your interest!

fabrik

Serverless orchestration of CI/CD pipelines in an infrastructure-as-code context.

Configure

Add a profile to ~/.aws/credentials that will serve as your fabrik deployment identity in AWS. This should be a set of access credentials that have administrator privileges.

[fabrik]
aws_access_key_id = AKIA...
aws_secret_access_key = O4vew...
region = us-west-2
output = json

Install

Build the development Docker image

$ make image

Install the aws CLI utility

Build

Fetch dependencies

$ make deps

Build each Lambda function

$ make build

Deploy

Deploy/Update the entire stack defined in serverless.yml

$ make deploy

SSM Parameters

We utilize AWS SSM for secure parameter storage. Values are encrypted at rest using a KMS key.

Set a parameter like so,

$ aws --profile opolis ssm put-parameter \
    --type SecureString \
    --name {name} \
    --value $(cat {file}) \
    --key-id 344d9fba-07d2-45c8-9bde-2356aaedc6c3

The secret value should first be written to a temporary file to avoid storing the value in shell history.

The following keys are deployed in production:

Key	Description
fabrik.github.hmac	GitHub OAuth token with repo scope
fabrik.github.token	GitHub HMAC key used in webhook configuration

Adding a Repository

See example/