Boloro is a patented transaction authentication and mobile payment network. Their mission is to empower everyone, who owns and wants to pay by mobile phone, with access to secure financial services, improving quality of life and eliminating the hassles of cash.
Boloro had a project they needed to implement in one of their customers, which they intended to implement on AWS. Boloro’s former partners designed the AWS solution and architecture, which had a several errors and issues, which meant it wasn’t consistent or ready to be implemented.
The project consisted of the creation and implementation of an NFT Marketplace. Boloro intended to create an infrastructure that would be redundant, fault tolerant and multi-region. Even though some services didn’t work or supported a multi-region deployment, it was a client requirement to replicate the architecture on both regions, which they needed to be implemented in a short period of time.
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.
To create the NFT Marketplace, the whole infrastructure was implemented from scratch. It used services like Aurora and DocumentDB to be the databases behind the Website. Aurora DB was running PostgreSQL as a Cluster, and as a deployment on Multi-Az and Multi-Region, with a Global Database, to create redundancy. Document DB was used for data persistency, deployed in multi-AZ and multi-Region.
EC2 and EBS were used for compute purposes, mainly used on the Bastion Host, Kibana and Fluentd instances as well as the EKS Cluster nodes. The EKS Cluster, was responsible to provide the application layer to the Marketplace, it was composed by eight EC2 instances and with the Auto Scaling Group, it would scale up to twelve instances based on the usage and load of the website, while the instances storage is stored on EBS.
All the Kubernetes images are stored in ECR. All the assets that are shown within the Marketplace are stored in S3 buckets, as well as the website pages. These contents will be shared via CloudFront Distributions, used in combination with Certificate Manager to use the customer custom domain, that is self-hosted.
The CloudFront Distributions are behind a WAF that restricts the allowed traffic. Alongside the Kubernetes Cluster in EKS, based on Ingress Controller, it was deployed an Elastic Load Balancing.
The KMS was used to create a Customer Managed Key that was required to create the MSK Cluster. The MSK Cluster, based on Kafka, was deployed to be a future replacement for SQS, that was responsible to queue the requests that were done to the EKS Cluster.
IAM was used to allow the Boloro Team to access the AWS platform. It was request by the Customer, the usage of Kibana and Fluentd to monitor their Kubernetes Nodes and to monitor all the activity and usage in AWS, to achieve this, CloudWatch and CloudTrail were used.
OpenSearch was used to allow the customer to ingest, secure, search, aggregate, view and analyse the data from their business activity.
Figure 1 - Boloro Architecture
Based on the customer's concerns of high availability and fault tolerance, the architecture was deployed as Multi-AZ and Multi-Region.
All the services that supported a multi-region approach, were being replicated from the Ireland Region to Frankfurt.
Results and Benefits
As this project was implemented from the scratch, there are no improvements, but compared with the previous architecture and design that was made by Boloro’s former partners, the architecture and infrastructure was more detailed and well defined.
Due to Boloro’s time constraints and agreements with their client, the project was implemented in a very short period of time, while respecting the schedule.
From the beginning, the infrastructure was designed taking into consideration a big guideline, cost saving and optimization. The reason was to obtain the best cost/performance solution, but also to save enough money to invest in an IT Team to manage their AWS infrastructure. Boloro then decided to delegate this task to Magic Beans’ Managed Services Department.
The Managed Services Team would be responsible for maintaining the platform and the infrastructure within, as well as to keep the project below the defined budget, following the Cost Optimization Guidelines as well as other principles from the Well Architected Framework.
Another Boloro’s request that was achieved, was the Marketplace availability, ensuring no down-times. Due to this request, Magic Beans focused on creating an architecture that would be as fault tolerant as possible, while being as secure as possible.
Ready to get started?
To learn more about how AWS and Magic Beans can help your business, contact us at firstname.lastname@example.org
© Copyright - | magic beans | All Rights Reserved | Powered by: valkirias