Open Banking on AWS
Publication date: September 7, 2021 (Diagram history)
With this architecture, you can open APIs for authorized third parties and implement Open Banking regulations. Third parties access consumer data (account balances, transactions, statements) or initiate payment submissions with customer consent. This supports use cases such as spend analysis, credit decisioning, and ecommerce payments.
Overview
The following steps describe the architecture:
-
Access the licensed or accredited third-party application and provide consent for the third party to access consumer data or initiate a payment submission request.
-
Use third parties as authorized institutions that provide value-added services on top of regular banking needs (accounts information, payments). This approach supports use cases such as spend analysis, credit decisioning, and ecommerce payments.
-
Validate the authenticity of banks and third parties through a Trust Service Provider (TSP) authorized by a supervisory government body. The TSP issues digital certificates to third parties.
-
Connect the bank IT environment, including AWS and data center components.
Networking and security
With this architecture, you can connect on-premises core banking systems to AWS and expose Open Banking APIs securely. The solution uses AWS Direct Connect for connectivity, AWS Transit Gateway for network hub management, and Amazon API Gateway for API management with AWS WAF integration.
The following steps describe the architecture:
-
Send and receive all new and updated transactions between core banking systems and AWS by using streaming technologies such as Apache Kafka and message queue (MQ) mechanisms.
-
Connect the bank data center to AWS by using a combination of AWS Direct Connect and AWS Site-to-Site VPN. Use two diverse AWS Direct Connect connections for maximum resiliency.
-
Use AWS Transit Gateway as the central hub on AWS to manage interconnectivity between workloads running in different AWS accounts. Share the AWS Direct Connect and VPN connection with other workloads in the bank.
-
Provide secure outbound access from an outbound Amazon VPC through a proxy.
-
Authenticate accredited third parties and provide access tokens through mutual TLS (mTLS) for transport layer security.
-
Expose Open Banking APIs and Authorization APIs through Amazon API Gateway. Integrate AWS WAF with Amazon API Gateway for web protection.
-
Store public certificates of clients in Amazon Simple Storage Service as a trust store for validating requests. Validate the authenticity of third parties against a Trust Service Provider (TSP).
-
Connect Amazon API Gateway to the private subnets hosting microservices in other AWS accounts through a private integration Amazon VPC and AWS PrivateLink.
-
Provide traffic management and domain name resolution by using Amazon RouteĀ 53. Deliver static data through Amazon CloudFront with AWS Shield protection.
Services and operations
With this architecture, you can implement Open Banking API microservices, manage identity, and monitor security posture. The solution uses Amazon Elastic Container Service with AWS Fargate for containerized services, Amazon DynamoDB for consent storage, and Amazon GuardDuty for threat detection.
The following steps describe the architecture:
-
Connect securely between VPCs and services hosted on AWS or on-premises by using AWS PrivateLink.
-
Implement Open Banking API specifications for Account Information and Payments services by using multiple container-based microservices hosted on Amazon ECS with AWS Fargate. Cache customer account information by using Amazon ElastiCache. Host webhooks for payment status in this layer.
-
Store consumer consents, aggregated data, and API performance metrics in DynamoDB.
-
Hold a copy of the system of record in Amazon RDS. Synchronize data in near real time from the bank core system.
-
Implement the identity provider (IdP) for OAuth 2.0 in a separate AWS account so that other workloads in the bank can consume it securely.
-
Provide a separate developer sandbox for the third party to integrate with the bank AWS environment and build their products.
-
Monitor for malicious activity and unauthorized behavior by using GuardDuty. Get a comprehensive view of security alerts and security posture across AWS accounts by using AWS Security Hub CSPM.
-
Collect logs from all services in Amazon S3. Analyze and monitor logs by using Amazon OpenSearch Service.
-
Manage configuration by using AWS Systems Manager. Deploy environments by using AWS CloudFormation. Use Amazon EventBridge, Amazon Simple Queue Service, and Amazon Simple Notification Service for notification capability between services.
Further reading
For additional information, see the following resources: