Amazon Fargate

Neil Haddley • September 20, 2021

Pay-as-you-go

AWS DevOpsfargateserverless-containersecs

I used AWS Fargate, a serverless pay-as-you-go compute engine, to run containers on Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS).

I used Amazon Elastic Kubernetes Service (Amazon EKS) to deploy, manage, and scale containerized applications using Kubernetes on AWS.

Amazon also offers Amazon Elastic Container Service (Amazon ECS) and Amazon Fargate.

Since Amazon EKS is based on the open-source tool Kubernetes, all applications managed by Amazon EKS are fully compatible with applications managed by any standard Kubernetes environment.

Tap the image to open it full size

I logged in to aws.amazon.com

Tap the image to open it full size

I navigated to the AWS Management Console

Docker desktop

To demonstrate that I could use the same kubectl client to deploy containers to a laptop or the AWS cloud, I used this Docker Desktop example.

Tap the image to open it full size

No containers were running

Tap the image to open it full size

I ran kubectl apply -f ./blog.yaml

Tap the image to open it full size

The cluster was running

Tap the image to open it full size

I accessed the Docker Desktop cluster

aws cli

I used the aws command line tool to manage the Amazon Web Services cloud.

Tap the image to open it full size

I created a new AWS access key

Tap the image to open it full size

The access key was created

aws configure

I used aws configure to set credentials.

BASH
1% aws configure

AWS Access Key ID [None]: AKIAYLZDACM7MNDENQV4

AWS Secret Access Key [None]: iBXYnPPUTp+enyaVU2xvXXXXXXXXXXXXXXXXXXXX

Default region name [None]:

Default output format [None]:

eksctl

I used eksctl, a simple CLI tool for creating clusters on EKS — Amazon's managed Kubernetes service for EC2.

https://github.com/weaveworks/eksctl

Tap the image to open it full size

I reviewed the eksctl documentation on the AWS site

Tap the image to open it full size

I found the eksctl project on GitHub

Tap the image to open it full size

I installed eksctl

Tap the image to open it full size

No clusters were running

eksctl create cluster

BASH

1% eksctl create cluster \
2  --name blog-cluster \
3  --node-type t2.nano \
4  --nodes 2

Tap the image to open it full size

I used eksctl to create a cluster (node type t2.nano)

Tap the image to open it full size

The blog-cluster was being created

Tap the image to open it full size

The blog-cluster was active

Tap the image to open it full size

The blog-cluster EC2 nodes were created

Tap the image to open it full size

The eksctl command finished

kubectl apply

Tap the image to open it full size

I used kubectl apply to deploy containers

eksctl delete cluster

I used eksctl delete to remove the cluster.

BASH

1% eksctl delete cluster \
2  --name blog-cluster

Tap the image to open it full size

I ran eksctl delete cluster

Tap the image to open it full size

The cluster was deleted

Deleting an AWS Access Key

Publishing AWS access keys is not a great idea, so I deleted mine.

Tap the image to open it full size

I selected the Delete link

Tap the image to open it full size

I clicked the Deactivate button

Tap the image to open it full size

I confirmed the access key name and clicked Delete

Tap the image to open it full size

The access key was deleted