Machine Learning

AWS: Deploying a FastAPI App on EC2 in Minutes

April 25, 2025
roosho

AWS is a well-liked cloud supplier that permits the deployment and scaling of enormous purposes. Mastering a minimum of one cloud platform is a necessary ability for software program engineers and information scientists. Operating an software domestically is just not sufficient to make it usable in manufacturing — it have to be deployed on a server to turn into accessible to finish customers.

On this tutorial, we’ll stroll by an instance of deploying a FastAPI software. Whereas the instance focuses on core EC2 networking ideas, the ideas are broadly relevant to different varieties of purposes as effectively.

Please be aware that this tutorial doesn’t cowl finest practices for AWS utilization. As a substitute, the aim is to offer readers a hands-on introduction to software deployment utilizing EC2 cases.

# 01. Occasion creation

Navigate to the Ec2 dashboard within the AWS service menu and select to create a brand new occasion. This may open a web page the place we will outline occasion parameters.

Choose the corresponding occasion sort. On this tutorial, we’ll launch a quite simple server with minimal technical necessities, so t3.nano must be ample for our wants.

For its containers, AWS makes use of SSH authentication. When creating a brand new occasion, it’s essential to create a brand new key pair that may permit us to log in from the native machine utilizing the SSH protocol. Click on on Create new key pair.

Assign a reputation to the brand new key. We is not going to dive into the attainable choices right here, so we’ll select RSA as the important thing pair sort and .pem because the personal key file format.

To avoid wasting time, in our demonstration software we is not going to fear about safety. For the community settings, tick all of the checkboxes similar to SSH, HTTP, and HTTPS site visitors.

Nice! By clicking Launch occasion, AWS will create a brand new occasion.

After the occasion is created, a .pem file will likely be downloaded to your native machine. This file comprises the personal key that enables SSH authentication. As apply, retailer this file in a protected location as a result of AWS doesn’t present a strategy to get well it whether it is misplaced.

By opening the EC2 dashboard, you’ll discover that the created occasion has an related IP deal with. This IP is proven underneath the label “Public IPv4 deal with”. For instance, within the picture under, it’s “16.16.202.153”. As soon as we deploy our software, will probably be accessible from a browser utilizing this IP deal with.

# 02. SSH connection

AWS gives a number of methods to carry out authentication. In our case, we’ll use the SSH mechanism.

Within the occasion menu, click on Join and choose SSH shopper from the highest bar.

Open the native terminal and, utilizing the screenshot above as reference, copy and execute command #3 (chmod 400 "<key_name>.pem") together with the command proven under the “Instance” label. Make certain your present terminal listing matches the placement the place the .pem key was downloaded within the earlier step.

In the course of the SSH connection, the terminal would possibly immediate whether or not to proceed. If it does, sort “sure”.

At this level, we’re efficiently linked from the native terminal to the EC2 occasion. Any instructions entered into the terminal will now be executed instantly within the EC2 container.

# 03. Atmosphere configuration

After connecting to the occasion from the native terminal, the following step is to replace the bundle supervisor and set up Python together with Nginx.

sudo apt-get replace
sudo apt set up -y python3-pip nginx

To redirect site visitors to our software, we have to create an Nginx configuration file. This file must be positioned within the listing /and so on/nginx/sites-enabled/ and might have any customized identify. We’ll add the next configuration to it:

server {
  hear 80;
  server_name <Public_IP_Address>;
  location / {
    proxy_pass http://127.0.0.1:8000;
  }
}

Mainly, we’re specifying that any exterior request despatched to the EC2 occasion’s IP deal with on the default port 80 must be redirected through a proxy to the applying working contained in the EC2 container on the deal with http://127.0.0.1:8000. As a reminder, that is the default HTTP deal with and port assigned by FastAPI.

To use these modifications, we have to restart Nginx:

sudo service nginx restart

If we’ve got a FastAPI server that we want to launch, the best manner could be to publish it on GitHub after which clone the repository onto the EC2 occasion.

git clone <GitHub_URL> <listing>
cd <listing>

Create and activate a digital surroundings:

python3 -m venv venv
supply venv/bin/activate

Set up the required Python necessities (assuming that the cloned repository comprises a necessities.txt file):

pip3 set up -r necessities.txt

Run the server:

python3 -m uvicorn <server_filename>:app

Open the browser and enter the IP deal with of the occasion.

Make certain to make use of the HTTP (not HTTPS) protocol. For instance: <a href="http://16.16.202.153/" rel="noreferrer noopener" goal="_blank">http://16.16.202.153</a>. The firewall would possibly block your connection, however it is best to proceed to open the net web page. Add /docs after the URL to open Quick API Swagger.

Train

If you need to run a FastAPI instance, you may create a easy repository consisting of only a fundamental.py file and a necessities.txt.

fundamental.py

from fastapi import FastAPI

app = FastAPI()

@app.get("/")
def read_root():
    return {"message": "Whats up, World!"}

necessities.txt

fastapi
uvicorn

Importing recordsdata

Should you attempt to add a file to a server and obtain a 413 standing with the error message “Error: Request Entity Too Giant”, it’s doubtless as a result of Nginx has a restrict on the utmost file dimension that may be uploaded. To resolve this problem, go to the Nginx configuration file and specify the utmost allowed file dimension through the use of the client_max_body_size directive (setting it to 0 signifies no limits on enter file sizes):

server {
  hear 80;
  server_name <PUBLIC_IP_ADDRESS>;
  location / {
    proxy_pass http://127.0.0.1:8000;
    client_max_body_size 0;
  }
}

After altering the configuration file, don’t forget to restart Nginx.

Conclusion

On this article, we’ve got realized methods to shortly create a working EC2 occasion utilizing a FastAPI server for example. Though we didn’t observe the most effective deployment and safety practices, the principle aim of the article was to offer minimal info for freshmen to launch their first server on AWS.

The following logical step within the AWS examine roadmap could be creating a number of EC2 cases and connecting them to one another.

All pictures except in any other case famous are by the creator.

Join with me