Leveraging AWS Fargate for running cost-friendly containerized application
summary
Argues that AWS Fargate cuts total operating cost by removing node management and charging per vCPU/memory and ports (demoed with the AWS pricing calculator over a 6‑month estimate), shows a working pipeline: build Docker image, push to ECR, create EKS with Fargate via eksctl, deploy a Fastify Node.js API from ECR, install AWS Load Balancer Controller with Helm and expose via NLB/ALB using IP targets. Notes constraints: daemonsets unsupported, Fargate Spot is ECS‑only, profiles allow up to five selectors, cluster creation ~20–30 minutes.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:17Leveraging aws Fargate for Running Cost Friendly and Containerized Applications
- 7:33Is fargate Really Cost Friendly
- 9:11Estimating Runtime Costs
- 12:18Who Should Use Fargate
- 14:17How Does Fargates Work with the Eks
- 17:28Create a Fargate Profile
- 19:08Create the Eks Cluster
- 20:26Create a Profile
- 21:42Create a Deployment Resource
- 22:17Exposing the Application to the Internet
- 23:33Create the Load Balancer
related talks
35mKubernetes on AWS: Zero to hero
43mBringing EDA to the Containers World
40mServerless Compute at the Heart of Your EDA
24mLessons Learned Migrating an On-Prem App to AWS EKS w/ Fargate
44mServerless and containers are coming together: an AWS perspective
27mGrow Your Company with AWS Container Services
46mArchitecting for Success and Runway
18mAbby Fuller, AWS | DockerCon 2018