Skip to main content

AWS Solutions Library

Guidance for Building a Core Banking System on AWS

Transform your customer experience with a modernized banking architecture

Overview

This Guidance helps financial institutions build a modern core banking system using native AWS services. Banks traditionally have legacy core banking applications, which are monolithic and lack open architecture. With a modern cloud-based core, banks can be more agile and innovate to better serve their financial services customers by adding new functionalities and releasing features quickly.

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

The platform is built using native AWS services, which integrate natively with Amazon CloudTrail and Amazon CloudWatch for monitoring, logging, and auditing purposes. The applications are built as microservices and scale independently of each other using an event-driven architecture. 

Read the Operational Excellence whitepaper 

The Amazon API Gateway and AWS WAF protects all of the API requests coming into the platform. The various resources are also logically isolated from each other using VPCs. 

Read the Security whitepaper 

All services are scalable to multiple AZs within the region to provide high resiliency. Reliability is also improved by using Amazon MSK to capture data and to build an event-driven platform. 

Read the Reliability whitepaper 

Amazon FSx for Lustre is a shared file system suitable for batch processing requirements where the batch jobs need to finish within a certain timeframe. In addition, real-time transactions need to be written to the database and the response sent within about 200ms. This is achieved by having Direct Connect with the bank’s data center for network connectivity and having as few hops as possible for the transactions to be written to the ledger database. 

Read the Performance Efficiency whitepaper 

Amazon QLDB is a serverless database and the customer only pays for what they use. Amazon Elastic Kubernetes Service (Amazon EKS) also allows customers to build a microservices platform and scale the services as needs change. 

Read the Cost Optimization whitepaper 

Leveraging native AWS services and serverless technologies such as Amazon QLDB, API Gateway, Amazon Simple Storage Service (Amazon S3), and Amazon DynamoDB helps build a platform that scales with growth in business and helps the bank avoid building and keeping over-provisioned resources.

Read the Sustainability whitepaper 

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

Did you find what you were looking for today?

Let us know so we can improve the quality of the content on our pages