The Dossier System is an AWS CloudFormation and AWS Lambda project that publishes Latex documents to Dropbox. The problem that this system solves is:

1. Neither Latex PDFs or intermediary files are commited to the source repository
2. The projects are built in a reproducable manner
3. The Latex PDFs are published to an easily accessible location

(2) is solved by using Docker and (3) is solved by using AWS Lambda to publish the artifacts from building the Latex documents to Dropbox.

The system, pictorially, looks like the following pipeline:

The S3DropboxLambda project is located on GitHub at S3DropboxLambda.

The DossierCloudFormationRuby project deploys the CloudFormation Stack for the Dossier System. This includes the pipelines for both the Latex documentation and S3DropboxLambda deployment. CloudFormation provides a programatic and reproducible approach to generating, connecting, and retiring AWS resources.

This project has only been tested with Ruby 2.x. Installation is achieved using bundle with the package's Gemfile:

bundle install

The CloudFormation project is run using Rake tasks. Use the following to print a list of tasks along with a description of each task: rake --tasks. Different commands require task arguments. The following table provides a description of each. The Name is the name of the argument, which is printed in rake --tasks.

The CloudFormation stack requires two stages to be deployed. The reason for this because there is a circular dependency between the trigger S3 bucket and the AWS Lambda function:

• The S3 bucket notification configuration requires the AWS Lambda Function ARN
• The AWS Lambda function requires the S3 bucket's ARN to grant the bucket permission to invoke it

The stages are deployed via (the third argument is the stage number):

# run on CLI
rake dossier:deploy_stage'[GITHUB_CONNECTION,PHONE_NUM,0]'
rake dossier:deploy_stage'[GITHUB_CONNECTION,PHONE_NUM,1]'