terraform-aws-ecs-web-app
terraform-aws-ecs-alb-service-task
terraform-aws-ecs-web-app | terraform-aws-ecs-alb-service-task | |
---|---|---|
2 | 1 | |
222 | 136 | |
1.4% | 0.0% | |
5.4 | 5.8 | |
9 days ago | 9 days ago | |
HCL | HCL | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-aws-ecs-web-app
-
Ask HN: A Better Docker Compose?
I’ve been spending a week trying to learn how to deploy a collection of containers (my web app, a Postgres DB, and some microservices) to AWS and I am still so lost.
The first solution I happened upon was serverless. Specifically SST, which is written with AWS CDK, but you must develop on live services and I just can’t justify paying to develop.
Then I found Serverless Framework, which is an abstraction on CloudFormation, but the offline solutions like localstack get a lot of flack for being buggy and localstack charges for some services. I also looked into Architect but the documentation is abysmal.
Then I figured serverful might be the easier way to go. I found that docker compose has a built in integration with AWS ECS where it transforms your yaml into Cloudformation to provision the right services. However, it seems to just be missing key parts like custom domain and SSL certificate provisioning which seems to defeat the IaC ethos.
Then I figured I might go with Terraform and I found some seemingly good starters like https://github.com/aws-ia/terraform-aws-ecs-blueprints https://github.com/cloudposse/terraform-aws-ecs-web-app https://github.com/turnerlabs/terraform-ecs-fargate but the examples are just lacking. They don’t have any examples for multiple containers that can access each others’ resources that I can find. Reading these templates has at least given me a better idea of the resources I need to provision in AWS but the networking and configuration still frighten me. Like do I need to configure nginx with a reverse proxy myself? How do I orchestrate that container with the others? And apparently services can crash and just not restart? And I need to make sure to configure volumes for data that needs to persist. And setting up the CI/CD seems daunting.
I’ve also heard about docker swarm, kubernetes, pulumi, AWS SAM, etc but it’s a lot to learn. When I go on Discords for web frameworks, mostly everyone including the devs of these frameworks use 2nd tier managed providers like Vercel, Fly, Netlify, Supabase, Cloudflare, etc. But many of those are just not as reliable as core cloud providers and the cost is way higher. Glad to see I’m not alone in a very reasonable expectation of a simple way to orchestrate multiple containers on AWS, what must be the most common use case web developers have
-
Blitz.js – The Missing Fullstack Toolkit for Next.js
As an aside, this is the first time I've heard about Flightcontrol. Super impressed! The biggest con of something like Vercel is that you can't be on your own AWS VPC. An RDS instance with a public IP address (which Vercel's docs endorse) is a dealbreaker for me.
But... wouldn't a Terraform module accomplish something simmilar? Our own stack is something like Codepipeline + Fargate + ALB + Cloudwatch + Cloudfront and we basically just forked https://github.com/cloudposse/terraform-aws-ecs-web-app
terraform-aws-ecs-alb-service-task
-
My Infrastructure as Code Rosetta Stone - Deploying the same Django application on AWS ECS Fargate with CDK, Terraform and Pulumi
There is a consultancy called Cloud Posse which shares a lot of Terraform module repos with examples. Here is an example comparable to what I did. Good for them for making all of their repos open source, but I feel like the more robust and dynamic the modules get (and theirs are), the harder they are to read/digest. I can still learn from them but I don't think I would use them when the alternative is building your own solution for your own product.
What are some alternatives?
terraform-aws-alb - Terraform module to create AWS Application/Network Load Balancer (ALB/NLB) resources 🇺🇦
TypeScript-Handbook - Deprecated, please use the TypeScript-Website repo instead
ecs-fargate-deployment - Repository from exanubes.com for Deploying ECS Fargate Application
terraform-aws-sns-lambda-notify-slack - Terraform module to provision a lambda function that subscribes to SNS and notifies to Slack.
terraform-aws-django - Terraform modules for deploying Django applications on AWS using ECS Fargate
ecs-blueprints - Configure and deploy complete ECS solutions with Terraform or CDK
briancaffey
terraform-aws-cloudfront-s3-cdn - Terraform module to easily provision CloudFront CDN backed by an S3 origin
django-step-by-step - A Django + Vue reference project that focuses on developer tooling and CI/CD + IaC
dhall-lang - Maintainable configuration files
pulumi-aws-django - A Pulumi package for deploying Django applications to AWS using ECS Fargate and other managed services