AWS Builder Center

Weekend Showcase Challenge: CloudBank – A Cloud-Native Banking Application on AWS

CloudBank is a cloud-native banking application built with Spring Boot, React, PostgreSQL, Docker, AWS, Terraform, and Kubernetes, providing secure account and transaction management through REST APIs.

Vision

CloudBank is a cloud-native banking application I built to bring together my learning in AWS, Cloud, DevOps, backend development, frontend development, containers, and Infrastructure as Code into one practical project.
The goal was to build more than a simple banking UI. I wanted to understand what happens behind a real application: how a frontend communicates with backend APIs, how backend services interact with a database, how applications are containerized, and how the complete system can be deployed and managed in the cloud.
CloudBank provides a web-based banking dashboard where users can authenticate and perform common banking operations such as managing customers and accounts, making deposits and withdrawals, viewing transactions, and transferring funds between accounts.

What I Built

The application uses a React/Vite frontend and a Spring Boot backend connected to a PostgreSQL database.
The frontend provides a login page and an interactive banking dashboard. I integrated the frontend with the backend using Axios and REST APIs. Authentication is handled through Spring Security, and the application communicates with protected backend endpoints using authentication credentials.
The Spring Boot backend exposes REST APIs for:
  • Customer management
  • Account creation and retrieval
  • Deposits
  • Withdrawals
  • Transaction history
  • Account-to-account transfers
  • Application health monitoring
For example, accounts can be created through a REST endpoint and transactions update the corresponding account balance. I also verified that application data is actually persisted in PostgreSQL rather than existing only in the frontend.

How I Built It

I started by developing the backend using Spring Boot, Java, Spring Data JPA, and REST APIs. PostgreSQL was selected as the relational database because banking data requires structured and persistent storage.
I then developed the frontend using React and Vite, creating separate login and dashboard components. The frontend communicates with the Spring Boot APIs rather than directly accessing the database.
To make the application portable and easier to manage, I containerized the backend and PostgreSQL database using Docker and Docker Compose.
The Docker Compose configuration runs the Spring Boot backend and PostgreSQL as separate containers. PostgreSQL uses a persistent Docker volume so that database records remain available even when the container is restarted.
I verified the setup directly from the EC2 instance and confirmed that PostgreSQL contains the  customers ,  accounts , and  transactions  tables. I also tested the REST APIs using  curl  and successfully created and retrieved customer and account records.

AWS Architecture

CloudBank is deployed on AWS EC2 and integrated with AWS networking components that I configured while building the project.
The main architecture is:
User → React Frontend → Spring Boot REST API → PostgreSQL
The application runs inside an AWS environment using EC2, VPC networking, subnets, route tables, Internet Gateway, and security configuration.
I also used Terraform to practice Infrastructure as Code and define AWS infrastructure in a repeatable way rather than relying entirely on manual configuration.
For container orchestration, I created Kubernetes configurations for the CloudBank namespace, backend deployment and service, PostgreSQL deployment and service, and secret/configuration resources. These manifests prepare the application for a future Kubernetes/EKS deployment.

Challenges and Lessons

One of the biggest learning experiences was connecting all the layers together. A working application locally is very different from an application running on an EC2 instance.
I worked through challenges involving EC2 networking, Docker container communication, PostgreSQL connectivity, Spring Security authentication, frontend-to-backend connectivity, persistent storage, and Kubernetes configuration.
I also learned the importance of separating application components. Keeping the frontend, backend, and database as independent components made it much easier to troubleshoot and understand the architecture.
Another important lesson was persistence. Initially, it was easy to assume that data displayed on the dashboard was simply frontend state. By connecting directly to the PostgreSQL Docker container and inspecting the database tables, I verified that the banking records were actually being stored in PostgreSQL.

What I Learned This Summer

CloudBank brought together many of the technologies I worked with throughout the summer.
I gained practical experience with AWS, Linux, Docker, Docker Compose, PostgreSQL, Spring Boot, React, REST APIs, Terraform, Kubernetes, Git, and GitHub.
More importantly, I learned how these technologies fit together as a complete system.
Instead of learning each tool independently, CloudBank gave me an opportunity to understand the complete journey from writing application code to containerizing it, deploying it on AWS, connecting it to persistent storage, and preparing it for orchestration.

What's Next

CloudBank is still a work in progress. My next goals are to deploy the Kubernetes configuration on Amazon EKS, improve CI/CD automation, add monitoring and observability, strengthen authentication and secret management, and continue moving the application toward a more production-ready architecture.
This project started as a way to practice cloud and DevOps concepts, but it became a much bigger learning experience. Building CloudBank helped me understand that cloud engineering is not just about knowing individual AWS services — it is about understanding how application code, infrastructure, networking, security, containers, databases, and automation work together.

Project

Thank you to the AWS Builder Center community and the builders who shared their projects and ideas throughout the summer. These challenges encouraged me to keep building, experimenting, and taking my projects further.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article