Project : AWS ECS - RDS Database Configuration (Part 1)

Setup RDS Database and Build Backend Application Docker Image — Deploy to AWS ECS Fargate with Load Balancer (Part 1)

Cloud Architecture of AWS ECS with ALB

Before getting started with setting up AWS ECS Fargate with Load Balancer, let’s get a backend server and create a docker image of it. As I being a Python developer, I am creating a FastAPI application with few API endpoints.

Setup Database

For database, let’s setup a postgresql db instance in AWS RDS.

1. Login to AWS console and go to Amazon RDS dashboard.

2. Click on Create Database button.

3. Create database:

Note: For demo purpose, I will be using free-tier Postgres instance with Password Authentication enabled and all the additional backup, autoscaling, encryption, monitoring, etc. disabled. Please enable the plans based on your requirements.

Section 1. Choose a database creation method: Select Standard create.

Section 2. Engine Options: Select PostgreSQL.

Section 3. Templates: Select Free tier.

Section 5. Settings:

a. DB Instance Identifier: Name your instance. [Name: ecs-fargate-db]

b. Master username: Default is postgres. If you would like to have username other than postgres, add username. It will be login ID for your instance.

c. Master password: Type the password.

d. Confirm password: Type Master password.

Note: Please be sure you store master username and password

Section 7. Storage: Increase Allocated storage if required and Disable autoscaling.

Section 8. Connectivity:

a. Virtual Private Cloud: Default VPC.

b. Subnet group: default

c. Public access: Select Yes if you want to access from outside VPC else select No. Note: Can be controlled from Security Group.

d. VPC security group: Create new and name New VPC security group.

[Name: ecs-fargate-db-SG]

Section 10. Additional configuration:

a. Add initial database name if required, else postgres database is created by default. [Initial Database Name: ecs_alb_db]

b. Disabled Backup, Encryption, Performance Insights, Monitoring, Log Exports, Maintenance, Deletion Protection.

4. Once database instance is created successfully, you can view the connection details on success message toaster and note down password and endpoint.

Note: Endpoint will be used as DB Host.

Build Docker Image of backend server

Here, I have created a FastAPI application and added DB credentials to .env file.

Note: Do not forget to add health check API to the server.

Codebase Structure of FastAPI application

Let’s jump into containerizing the backend application.

1. Add a Dockerfile

2. Build Image

Run the command on project’s root directory.

docker build -t ecs-alb-image .

The command will build an image with name `ecs-alb-image` and tag `latest`.

~ docker image ls
REPOSITORY                TAG               IMAGE ID       CREATED          SIZE
ecs-alb-image             latest            4f8e343e2a11   8 minutes ago    536MB

3. Run Image

Run the image locally to test if the server is running and functioning as desired.

~ docker run -it -p 8000:8000 --rm ecs-alb-image:latest

Thanks to FastAPI providing API documentation by default.

Here, I conclude Part 1 with setting up database in Amazon RDS, dockerizing backend application and building its image.

In order to get your docker image pushed into Amazon Elastic Container Registry (ECR), follow my next article Part 2

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more