Command Palette

Search for a command to run...

Hectal
Phase 5Intermediate6 of 9 in AWS

Containers & Serverless

ECR and ECS on Fargate, EKS on AWS, Lambda, and API Gateway — the ways to run code on AWS without managing individual servers.

Phase 2 ran applications on EC2 instances you manage. This phase moves up a level: AWS runs the machines, you hand it a container image or a function. You'll see how ECS on Fargate runs containers with no nodes to patch, how EKS maps onto everything from the Kubernetes course, how Lambda's execution model shapes the code you write, and how API Gateway puts an HTTP front door on it — plus how to choose between them.

0/4 · 0%
4 topics ~53 min 12 code blocks & diagrams
Start with the first topic
1
5.1

ECR & ECS on Fargate

ECR stores your container images; ECS runs them as tasks described by a task definition and kept alive by a service — and with Fargate, AWS provides the compute for each task so there are no EC2 nodes to manage.

13 min 3 code practice

2
5.2

EKS on AWS & Choosing Your Compute

EKS is managed Kubernetes whose control plane AWS runs; its AWS-specific pieces are pod networking in your VPC, IAM for pods, and the load balancer controller — and the real decision is whether you need Kubernetes at all versus ECS or Lambda.

13 min 1 diagram 2 code practice

3
5.3

Lambda: The Execution Model

Lambda runs your function in response to events inside short-lived execution environments that are reused between invocations — understanding cold starts, concurrency, timeouts, and what survives between calls is what makes Lambda code correct and fast.

14 min 1 diagram 2 code practice

4
5.4

API Gateway & Serverless Patterns

API Gateway is a managed HTTP front door that handles routing, auth, throttling, and TLS in front of Lambda or other backends; combined with events and Step Functions it forms the backbone of serverless architectures.

13 min 1 diagram 2 code practice