While one-click deployments to the cloud sound attractive, I wanted to explore the more traditional approach many companies use: deploying applications with EC2 + LB + ASG. This is also cost-effective, which is crucial for my open-source SaaS solution (<a href="https://github.com/zyghq/zyg" target="_blank" rel="noopener nofollow">https://github.com/zyghq/zyg</a>).
As it turns out, deploying applications the “old way” with Terraform and GitHub Actions isn’t difficult at all. In fact, it can provide even greater control over the process.
Check out my GoAWS repository and give it a try! (<a href="https://github.com/sanchitrk/goaws" target="_blank" rel="noopener nofollow">https://github.com/sanchitrk/goaws</a>)
Here’s the folder structure
<pre><code>.
├── README.md
├── appspec.yml
├── buildspec.yml
├── go.mod
├── goaws
├── infra
│   ├── alb
│   ├── asg
│   ├── backend
│   ├── kp
│   ├── main.tf
│   ├── s3
│   ├── terraform.tfstate
│   └── terraform.tfstate.backup
├── scripts
│   ├── after.sh
│   ├── before.sh
│   ├── srv.service
│   ├── start.sh
│   ├── stop.sh
│   └── validate.sh
└── server.go
</code></pre>
8 directories, 15 files
Starting with single ec2 setup to asg + alb setup, so you easily follow along.
PS: star if you like it ;)

Self-hosted refers to the practice of running your own applications and services on your own servers or devices, giving you full control over your data and how it is managed.

selfhosted

Explore a traditional method for deploying applications using EC2, Load Balancer, and Auto Scaling Group (ASG) on AWS. This approach, implemented through Terraform and GitHub Actions, provides greater control and cost-effectiveness for open-source SaaS solutions. The post includes a repository and a structured guide for setting up deployments.

Go + AWS - The Boring CI/CD setup using Terraform and GitHub actions.