NFT Marketplace Migration

## Challenge

Boloro had the infrastructure for their application hosted on their on-premises data center, which was causing them several issues since they were not capable of proceeding with the deploying to Production or Go Live.

Their Web Application consists of an NFT Marketplace, which as the name states, consists of a Marketplace to sell non-fungible tokens (NFT). Based on these issues, their urge to find a proper solution started to arise, turning them to the AWS Cloud and also to Magic Beans.

The project consisted of the migration and modernization of the whole infrastructure of the previously mentioned NFT Marketplace. It was one of the customer's main concerns the possibility of having a highly-available, redundant and fault tolerant infrastructure. Based on this, Magic Beans has created the infrastructure on a Multi-Az and Multi-Region perspective.

## Why AWS and Magic Beans?

Boloro chose Magic Beans as a partner, due to our knowledge, qualification and experience, believing we would bring added value to the project and that we are the ideal partner in their journey on the AWS Cloud.

## Solution

In order to migrate the existing resources that were deployed on-premises into AWS, using AWS Native Services such as AWS Application Migration Services to migrate the Virtual Machines to EC2 Instances and AWS Database Migration Service to migrate the databases into Aurora PostgreSQL.

The infrastructure takes advantages of services such as Aurora and DocumentDB as databases behind the Application. The Aurora is running on PostgreSQL as a Cluster, deployed on Multi-Az and Multi-Region, as a Global Database in order to create redundancy and high availability. As for the Document DB, it is used for the data persistency, and it's also deployed in Multi-Az and Multi-Region.

Services such as EC2 and EBS are used for compute purposes, used for the Bastion Host, Kibana and Fluentd instances and the EKS Cluster nodes. The EKS Cluster is running on Kubernetes and it's responsible for providing the application layer to the Marketplace, and it's composed of eight EC2 instances with an Auto Scaling Group, which will allow the cluster to scale up to twelve instances based on the usage and load of the Web App.

The Kubernetes images that are deployed to EKS, are stored in ECR. As for the Web App assets that are shown in the marketplace, are stored in S3 Buckets as well as the static contents from the website. The Web App contents will be distributed by CloudFront Distributions in combination with AWS Certificate Manager in order to enforce the utilization of TLS and a custom domain.

## Results and Benefits

Since this project consisted of a migration of a couple of resources that were deployed on-premises, there were a lot of improvements from on-premises into AWS. Taking in consideration the customer urgency and time constraints, the project was implemented in a very short period of time and complying with the respected timeline.

From the beginning, the infrastructure was designed taking into consideration big expectations for the usage of the platform from the client side, which throughout the project were possible to perform cost saving and optimizations actions.