DEV Community

Cover image for Building and Deploying a Minimal API on AWS ECS/Fargate using Terraform
AWS Community Builders profile image Oluwasegun Adedigba
Oluwasegun Adedigba for AWS Community Builders

Posted on

Building and Deploying a Minimal API on AWS ECS/Fargate using Terraform

#terraform #aws #api #docker

Introduction:

The aim of this blog post is to show in detail the process of creating a minimal API with two endpoints and deploying it on AWS ECS/Fargate using Terraform. The endpoint API codes are written in Python.

These APIs provide two simple functionalities which are listed below:

1. Timestamp API: This is responsible for retrieving the current Unix timestamp.

2. Random Numbers API: This is responsible for generating a list of 10 random numbers in the range of 0 to 5.

The aim of this article is to walk the reader through the process of creating a working API running in a Docker container on AWS ECS/Fargate which is accessible to the public.

Requirement:

To be able to do this on your device, make sure you have the following in place:

  1. AWS account with appropriate permissions to create ECS/Fargate resources. Visit here to get started.

  2. AWS CLI installed and configured on your local device. Visit here to install and configure AWS CLI on your device.

  3. Docker installed on your local machine. Visit here to install Docker on your device.

  4. Terraform installed on your local machine. Visit here to install Terraform on your device.

Procedure:

Creating the Minimal APIs

The first step is creating the python APIs for the two endpoints 'time' and 'random'. The Flask framework is used to create the endpoints. The code snippets below are used to create the endpoints:

Time Endpoint: 



# app.py
from flask import Flask
import time

app = Flask(__name__)

@app.route('/time')
def get_current_time():
    timestamp = str(int(time.time()))
    response = {
        "data": {"unix_timestamp": timestamp},
        "message": "success"
    }
    return response
Enter fullscreen mode Exit fullscreen mode

Random Numbers Endpoint: 



# app.py
from flask import Flask
import random

app = Flask(__name__)

@app.route('/random')
def get_random_numbers():
    numbers = [random.randint(0, 5) for _ in range(10)]
    response = {
        "data": {"random_number": numbers},
        "message": "success"
    }
    return response


if __name__ == '__main__':
    app.run(host='0.0.0.0', port=5000)
Enter fullscreen mode Exit fullscreen mode

Creating the Dockerfile

Next, a Dockerfile that includes the Python APIs and specifies the necessary configurations is created using the Dockerfile snippet shown below:



FROM python:3.10-alpine3.18

# WORKDIR /app

COPY . .

RUN pip install -r requirements.txt

EXPOSE 5000

ENV PYTHONUNBUFFERED=1

CMD ["python" ,"app.py"]
Enter fullscreen mode Exit fullscreen mode

What this Dockerfile does is that it sets up the container environment using Python 3.10-alpine3.18 as the base container image. This base image keeps the container size at a minimal level due to it being lightweight.

The 'COPY' line copies everything from the working directory into the working directory of the Docker image.

The 'RUN' command installs the dependencies of the application which are listed in the requirements file.

The 'EXPOSE' command lets the container listen on port 5000.

The 'CMD' line runs the app.py file when the container is up and running.

Building and Pushing the Docker Image

After writing the codes for the APIs and the Dockerfile commands, the Docker image is built and pushed to a public container registry. In this case, Amazon Elastic Container Registry Amazon ECR is used.

First, create your own repository on Amazon ECR. Select your own preferred configurations and give you repository a preferred name.

Create ECR Repository

Then, build the Docker image using the AWS CLI commands below: 



# Get authentication token and authenticate Docker client to the registry

aws ecr get-login-password --region <your-region> | docker login --username AWS --password-stdin <your-account-id>.dkr.ecr.<your-region>.amazonaws.com
Enter fullscreen mode Exit fullscreen mode 


#Build the image

docker build -t <your-repo-name>:<tag> .
Enter fullscreen mode Exit fullscreen mode

After building the image, tag the image with a preferred tag with which it will be pushed into the repository



# Tag the Image 

docker tag <your-repo-name>:<tag> <your-account-id>.dkr.ecr.<your-region>.amazonaws.com/<your-repo-name>:<tag>
Enter fullscreen mode Exit fullscreen mode

After the image has been correctly tagged, the command below pushes the image into the repository



# Push the Docker image to Docker Hub

docker push <your-account-id>.dkr.ecr.<your-region>.amazonaws.com/<your-repo-name>:<tag>
Enter fullscreen mode Exit fullscreen mode

Alternatively, the commands to build and push the Docker image to a repository on Amazon ECR can be found by clicking the "View push commands" button in the repository page.

View Push Commands

Creating the Terraform script for Deployment

After the image has been uploaded to the created ECR repository, the terraform script which will be used to deploy the container on Amazon Elastic Container service Amazon ECS is then created.

Firstly, configure the necessary AWS credentials using the AWS CLI command below. Use the AWS Access Key ID and Secret Access Key, set the default region and the preferred output format. 



aws configure
Enter fullscreen mode Exit fullscreen mode

After configuring the AWS credentials, create a file named 'main.tf' and paste the code snippet below:



# Provider definition
provider "aws" {
  region = "us-east-1"
}

# VPC definition
data "aws_vpc" "existing" {
  id = "vpc-XXXXXXXXXXXXXXXXX"  # Replace "vpc-XXXXXXXXXXXXXXXXX" with your VPC ID
}

# Security group for the ECS tasks
resource "aws_security_group" "ecs_sg" {
  vpc_id = data.aws_vpc.existing.id
  name   = "ecs-security-group"
  # Inbound and outbound rules
  ingress {
    from_port   = 5000
    to_port     = 5000
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }
  egress {
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["0.0.0.0/0"]
  }
}

# ECS task definition
resource "aws_ecs_task_definition" "task_definition" {
  family                = "miniflask-api-task"
  network_mode          = "awsvpc"
  memory                = "512"
  requires_compatibilities = ["FARGATE"]

  # Task execution role (Replace "XXX" with your IAM role ARN)
  execution_role_arn    = "arn:aws:iam::XXX:role/ecr_task_role"  # Replace "XXX" with your IAM role ARN

  # Container definition
  container_definitions = jsonencode([
    {
      name      = "miniflask-api-container"
      image     = "public.ecr.aws/g1s5q2a7/miniflask-api:latest" 
      cpu       = 256
      memory    = 512
      port_mappings = [
        {
          container_port = 5000
          host_port      = 5000
          protocol       = "tcp"
        }
      ]
    }
  ])

  # Defining the task-level CPU
  cpu = "256"  
}

# ECS service
resource "aws_ecs_cluster" "ecs_cluster" {
  name = "minimal-api-cluster"  
}

resource "aws_ecs_service" "service" {
  name            = "miniflask-api-service"
  cluster         = aws_ecs_cluster.ecs_cluster.id
  task_definition = aws_ecs_task_definition.task_definition.arn
  desired_count   = 1
  launch_type     = "FARGATE"

  # Network configuration
  network_configuration {
    subnets          = ["subnet-XXX", "subnet-XXX", "subnet-XXX", "subnet-XXX", "subnet-XXX", "subnet-XXX"]  # Replace "subnet-XXX" with your subnet IDs
    security_groups  = [aws_security_group.ecs_sg.id]
    assign_public_ip = true
  }
}
Enter fullscreen mode Exit fullscreen mode

Deploying the APIs

After the terraform script has been written with the appropriate values of the variables in the main.tf file, the APIs are deployed to AWS ECS/Fargate using Terraform with the following terraform commands: 



# Initialize Terraform in the project directory
terraform init

# Preview the resources that will be created
terraform plan

# Deploy the resources to AWS
terraform apply
Enter fullscreen mode Exit fullscreen mode

Accessing the APIs

Once the terraform apply command is complete and successful, you should see an output message which shows the number of resources added, changed and destroyed.

The public IP address of the API endpoint can then be gotten from the Amazon ECS page in the AWS management console or by using the following AWS CLI command in the terminal:



aws ecs describe-tasks --cluster YOUR_CLUSTER_NAME --tasks YOUR_TASK_ID --query 'tasks[0].attachments[0].details[?name==`networkInterfaceId`].value'
Enter fullscreen mode Exit fullscreen mode

After the public IP address is gotten, the endpoints can be accessed by using a browser or using the terminal.

If a browser is used, the two endpoints can be accessed by using the public IP address as shown below:

  1. Current Unix timestamp:


http://x.x.x.x:5000/time
Enter fullscreen mode Exit fullscreen mode

Unix Timestamp

  1. List of 10 random numbers (0 < X < 5):


http://x.x.x.x:5000/random
Enter fullscreen mode Exit fullscreen mode

Random Numbers

If a terminal is used, the two endpoints can be accessed by using the public IP address as shown below:

  1. Current Unix timestamp:


curl http://x.x.x.x:5000/time
Enter fullscreen mode Exit fullscreen mode
  1. List of 10 random numbers (range: 0 to 5):



curl http://x.x.x.x:5000/random
Enter fullscreen mode Exit fullscreen mode




Conclusion

After following this procedure, a minimal API built using Flask, containerized with Docker, deployed on AWS ECS with a Fargate configuration using Terraform would have been achieved. The knowledge gotten from this can be built upon to develop more complex solutions on AWS.

Thank you for making it to this point. Comments and feedback are greatly appreciated. Happy coding!

Top comments (10)

Collapse
 
yogini16 profile image
yogini16 •

Great post !!
Minimal api is great concept for building fast HTTP APIs with ASP.NET Core.
Though this post indirectly talks about use case of minimal api. If you mention use cases of minimal apis, it will give more insights to readers.

Collapse
 
cloudsege profile image
Oluwasegun Adedigba •

Thanks for this. I will address this in another post. Thank you

Collapse
 
seuncaleb profile image
seuncaleb •

This is so helpful thanks for sharing

Collapse
 
cloudsege profile image
Oluwasegun Adedigba •

Thank you!

Collapse
 
cvanti profile image
Cristian V •

But you know that for an app like this, AppRunner or even Lambda would be much better options, and that configuration of ECS is not production-ready

Collapse
 
cloudsege profile image
Oluwasegun Adedigba •

Definitely. This was a problem I came across once, which is why I decided to write on it. Thank you

Collapse
 
zaheer profile image
Abdul-zahir Alao •

Great, thanks for sharing!

Collapse
 
cloudsege profile image
Oluwasegun Adedigba •

Thank you!

Collapse
 
eluedev profile image
Wisdom •

This is great! do one for Node.js next🥂

Collapse
 
cloudsege profile image
Oluwasegun Adedigba •

I'll look into that. Thank you!

Read next

arif_hossain profile image

Differentiating Docker stop vs Kill

Arif Hossain -

vortico profile image

Native Domain-Driven Design with Flama

Vortico -

takuma818t profile image

Lambda Performance Evaluation: The Relationship Between Memory and Internal vCPU Architecture, and Their Comparison

takuma818t -

ianbrumby profile image

Effortless Debugging: AWS CDK TypeScript Projects in VSCode

Ian -