Market Data Ingestion Engine
Ingests raw data from Markit, ICE, MSCI, and other providers, reads it from S3, processes it through Lambda, stores results in DynamoDB, and loads XML output into Fusion Invest.

An AWS-native, event-driven platform that replaced a legacy trade booking application and automated market data integration from Markit, ICE, and MSCI, delivering financial data transformation into Fusion Invest and Finastra for brokers and traders.

A financial technology client needed to modernize how its brokers and traders handle complex financial instruments and market data. Its legacy trade booking application slowed down execution, and raw feeds from Markit, ICE, MSCI, and other providers arrived in disparate formats that required heavy transformation before use in Fusion Invest. Ditstek engineered a fully AWS-native, event-driven platform that removes the outdated front-end, automates financial data transformation into XML and FIXML formats, and connects critical financial systems, giving the client scalable market data integration with less manual intervention.
Brokers and traders were forced to book Foreign Exchange (FX), Interest Rate Swaps (IRS), and Cross-Currency Swaps (CCS) trades through an inefficient legacy trade booking application.
The outdated interface created unnecessary friction in fast-paced trading environments, slowing down critical trade execution at the moments when speed and accuracy mattered most to traders.
Raw market data feeds from Markit, ICE, MSCI, and other providers arrived in different formats, making market data integration a significant operational bottleneck for the business.
Before Fusion Invest could use any incoming feed, the data needed complex financial data transformation, a demanding process that the existing setup could not handle efficiently.
Without the right architecture, the transformation process risked data delays, manual intervention, and downstream reporting failures that could disrupt trading operations and the teams depending on them.
The client needed a highly scalable and flexible architecture that could handle changing data loads and new provider formats without constant code changes or custom maintenance.
Ditstek replaced the legacy front-end and built a serverless, event-driven AWS platform for financial workflow automation, combining direct trade booking, automated orchestration, configuration-driven transformation, and privileged access security in one scalable architecture.
Brokers and traders now book FX, IRS, and CCS trades directly within Finastra, removing the legacy application as the front-end and consolidating the entire trading ecosystem.
Stateless AWS Lambda functions replace continuously running servers, so the system scales automatically in response to API calls, storage events, and message queues across the whole data pipeline.
AWS EventBridge serves as the central event bus, routing events to Lambda, SNS, SQS, and Step Functions, and reshaping data through input transformation before delivery.
AWS Step Functions coordinate multiple Lambda functions across each data workflow and react to AWS service events automatically, freeing the platform from fragile custom state management logic.
Parsing and transformation logic lives outside the core code in YAML, Jinja2, and XSLT configuration files, so new data formats can be supported without rewriting the application.
CyberArk Privileged Access Management secures the infrastructure, with strict network and IP restrictions limiting CyberArk administration to approved AWS subnets instead of all VPC traffic.
The platform covers the full trade and market data lifecycle, from file ingestion and email processing to transformation, trade booking, downstream responses, and secure access, all orchestrated through AWS serverless services.
Ingests raw data from Markit, ICE, MSCI, and other providers, reads it from S3, processes it through Lambda, stores results in DynamoDB, and loads XML output into Fusion Invest.
Replaces the legacy trade booking application, letting brokers and traders import and book FX, IRS, and CCS trades directly into Finastra through automated AWS services.
A control job sweeps new Markit files to S3, where a Step Functions state machine identifies each file, converts it to FIXML via Lambda, and hands it to Finastra's SFTP pickup.
A kickoff Lambda runs every 10 minutes, passing S3 configuration through EventBridge to Step Functions, which fetch emails via Microsoft Graph API and save attachments and content automatically.
Downstream responses land in S3 and trigger SQS and Step Functions, which run a Response Lambda to update DynamoDB and an Output/Excel Writer Lambda to finalize data.
Users access the interface through an Application Load Balancer with Cognito/OIDC authentication, upload files for Excel parsing and validation, and track long-running operations through live status tables.
Files are processed with Python 3.12, Polars for structured data, openpyxl for Excel, and lxml, XSLT, and Jinja2 for XML handling and template-based financial message generation.
State machines defined in Amazon States Language can be triggered via the AWS SDK for .NET, the AWS CLI, or S3 uploads, with CloudWatch monitoring executions and Lambda logs.
CyberArk secures AWS-hosted resources with session monitoring, session recording, automated password rotation, and secure credential vaulting, so privileged access to the platform stays tightly controlled and fully traceable.
Moving trade booking into Finastra retired the legacy application completely, giving brokers and traders one simpler workflow for booking all FX, IRS, and CCS trades.
Market data integration from Markit, ICE, MSCI, and other providers now runs automatically end to end, reducing the manual intervention that previously slowed data delivery.
The serverless, event-driven architecture scales automatically with API calls, storage events, and message queues, so the client no longer runs or manages continuously running application servers.
Configuration-driven financial data transformation lets the team support new provider formats by updating YAML, Jinja2, or XSLT files instead of changing the core application code.
Step Functions and EventBridge removed the need for fragile custom state logic, making workflows more reliable, lower-maintenance, and easier to monitor through CloudWatch and Grafana.
CyberArk PAM with subnet-level restrictions, session recording, and automated password rotation gives the client strong control over privileged access to its financial infrastructure on AWS.