Temenos T24 Transact

The core banking solution from Temenos uses AWS managed services to provide security and elasticity with low maintenance overhead.

AWS Cloud
Access to T24 is controlled and
1 monitored through the Amazon
API Gateway.
AWS Security services such as
Amazon Elastic AWS Secrets Amazon CloudWatch 2 AWS Web Application Firewall
Container Registry Manager
(AWS WAF) and AWS Shield
provide security at the
AWS WAF AWS Shield 2
perimeter.
OLTP transactions are handled
3 in scalable, containerized
Amazon ECS application processes running
Elastic Load Amazon ECS Amazon MQ Relational 4
Application in Amazon ECS.
Balancing Application Database
Containers 3 Containers
4 For a relational database, you
can use Amazon Relational
Database Service (Amazon RDS)
Amazon API 1 for Oracle or you can use
Gateway NuoDB (which runs in
containers).
Amazon Kinesis 5 Events from selected topics of
5 Kinesis Streams are ingested
into Amazon DynamoDB tables
6
using AWS Lambda.
Read-only requests are served
6 from query optimized Amazon
Amazon Route53 AWS Lambda Amazon DynamoDB AWS Lambda DynamoDB tables through
AWS Lambda.

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Reference Architecture
 Temenos T24 Transact
VPC & Networking Architecture

AWS Cloud
Access to the VPC is available
1 only through AWS PrivateLink
(see the Availability Zones
Architecture diagram on the
next page).
AWS WAF AWS Shield AWS Certificate AWS Secrets Amazon Elastic Amazon CloudWatch Amazon S3
Manager Manager Container Registry Amazon API Gateway private
2 endpoints can be used for
secure on-premises access
VPC through a VPN or AWS Direct
3 Connect.
Endpoint Endpoint Endpoint Endpoint
1 AWS services are accessed
3 from the VPC through
AWS Fargate AWS Fargate
endpoints, which removes the
Users Network Load need for internet access.
Amazon API Balancer 4
Gateway TCIB TCMB Amazon RDS You can run your containers in
T24 4 an AWS service managed by
Amazon Elastic Container
VPC Amazon MQ Service (Amazon ECS). In this
Application APIs UXPB Browser T24 T24 Endpoint diagram, the containers run on
Load Balancer AWS Fargate. You could also
T24 run your containers on
Branch
Endpoint Amazon Elastic Compute
Users
Cloud (Amazon EC2), or a
2 combination of both AWS
Fargate and Amazon EC2.
AWS Lambda Amazon DynamoDB AWS Lambda Amazon Kinesis

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Reference Architecture
Temenos T24 Transact
Availability Zones Architecture

VPC
Availability Zone A
This architecture diagram
Private Subnet 1 shows two Availability Zones,
but the architecture can be
AWS Fargate 4 AWS Fargate extended to three Availability
Zones.
5
TCIB TCMB Auto Scaling Group AWS Amazon MQ active-standby
Amazon MQ
Amazon RDS
Service 2 provides high availability. You
Primary Endpoints
Active can also use a network of
APIs UXPB Browser 2 T24 T24 T24 brokers for fast reconnection.

Amazon RDS Multiple

3 Availability Zones enhance
3
database availability.
AWS PrivateLink Network Load Application
Balancer Load Balancer
All container services use
4 auto-scaling.

TCIB TCMB T24 can control the scaling of

5 its own services based on
T24 T24 T24 AWS
Amazon MQ Amazon RDS predicted demand.
Service
APIs UXPB Browser Standby Standby Endpoints

Private Subnet

Availability Zone B 1

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Reference Architecture