Task Statement 2.1: Design scalable and loosely coupled architectures.

📘AWS Certified Solutions Architect – (SAA-C03)

In modern cloud applications, organizations often run applications inside containers. Containers package the application code, runtime, system tools, and dependencies together so the application runs the same way everywhere.

However, when an application runs many containers across many servers, managing them manually becomes very difficult. This is where container orchestration is required.

Container orchestration automatically deploys, manages, scales, and maintains containers across a cluster of compute resources.

For the AWS Certified Solutions Architect – Associate (SAA-C03) exam, you must understand how AWS orchestrates containers using:

Amazon Elastic Container Service (Amazon ECS)
Amazon Elastic Kubernetes Service (Amazon EKS)

1. What Is Container Orchestration?

Container orchestration is the automated management of containerized applications.

It manages tasks such as:

Container deployment
Scheduling containers on servers
Load balancing
Automatic scaling
Health monitoring
Networking between containers
Service discovery
Automatic replacement of failed containers

Without orchestration, administrators would need to manually:

Start containers
Decide which server runs them
Restart failed containers
Scale containers during traffic spikes

Orchestration platforms automate all of this.

2. Why Container Orchestration Is Important

Modern applications may consist of dozens or hundreds of microservices, each running in containers.

Typical IT environments require:

High availability
Automatic scaling
Fault tolerance
Efficient resource usage
Continuous deployment

Container orchestration platforms solve these challenges by managing the entire lifecycle of containers.

Key benefits include:

Automated Deployment

Applications can automatically start containers when needed.

Automatic Scaling

The system increases or decreases containers depending on traffic.

High Availability

If a container fails, the orchestration system replaces it automatically.

Efficient Resource Usage

Containers are scheduled on servers that have available CPU and memory.

Service Discovery

Containers can automatically find and communicate with each other.

3. Container Orchestration in AWS

AWS provides two primary container orchestration services:

Service	Description
Amazon ECS	AWS-native container orchestration platform
Amazon EKS	Managed Kubernetes service

Both services can run containers using:

Docker containers

They also support two main compute options:

Amazon Elastic Compute Cloud (EC2)
AWS Fargate (serverless containers)

4. Amazon Elastic Container Service (Amazon ECS)

Amazon Elastic Container Service is AWS’s native container orchestration platform designed to run and manage containers.

It is tightly integrated with other AWS services and is simpler to use than Kubernetes.

Key Characteristics

Fully managed container orchestration
Deep integration with AWS services
Simple setup and configuration
Highly scalable
Supports EC2 and Fargate launch types

5. Core ECS Components

Understanding ECS architecture is important for the exam.

ECS Cluster

An ECS cluster is a group of compute resources where containers run.

Clusters can include:

EC2 instances
Fargate resources

Task Definition

A Task Definition is a blueprint describing how a container should run.

It includes:

Container image
CPU and memory requirements
Port mappings
Environment variables
Storage volumes
Networking configuration

Task

A Task is a running instance of a task definition.

Example in IT environment:

A web API container starts based on a defined task configuration.

Service

An ECS Service ensures a specified number of tasks are always running.

If a container fails, the service automatically launches a replacement.

Services also support:

Load balancing
Auto scaling
Rolling deployments

Container Agent

The ECS container agent runs on each EC2 instance and communicates with the ECS service to manage containers.

6. ECS Launch Types

ECS supports two ways to run containers.

1. EC2 Launch Type

Containers run on EC2 instances inside the ECS cluster.

Advantages:

Full control of instances
Custom networking
GPU workloads supported
More configuration flexibility

Responsibilities include:

Managing EC2 instances
OS patching
Capacity planning

2. Fargate Launch Type

With AWS Fargate, AWS manages the infrastructure for containers.

You only define:

CPU
Memory
Container image

AWS automatically provides the compute resources.

Advantages:

No server management
Automatic scaling
Simplified operations

This is called serverless containers.

7. ECS Networking

ECS integrates with:

Amazon Virtual Private Cloud (VPC)

Networking features include:

VPC networking
Security groups
Elastic Load Balancing integration

ECS tasks can use:

Application Load Balancer
Network Load Balancer

8. ECS Scaling

ECS supports automatic scaling of container tasks.

Scaling can be based on metrics such as:

CPU utilization
Memory usage
Custom CloudWatch metrics

Monitoring is handled through:

Amazon CloudWatch

When demand increases, ECS launches more tasks automatically.

9. Amazon Elastic Kubernetes Service (Amazon EKS)

Amazon Elastic Kubernetes Service is AWS’s managed Kubernetes platform.

Kubernetes is an industry-standard container orchestration system.

EKS allows organizations to run Kubernetes clusters without managing the Kubernetes control plane infrastructure.

10. What Is Kubernetes?

Kubernetes is an open-source container orchestration system originally developed by Google.

It automates:

Container deployment
Scaling
Networking
Self-healing
Rolling updates

Many organizations already use Kubernetes, so EKS allows them to run Kubernetes in AWS.

11. Key Components of Kubernetes (EKS)

Cluster

A Kubernetes cluster contains:

Control plane
Worker nodes

AWS manages the control plane in EKS.

Node

Nodes are servers that run containers.

They can be:

EC2 instances
Fargate

Pod

A Pod is the smallest deployable unit in Kubernetes.

It contains one or more containers that share:

Networking
Storage

Deployment

A Deployment manages pods and ensures the desired number are running.

Service

A Service exposes pods and provides stable networking.

It can integrate with AWS load balancers.

12. EKS Integration with AWS Services

EKS integrates with many AWS services, including:

AWS Identity and Access Management (IAM)
Amazon CloudWatch
Elastic Load Balancing
Amazon Elastic Container Registry (ECR)

This allows secure container management and monitoring.

13. ECS vs EKS (Exam Comparison)

Understanding differences between ECS and EKS is important for the exam.

Feature	ECS	EKS
Type	AWS native	Kubernetes-based
Complexity	Simpler	More complex
Control	AWS-managed platform	Full Kubernetes control
Ecosystem	AWS ecosystem	Kubernetes ecosystem
Learning curve	Low	Higher

When to choose ECS

Simple container deployments
AWS-focused architecture
Faster setup
Less operational overhead

When to choose EKS

Kubernetes-based workloads
Multi-cloud portability
Standard Kubernetes tooling required

14. Container Image Storage

Containers typically store images in a registry such as:

Amazon Elastic Container Registry (ECR)

ECR provides:

Secure container image storage
Integration with ECS and EKS
Image versioning
IAM authentication

15. High Availability in Container Orchestration

Container orchestration platforms support high availability through:

Multi-Availability Zone deployment

Containers can run across multiple:

AWS Availability Zones

This protects against infrastructure failure.

Self-Healing

If a container crashes:

ECS services restart tasks
Kubernetes deployments recreate pods

Load Balancing

Containers can be distributed across multiple instances using:

Elastic Load Balancing

16. Security in Container Orchestration

Security is managed through multiple AWS services.

IAM

Access to ECS or EKS resources is controlled using:

AWS Identity and Access Management

Network Isolation

Containers run inside:

VPC
Subnets
Security groups

Image Security

Container images stored in ECR can be scanned for vulnerabilities.

17. Monitoring and Logging

Container environments must be monitored.

Common monitoring services include:

Amazon CloudWatch
CloudWatch Logs
Container Insights

These tools provide metrics such as:

CPU usage
Memory usage
Network traffic
Container health

18. Typical Architecture with Container Orchestration

A common AWS container architecture includes:

Container images stored in ECR
ECS or EKS cluster running containers
Containers deployed across multiple Availability Zones
Load balancer distributing traffic
CloudWatch monitoring system health
Auto scaling adjusting container count

This architecture provides:

High scalability
High availability
Automated operations

19. Key Exam Tips (SAA-C03)

Important points frequently tested in the exam:

ECS is AWS-native container orchestration.
EKS provides managed Kubernetes.
Fargate allows serverless containers.
ECS tasks and services manage container lifecycle.
Kubernetes uses pods, deployments, and services.
ECR stores container images.
Auto scaling and load balancing ensure scalability and availability.

✅ Summary

Container orchestration automates the management of containerized applications at scale. AWS provides two main orchestration platforms: Amazon ECS, a simple AWS-native solution, and Amazon EKS, a managed Kubernetes platform. These services manage container deployment, scaling, networking, monitoring, and fault recovery, enabling highly scalable and loosely coupled cloud architectures.