Containers
Separate images, processes, networking, persistent data and orchestration.
Learn containers from shared foundations
First distinguish images, executions, hosts and durable data. These foundations apply even if you do not use AWS.
After the foundations, choose the course for your platform. ECS and Kubernetes are alternatives; you need not study both in sequence.
Study ECS and Fargate
Identify the artifact → manage ECS executions → understand Fargate responsibilities → choose CPU/memory → read health → plan updates and rollback.
- 1 Container images and ECR: tags, digests and choosing what runs →
- 2 Amazon ECS basics: task definitions, tasks and services explained →
- 3 AWS Fargate explained: ECS, responsibilities and launch requirements →
- 4 Fargate CPU and memory: units, valid combinations and sizing decisions →
- 5 ECS health checks explained: task health, ALB targets and startup failures →
- 6 ECS rolling deployments: task-count limits and rollback conditions →
Study Kubernetes and EKS
Follow nodes/Pods and responsibilities → destinations and traffic restrictions → support deadlines, upgrades and recovery. Prior ECS study is optional.
- 1 Amazon EKS explained: Kubernetes nodes, Pods and management responsibilities →
- 2 Kubernetes networking explained: Services, Ingress and NetworkPolicy →
- 3 EKS upgrades and recovery: support deadlines, nodes and workloads →
✓ 10 lessons are available.
Plan your study
Use this suggested order to move from foundations to related topics. Availability is shown for each topic.
01Review the foundations
02Follow these topics
03Continue with related subjects
Questions to guide your study
- Define its role: inputs, outputs and responsibility boundaries.
- Trace dependencies: required network, operating system, access and data conditions.
- Include operations: observable state, change impact and recovery procedures.
Topics in this subject
Available lessons and tools
Containers for beginners: images, runtime, hosts and persistent data
A container runs application processes in a separated environment. An image packages the files used for that execution; it is not itself a running application. Use two API containers made from one image to understand Linux hosts, networking and data lifetimes.
Container images and ECR: tags, digests and choosing what runs
A tag names a reference; a digest identifies content. ECR stores and distributes images, while services such as ECS execute them. Learn to identify the intended artifact without assuming a repeated tag means identical content or zero scan findings prove safety.
Amazon ECS basics: task definitions, tasks and services explained
A task definition describes what to run, a task is an execution, and a service maintains a desired number of tasks. Amazon Elastic Container Service (ECS) manages containerized applications. Follow a fictional two-task report API to distinguish registration, execution and updates.
AWS Fargate explained: ECS, responsibilities and launch requirements
Fargate lets AWS provision and maintain the server infrastructure running your containers. With ECS, distinguish management of what and how many tasks to run from the Fargate compute option. Less host management does not remove application, IAM, networking or data responsibilities.
Fargate CPU and memory: units, valid combinations and sizing decisions
Fargate does not accept arbitrary CPU and memory combinations. First align units, supported pairs, OS and platform-version conditions. Then separate a supported configuration from evidence that it provides enough application performance.
ECS health checks explained: task health, ALB targets and startup failures
RUNNING describes execution; HEALTHY reports a configured check. Neither alone proves a successful user operation. ECS container checks also differ from ALB checks. Use fixed report-API examples to identify what each observation establishes and which evidence to inspect next.
ECS rolling deployments: task-count limits and rollback conditions
Convert deployment percentages into task counts. A numerical slot does not guarantee that a new task can start and become healthy. Use fixed examples with desired counts of three and four to understand rounding, health checks and the limits of rollback.
Amazon EKS explained: Kubernetes nodes, Pods and management responsibilities
EKS is an AWS service for using Kubernetes. A Pod is an application deployment unit, a node provides compute for Pods, and the control plane coordinates placement and state. Choosing EKS still leaves application configuration, data and required permissions to decide. Read one report API through separate views of structure and responsibility.
Kubernetes networking explained: Services, Ingress and NetworkPolicy
A Service groups application destinations, an Ingress declares HTTP routing, and NetworkPolicy restricts Pod traffic. Creating any one object does not complete connectivity. Read destinations, implementation and permissions through a fictional report API on EKS.
EKS upgrades and recovery: support deadlines, nodes and workloads
An EKS control-plane upgrade does not establish that nodes, add-ons and applications all upgraded together. Identify each change, then align support deadlines, compatibility, availability during the change and recovery conditions. An update status alone does not prove successful user operations.