Intermediate

Containers on ECS for Service Teams

Teams adopt containers quickly, then stall on logging and secrets. This course keeps the scope tight: ECS on Fargate, Application Load Balancer health checks, and structured logs shipped to a search tool you already use.

10 sessions (20 hours) · Cohort with code reviews · English

From ¥72,000 JPY

Request information

Cover visual for Containers on ECS for Service Teams

Included focus areas

  • Task definition templates with CPU/memory guardrails
  • Secrets Manager rotation walkthrough (read-only)
  • Canary-ish deploy pattern without extra vendor tools
  • Log routing lab with JSON field conventions
  • AutoScaling target tracking tuned for batch + web
  • Mentor office hours for compose-to-task translation
  • Cost note comparing Fargate vs EC2-backed (conceptual)

Artifacts you should exit with

  1. Ship a sample service with health-checked ALB
  2. Document log fields your support desk can search
  3. List rollback steps your on-call can execute

Mentor anchor

Shipping engineer; prefers boring deploy graphs over flashy demos.

Avatar for Noah Fischer
Noah Fischer

Primary reviewer for this track

Participant questions

This track is ECS-only. We publish a separate Kubernetes primer quarterly.

Experience notes

Canary-ish deploy section used plain ALB rules—finally something I can explain to PMs.