Migrate to IaC and Serverless deployments

[m-triassi]

Description

Currently infrastructure for the site is not defined in any sort of specification. It runs on AWS and is managed by an external service, Laravel Forge.

This means that the application is provisioned on a fixed size EC2 instance, resulting on a constant bill based off the instance size. Due to the low traffic nature of the application it would more cost effective to use serverless technologies (Lambda + Aurora) to host the site. This would roughly half the cost, assuming consistent, low traffic.

Possible Implementation

Use Bref to run the application code on a lambda function.

(Ideally) Write a Cloud Formation specification that matches this blog post, in some way. With the Bref config syntax, it should be possible to define this as a resource in the config file allowing it to spin up with the rest of the application stack.

• In the event that a CloudFormation Specification is unavailable / unworkable, spin up the instance by hand 🤮...

Connecting a Bref configured serverless application is detailed here in the documentation

Add an S3 bucket to the resources as well to store public assets (such as character art for future features).

Out of scope

N/a

Requirements / Restrictions

Bill should be lower than current costs shown in the AWS billing console, or as low as possible according to AWS Pricing Calculator.