INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

COMPARISONTopic: container operating models

ECS vs EKS: how to choose and what you manage

ECS and EKS manage the placement and execution of containerized applications. ECS uses AWS task and service concepts; EKS uses Kubernetes. Compare required APIs, existing operating knowledge, compute options and the work your team retains. Follow three cases where the same report API leads to different selection reasons.

What you will learn

Separate ECS/EKS from compute choices, then explain a requirement-based selection, the work to learn and conditions still unverified.

Prerequisite

An API is an interface through which applications or tools request functionality. A container image packages application files and runtime requirements; Kubernetes manages placement, replication and updates. These fictional reading examples require no AWS account or Docker execution.

Separate orchestration from compute

ECS stands for Amazon Elastic Container Service; EKS stands for Amazon Elastic Kubernetes Service. Distinguish Kubernetes from EKS, the AWS service used to operate it.

Orchestration coordinates application placement, count and updates. Choosing ECS or EKS does not uniquely determine the compute beneath it. Infrastructure choices change management duties for both services.

Selection map: lines show questions to consider, not network traffic or configuration compatibility
Selection map: lines show questions to consider, not network traffic or configuration compatibility1: Report API requirements — Reasons to use AWS execution management — ECS orchestration. 2: Report API requirements — Reasons to use Kubernetes — Kubernetes on EKS. 3: ECS orchestration — Check support and management — Compute for ECS. 4: Kubernetes on EKS — Check support and management — Compute for EKS. 5: Compute for ECS — Identify retained work — Work retained by your team. 6: Compute for EKS — Identify retained work — Work retained by your team123456Report APIrequirementsECS orchestrationKubernetes on EKSCompute for ECSCompute for EKSWork retained byyour teamSelection map: lines show questions to consider, not network traffic or configuration compatibility1: Report API requirements — Reasons to use AWS execution management — ECS orchestration. 2: Report API requirements — Reasons to use Kubernetes — Kubernetes on EKS. 3: ECS orchestration — Check support and management — Compute for ECS. 4: Kubernetes on EKS — Check support and management — Compute for EKS. 5: Compute for ECS — Identify retained work — Work retained by your team. 6: Compute for EKS — Identify retained work — Work retained by your team123456Report APIrequirementsECSorchestrationKubernetes onEKSCompute for ECSCompute for EKSWork retainedby your team
  1. Report API requirements → ECS orchestrationReasons to use AWS execution management
  2. Report API requirements → Kubernetes on EKSReasons to use Kubernetes
  3. ECS orchestration → Compute for ECSCheck support and management
  4. Kubernetes on EKS → Compute for EKSCheck support and management
  5. Compute for ECS → Work retained by your teamIdentify retained work
  6. Compute for EKS → Work retained by your teamIdentify retained work
Report API requirements
Check required APIs, operating assets and constraints
ECS orchestration
Task definitions, tasks and services
Kubernetes on EKS
APIs and operations for Pods, Deployments and more
Compute for ECS
Fargate, customer-managed EC2 or Managed Instances
Compute for EKS
Auto Mode, node groups, eligible Fargate Pods and more
Work retained by your team
Application, access, networking, data and verification

Compare the operating model and retained work

The same container does not imply the same configuration or operations
QuestionECSEKS
Execution configurationTask definitions, tasks, services and related ECS concepts.Kubernetes APIs for Pods, Deployments and related objects.
Infrastructure managementDepends on Fargate, customer-managed EC2, Managed Instances or another supported approach.Depends on Auto Mode, node groups, Fargate or another supported approach.
Retained checksImages, application access, networking, data and behavior.Workloads, access, networking, data and behavior.
Existing assetsAWS integrations and ECS-specific configuration.Kubernetes APIs and compatible operating tools or extensions.

Reusing an image differs from reusing deployment configuration, permissions or exposure. A Kubernetes Operator extends application management through Kubernetes APIs and custom resources. The same image does not establish that an Operator will work unchanged on ECS.

Compare what your team needs to learn

Avoid rules such as “every small team must use ECS” or “EKS solves every future need.” Separate existing knowledge from new operating duties. Kubernetes experience and actual requirements change the learning work involved.

Record owners and verification methods instead of invented learning scores
Work to learnExamples with ECSExamples with EKS
Placement and updatesDefinition revisions, service references, actual tasks and update results.Pod templates, Deployments, actual Pods and update results.
AccessSeparate human operations from application task roles and related permissions.Separate Kubernetes API access from workload access to AWS.
Infrastructure and maintenanceAssign update, capacity and failure duties for the chosen compute.Assign node, add-on and compatibility checks for the chosen approach.

The same report API can lead to different choices

The fictional workload is a containerized HTTP report API using external storage. Its application behavior stays the same, while the requirements below change. A candidate in these cases is not approval for production deployment.

Requirement → candidate rationale → further checks
Given requirementsCandidate and rationaleStill to verify
A: AWS-focused; the team already operates ECS; no Kubernetes API or Operator requirement.Start the comparison with ECS: reuse existing knowledge without adding an unneeded Kubernetes operating model.Compute support, access, networking, storage, updates, incident response and cost.
B: The same API must also use an existing Kubernetes Operator and custom resources.Among these two services, EKS has a requirement-based reason for consideration.Operator versions, permissions, compute constraints and actual behavior.
C: Only “two containers run in Docker” is known; operating requirements are uncollected.Defer selection. Container count alone does not determine the operating model.Required APIs, operating assets, supported features, owners, data, connectivity and cost conditions.

Align cost assumptions and unknowns

Service names alone do not establish lower cost. ECS Managed Instances adds management charges to EC2 charges. For EKS, distinguish cluster, selected capabilities and compute charges; Auto Mode charges alone are not the whole bill. Align requirements, Region, resources, duration and surrounding storage, networking and logs before consulting pricing.

  1. Record required APIs and operating assets to retain.
  2. Record service and compute choices separately.
  3. List retained work, owners and learning needs.
  4. Record support constraints, cost assumptions, unknowns and reasons to revisit the decision.

Choose a reason that fits the assumptions

Choose an option to see the result and explanation.

Case A: the team already operates ECS and has no Kubernetes-specific requirement. Why start with ECS?
Read the answer and reason

Answer: Reuse existing knowledge without adding an unneeded operating model · This fits the assumptions; it does not establish supported compute or acceptable cost.

Case B requires a Kubernetes Operator and custom resources. How should these two candidates be compared?
Read the answer and reason

Answer: Consider EKS and separately verify Operator support and behavior · The Kubernetes API requirement supplies the rationale; choosing EKS does not prove every Operator compatible.

Case C only establishes that two containers run in Docker. What is appropriate next?
Read the answer and reason

Answer: Defer selection and collect API, operations, compute and data requirements · Keep unknowns explicit and gather the evidence needed for a choice.

After choosing EKS Auto Mode or managed ECS compute, what work remains?
Read the answer and reason

Answer: Application, access, networking, data, approach conditions and verification · Broader managed scope does not remove configuration or outcome verification.

Check, then explain in your own words

  1. Separate orchestration from compute.
  2. Compare existing knowledge with future operating duties.
  3. Explain each case from its requirements and retain unknowns.
Check your understanding: What should accompany an ECS/EKS selection rationale?

Record required APIs, existing operating assets, compute choice, team duties and learning needs, plus unknown conditions.

Service names and container counts do not determine responsibility, compatibility or cost. Record assumptions so a changed requirement can trigger a review.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.