While one-click deployments to the cloud sound attractive, I wanted to explore the more traditional approach used by many companies: deploying applications with EC2 + LB + ASG. This method offers cost-effectiveness, 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>)
PS: star if you like it ;)

A supportive squad for Go developers who want to dive deeper into what makes Go special. We focus on the language's clean simplicity, powerful concurrency, and reliable performance.

Go Developers

Exploring traditional deployment methods using EC2, Load Balancers, and Auto Scaling Groups for a cost-effective and controlled CI/CD setup with Terraform and GitHub Actions. Check out the GoAWS repository for implementation details.

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

Love this experiment but by LB and ASG I want to assume you mean Load Balancer and Security Groups? I think it would be useful to spell those out as someone not entirely familiar with that domain would not find the abbreviations helpful (especially since you use it in naming your files as well).
Perhaps updating the readme and this article with explanations to help those unfamiliar but would like to partake in this experiment as well.