EKS vs ECS decision in AWS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS service used for managed Kubernetes.

AWS

service = "[1]"

Drag options to blanks, or click blank then click option'

AEKS

BECS

CLambda

DFargate

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing ECS which is for container orchestration but not Kubernetes.

EKS is the AWS managed Kubernetes service.

2fill in blank

medium

Complete the code to specify the AWS service that manages containers without Kubernetes.

AWS

service = "[1]"

Drag options to blanks, or click blank then click option'

ACloudFormation

BEC2

CECS

DEKS

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing ECS with EKS or EC2.

ECS is AWS's container orchestration service without Kubernetes.

3fill in blank

hard

Fix the error in the statement about the control plane management service.

AWS

control_plane = "[1]"

Drag options to blanks, or click blank then click option'

ALambda manages the Kubernetes control plane

BEC2 manages the Kubernetes control plane

CECS manages the Kubernetes control plane

DEKS manages the Kubernetes control plane

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking ECS or EC2 manages Kubernetes control plane.

EKS manages the Kubernetes control plane for you.

4fill in blank

hard

Fill both blanks to describe the compute options for ECS and EKS.

AWS

ECS can run on [1] or [2] compute options.

Drag options to blanks, or click blank then click option'

AEC2

BLambda

CFargate

DS3

Attempts:

3 left

💡 Hint

Common Mistakes

Including Lambda or S3 which are not ECS compute options.

ECS supports EC2 instances and Fargate serverless compute.

5fill in blank

hard

Fill all three blanks to describe the orchestration and management differences.

AWS

EKS uses [1] for orchestration, [2] manages the control plane, and [3] supports serverless compute.

Drag options to blanks, or click blank then click option'

AKubernetes

BAWS

CFargate

DDocker Swarm

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Docker Swarm with Kubernetes or misattributing control plane management.

EKS uses Kubernetes for orchestration, AWS manages the control plane, and Fargate supports serverless compute.

Practice

1. Which AWS service is best if you want to use Kubernetes features and have more control over container orchestration?

easy

A. Amazon S3

B. Amazon ECS

C. AWS Lambda

D. Amazon EKS

Solution

1. Step 1: Understand Kubernetes and AWS services

   Kubernetes is a popular container orchestration system. Amazon EKS is AWS's managed Kubernetes service.

2. Step 2: Match service to requirement

   Since the question asks for Kubernetes features and control, Amazon EKS fits best.

3. Final Answer:

   Amazon EKS -> Option D

4. Quick Check:

   Kubernetes features = Amazon EKS [OK]

Hint: EKS = Kubernetes control; ECS = simpler AWS container [OK]

Common Mistakes:

• Confusing ECS as Kubernetes service
• Choosing Lambda or S3 which are unrelated
• Thinking ECS offers full Kubernetes features

2. Which of the following is the correct way to describe Amazon ECS?

easy

A. A managed Kubernetes service

B. An object storage service

C. A simple AWS-native container orchestration service

D. A serverless function service

Solution

1. Step 1: Identify ECS service type

   Amazon ECS is AWS's own container orchestration service, simpler than Kubernetes.

2. Step 2: Match description

   It is AWS-native and simpler, not Kubernetes or serverless or storage.

3. Final Answer:

   A simple AWS-native container orchestration service -> Option C

4. Quick Check:

   ECS = simple AWS container service [OK]

Hint: ECS = simple AWS container service, not Kubernetes [OK]

Common Mistakes:

• Calling ECS a Kubernetes service
• Confusing ECS with Lambda or S3
• Mixing up service types

3. You have a team with no Kubernetes experience and want to deploy containers quickly using AWS services. Which service will likely result in faster setup and simpler management?

medium

A. Amazon ECS

B. Amazon EC2 without containers

C. Amazon EKS

D. AWS Elastic Beanstalk

Solution

1. Step 1: Consider team skills and service complexity

   Without Kubernetes experience, simpler AWS-native services are easier to manage.

2. Step 2: Compare ECS and EKS for ease

   ECS is simpler and faster to set up than EKS, which requires Kubernetes knowledge.

3. Final Answer:

   Amazon ECS -> Option A

4. Quick Check:

   No Kubernetes skill = ECS faster setup [OK]

Hint: No Kubernetes skill? Choose ECS for simplicity [OK]

Common Mistakes:

• Choosing EKS despite no Kubernetes experience
• Confusing Elastic Beanstalk with container orchestration
• Ignoring team skill impact

4. A developer tries to deploy a containerized app using Amazon EKS but faces complex setup issues. What is a likely cause?

medium

A. EKS requires Kubernetes knowledge and setup complexity

B. ECS does not support containers

C. EKS does not allow container orchestration

D. ECS is only for serverless functions

Solution

1. Step 1: Understand EKS complexity

   EKS is a managed Kubernetes service, which needs Kubernetes knowledge and setup steps.

2. Step 2: Identify cause of deployment issues

   Complex setup issues usually come from Kubernetes learning curve and configuration.

3. Final Answer:

   EKS requires Kubernetes knowledge and setup complexity -> Option A

4. Quick Check:

   EKS complexity = Kubernetes knowledge needed [OK]

Hint: EKS needs Kubernetes skills; complexity causes issues [OK]

Common Mistakes:

• Thinking ECS can't run containers
• Believing EKS disallows orchestration
• Confusing ECS with serverless only

5. Your project requires running containers with advanced Kubernetes features like custom scheduling and network policies, but your team has limited Kubernetes experience. What is the best approach?

hard

A. Use Amazon ECS for simplicity and skip advanced Kubernetes features

B. Use Amazon EKS and invest in Kubernetes training for your team

C. Use AWS Lambda to run containers without orchestration

D. Use Amazon EC2 instances manually without container orchestration

Solution

1. Step 1: Identify feature needs

   Advanced Kubernetes features require Kubernetes orchestration, which only EKS provides.

2. Step 2: Consider team skills and project needs

   Since the team lacks Kubernetes experience, investing in training is needed to use EKS effectively.

3. Step 3: Evaluate alternatives

   ECS is simpler but lacks advanced Kubernetes features; Lambda and EC2 do not provide needed orchestration.

4. Final Answer:

   Use Amazon EKS and invest in Kubernetes training for your team -> Option B

5. Quick Check:

   Advanced Kubernetes features = EKS + training [OK]

Hint: Advanced Kubernetes needs EKS plus team training [OK]

Common Mistakes:

• Choosing ECS despite missing features
• Using Lambda or EC2 without orchestration
• Ignoring team skill development