What is the difference between ECS vs eks vs fargate?

In the context of AWS, here are the differences given:-

Amazon ECS

It is a fully managed container orchestration service that can provide high scalability and ease of management with other AWS services. It is very suitable for organizations that are already using AWS service extensively and looking for a managed solution with less complexity.

Import boto3

# Initialize ECS client
Ecs = boto3.client(‘ecs’)
# Create ECS task definition
Response = ecs.register_task_definition(
    Family=’my-task’,
    containerDefinitions=[
        {
            ‘name’: ‘my-container’,
            ‘image’: ‘my-image:latest’,
            ‘cpu’: 512,
            ‘memory’: 1024,
            ‘portMappings’: [
                {
                    ‘containerPort’: 80,
                    ‘hostPort’: 80
                },
            ],
        },
    ],
    networkMode=’bridge’
)
# Create ECS service
Response = ecs.create_service(
    Cluster=’my-cluster’,
    serviceName=’my-service’,
    taskDefinition=’my-task’,
    desiredCount=2,
    launchType=’EC2’
)
Amazon eks
It is used in providing management of the Kubernetes environment, offering flexibility, scalability, and control for organizations familiar with Kubernetes. It is very much suitable for the orchestration feature and Kubernetes ecosystem compatibility.
Import boto3
# Initialize EKS client
Eks = boto3.client(‘eks’)
# Create EKS cluster
Response = eks.create_cluster(
    Name=’my-cluster’,
    Version=’1.21’,
    roleArn=’arn:aws:iam::123456789012:role/eks-service-role’,
    resourcesVpcConfig={
        ‘subnetIds’: [
            ‘subnet-12345’,
            ‘subnet-67890’
        ],
        ‘securityGroupIds’: [
            ‘sg-12345’
        ],
        ‘endpointPublicAccess’: True,
        ‘endpointPrivateAccess’: True
    }
)
AWS fargate

It is a serverless container orchestration service that would allow you to run containers without managing the underlying infrastructure. It is very much suitable for organizations focusing on application development without worrying about server provisioning or scaling.

Import boto3
# Initialize ECS client for Fargate
Ecs = boto3.client(‘ecs’)
# Create ECS task definition for Fargate
Response = ecs.register_task_definition(
    Family=’my-task’,
    containerDefinitions=[
        {
            ‘name’: ‘my-container’,
            ‘image’: ‘my-image:latest’,
            ‘cpu’: 512,
            ‘memory’: 1024,
            ‘portMappings’: [
                {
                    ‘containerPort’: 80,
                    ‘hostPort’: 80
                },
            ],
        },
    ],
    networkMode=’awsvpc’,
    requiresCompatibilities=[‘FARGATE’],
    cpu=’512’,
    memory=’1024’
)
# Run ECS task on Fargate
Response = ecs.run_task(
    Cluster=’my-cluster’,
    taskDefinition=’my-task’,
    launchType=’FARGATE’,
    networkConfiguration={
        ‘awsvpcConfiguration’: {
            ‘subnets’: [
                ‘subnet-12345’,
                ‘subnet-67890’
            ],
            ‘securityGroups’: [
                ‘sg-12345’
            ],
            ‘assignPublicIp’: ‘ENABLED’
        }
    }
)