Menu

Case study: ECS Fargate pipeline with Terraform and OIDC
📰

Case study: ECS Fargate pipeline with Terraform and OIDC

DEV Community: terraform·Muhammad Umar·about 15 hours ago
#kbuT6vWB
#devtoterraform#devto#dev#service#terraform
Reading 0:00
15s threshold

In short:

A fixed-price, five-day client project: a container app on AWS, deployed by a pipeline, with all the infrastructure as code.

Terraform builds the network, load balancer, registry, service and alarms. GitHub Actions deploys every merge to main with OIDC, so no AWS keys are stored.

Skipping the NAT gateway saves about $32 a month, and one command builds or removes the whole stack.

This was a fixed-price, five-day client project: a container app on AWS, deployed by a pipeline, with the infrastructure written as code. I am keeping the client private, and the repository is private too, so there is no link to it.

The diagram above is the handover map. This post explains what is in it and why.

What was built

A small Node.js API runs as a container on AWS ECS Fargate behind an application load balancer. Everything in AWS is created by Terraform, and every merge to main deploys through GitHub Actions.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.