← Financial Cloud Cloud Cloud Club · AWS Re:cap

Vertex Macro | Financial Cloud Cloud · AWS Re:cap

AWS Re:cap 06: FSI Meetup 2025 Q4 - Stifel Modern Data Platform

Speaker: Martin Nieuwoudt, Hossein Johari, Srinivas Kandi, Amit Maindola

Session: 06

Session
Summit Dev Lounge2026 Re:cap
01 Encode Architecture as Steering for AI Agents
02 Agent Harness Is the Real Engineering Moat
03 Ask Observability Data in Plain Language
04 Serverless AR Game with Bedrock AgentCore
05 Multi-Agent Quant Backtesting on AgentCore
06 Blog to Slides in Three Minutes with Kiro
AWS Community Day Hong Kong 2025 Re:cap
02 AWS Compliance with Terraform
03 Beginner to Builder An AWeSome Cloud Journey
04 Team-First Serverless Engineering with Laravel & Bref
05 Event Opening - AWS Community Day Hong Kong 2025
06 Agent-to-Agent: Building Interoperable AI on AWS
07 Utilize another telemetry data for faster improvement with AI agent
08 Graduating from Vibe Coding: Spec-Driven Development with Kiro
09 Automated Testing using MCP & AI Agents
10 Modernizing Telecom Security ML Powered Approach
11 Rethinking GenAI Agent: RAG & MCP
12 Disaster and Emergency Response with TAK and AWS
13 Rethinking Serverless Application Workflows from a Testing Perspective
14 Practical AWS FinOps for Cloud Success
15 AI-Powered Global Pure-Alpha Macro Trades on AWS: Revolutionizing Risk-Adjusted Asset Returns
FSI Recap
01 Modern Trade Lifecycle: Trading to Settlement
02 Goldman Sachs: Fast Track your applications onto Cloud - AWS Re:cap Q1/2023
03 Zurich Insurance Group: Building an Effective Log Management Solution on AWS
04 FSI Meetup 2025 Q4 - Brex Database Disaster Recovery
05 FSI Meetup 2025 Q4 - A Graviton Migration Success Story
06 FSI Meetup 2025 Q4 - Stifel Modern Data Platform
07 FSI Meetup 2025 Q4 - Financial Transaction Data Reconciler PayPal
08 FSI Meetup 2025 Q4 - Scaling Resilience
09 Maximizing AI Inference Cost Efficiency: Strategic Adoption of AWS GPU Instances
10 Advanced Agentic AI Design Patterns
11 Build New Modern Apps on AWS
AWS re:Invent 2025
01 Coinbase re:Invent Recap (IND3312)
02 Building the Future Trading Platform Leveraging AI and AWS
03 Trading Innovation: Jefferies' AI Assistant on Amazon Bedrock (IND3315)
04 How FSI Revolutionized HFT Analytics with Agentic AI (GBL302)
05 Improving Distributed Systems with Amazon Time Sync Featuring Nasdaq
06 Amazon Aurora HA and DR Design Patterns for Global Resilience (DAT442)
07 Building Agentic AI: Amazon Nova Act and Strands Agents in Practice (DEV327)
08 Deep Dive into Amazon Aurora and Its Innovations (DAT441)
09 Deep dive on Amazon S3 (STG407)
10 Nasdaq: Build Resilient Infrastructure for Global Financial Services (HMC327)
11 What's New with AWS Lambda (CNS376)
12 Spec-Driven Development with Kiro (DEV314)
13 Amazon's finops: Cloud cost lessons from a global e-commerce giant (AMZ308)
14 Tick to trade latency trading platforms on aws
Government data
01 The AI Era: The Boundary Between Development and Design Is Disappearing
02 On-Device Multimodal AI and Smart-City Practice
03 Large-Model Capability Evaluation and a Method for Landing AI Projects
04 Controlled End-to-End Automation of Government Development with Cloud Agents
05 A New Software Ecosystem for the Agent Era, Seen Through Multi-Agent Systems
06 AI-Driven Macro Quantitative Research and Smart Governance
07 Authorized Operation of Public Data and Smart-Government Practice
08 Putting Data Assetization into Practice: Rights, Compliance, Engineering Governance, and Digital-Government Cases
09 AI for Mental-Health Public Welfare: Governance, Architecture, and Practice of a Trustworthy Platform
Amarathon 2025 Recap
01 A Developer’s Roadmap to Architecting for Agents
02 Amazon Bedrock Data Automation
03 Multi-Agent on AgentCore
04 Building Agentic AI Nova Act and Strands Agents in Practice
04 Accelerating Migration Projects with Kiro using Spec-Driven Development
06 From Matching to Understanding: Personalized AI Search Practice Driven by AgentCore Memory
07 Observe to Optimize – LLM Observability to AIOps Turning real-time insights into intelligent automation
08 Deploying TEAM and Building the Best Engineering Team
09 Five Hard Lessons from Five Years of So-Called Serverless Databases
14 What if AI does my job How Q Developer CLI and Kiro have changed my daily routine
16 Velocity with Vigilance: Security Essentials for Amazon Bedrock Agent Development
26 Run OSS LLMs on a Single H100 Smarter, Cheaper, Faster
28 A Modern Unified Metadata Architecture: New Approaches to Breaking Down Data Silos
29 Serverless MediaOps: Automating Video Workflows with AI on Amazon Web Services
30 Architecting for Efficiency and Reliability with Performance Testing at Scale
31 Connecting the World Through Open Source: Practical Journey of Technology, Community and Global Developer Relations
33 Building Streaming Iceberg Tables for Real-Time Logistics Analytics
34 Accelerating Large-Scale Robot Strategy Training: An Automated Closed-Loop Architecture Based on Kiro, Trainium, and EKS
35 From Vibe to Viable with spec driven development
36 Making Cloud Cost Analysis Smarter: Building FinOps Intelligent Agents with Strands and AgentCore
37 Transform Conversational Agentic AIOps for K8s Using CNCF Kagent, K8sGPT, and Nova Sonic

Stifel Overview:

● Around 10,000 associates across North America and Europe

● Approximately $540 billion in assets under management

● Mission: Making dreams come true through mortgages, retirement planning, and capital provision

● Notable project: Financing the Mackinac Bridge in the 1950s

Data Journey Analogy:

● Pre-modernization: Like waiting for a ferry with limited capacity, long wait times, and high operational overhead

● Post-modernization: Like the Mackinac Bridge, enabling a continuous flow and seamless connection

Modern Data Platform:

● Goal: Connect people, processes, and insights seamlessly

● Analogous to the Mackinac Bridge uniting Michigan

● Unites the business through data

Premodernization Environment:

● Used expensive and powerful SQL server

● High availability with six nodes

● One node resided on AWS cloud

● Faced issues like growth (both organic and through mergers and acquisitions)


Challenges Premodernization:

● Resources were contentious due to storage and compute being on the same servers

● Rapid growth led to multiple business teams developing their own business logic

● Created technical sprawl with minor differences in processing for different business units

● Lack of data governance, data catalog, and knowledge of available data

Business Drivers for Modernization:

● Unified set of data with fully integrated business logic in one place

● No duplication, system should grow without limitations

● Technology should align with business needs, not develop processes based on perceived importance

● Improve operational efficiency, reduce friction, ensure data availability to clients

● Enhance governance, compliance, and control

High-Level Platform Requirements:

● Centralized business logic

● Predefined data products approved by business owners

● Scalable system, easily adjustable, performant under any data or process pressure

● Metadata-driven, event-based notifications for seamless integration

● Continuous processing once sources are ready to meet SLA

● Immediate notification to operations department in case of issues

● Comprehensive monitoring, alerting, and ticketing for observability

Chosen Approach: Data Mesh Architecture

● Hub-and-spoke model with data domains aligned to business units

● Data products shared between business units, allowing access even if not the owner

● Metadata-driven, event-based notifications for seamless integration

● Continuous processing, immediate issue notification, and comprehensive monitoring

Data Catalog and Centralized Publishing:

● Fully open data catalog to inform business of available data

● Centralized place for publishing and defining data to the business


Three-Tier Architecture:

Raw Data Ingestion:

● Collects data from various vendors and trading systems

● Data in different formats, some from outside the country

● Stored in a data lake with historical data (up to 20+ years)

● Most up-to-date section of the data lake

Central Governance Account:

● Acts as a glue between all components

● Supports data sharing between data domains and raw ingestions

● Sends notifications when new data is available in the data lake

● Responsible for governance, data catalog, and business glossary

● Processes run daily to collect data catalog information

● Develop business glossaries

Data Domains:

● Aligned with business operations

● Each domain owns and produces its data, but shares with other domains

● Analytics data domain collects all data for analytics, BI dashboards, reporting, AI applications, and intelligent processes


Key Takeaways for Implementing the Architecture:

Federated Governance:

● Balances domain autonomy with organizational consistency

● Empowers domains to create and manage data products while adhering to centralized quality standards

● Ensures innovation, reliability, and operational excellence

● Improves operational efficiency by reducing system interdependencies and streamlining maintenance

● Achieves cost optimization through reduced development and infrastructure expenses

Technical Best Practices:

Event-Driven Architecture:

● Embraces publish-subscribe patterns

● Messaging pattern: message senders, called publishers, categorize messages into classes, and send them without needing to know which components will receive them.

● Moves away from rigid batch dependencies

● Enables real-time data flows that respond dynamically to business events

Metadata-Driven Architecture:

● Centrally manages dependencies and pipeline states

● Allows intelligent decisions about workflow execution and resource allocation

Standardization on Open Data Formats:

● Uses Apache Hudi for data lake storage

● Ensures interoperability across tech stack

● Provides optimized storage patterns for batch and streaming workloads

● Maintains data consistency

Organizational Transformation:

Breaking Down Data Silos:

● Standardizes toolset and implements data product approach

● Enables seamless data sharing and improves cross-functional collaboration

Empowering Business Domains:

● Grants greater autonomy in data governance

● Allows informed decisions on data sharing vs. domain-specific data

Customer-First Data Set:

● Implements systems for real-time data processing and personalized customer experiences

● Enhances ability to respond to customer needs dynamically

Agile and Responsive Organization:

● Focuses on creating an organization that can better serve customers

● Maintains balance between centralization and domain autonomy

● Embraces latest technological changes


Journey Timeline:

● 2021: Started with high-level architecture

● 2023: Refined architecture, presented to leadership, and received approval

● Engaged AWS Proserve: To help build the architecture

Implementation Phases:

● September 2024: Built and tested core components

● January 2025: Floated limited data to the new architecture

● September 2025: Built API endpoints using data within the architecture

● Current: APIs are part of an application supporting clients; ongoing work to enrich data domains and onboard more applications

Future Focus:

● Building New Data Domains: While enriching existing domains

● Enterprise-Wide Adoption: As more data becomes available on the platform

● Operational Efficiencies: With the shift away from the legacy platform

● Unstructured Data and AI Use Cases: Expanding the platform to include unstructured data and emerging AI applications


Data Mesh Overview:

● Decentralized data architecture

● Treats data as a product

● Shifts ownership from central team to individual business domains

Key Principles:

Domain-Oriented Decentralization:

● Data ownership and management by individual business domains

● Each domain manages its own data products

Data as a Product:

● Data is treated as a consumable product with clear value proposition

● Focus on data quality, discoverability, and accessibility

Self-Serve Data Infrastructure:

● Provides a platform that enables domains to manage their data independently

● Empowers domains with tools and capabilities for data processing and analytics

Federated Computational Governance:

● Establishes standards and guidelines for data quality, security, and compliance

● Balances domain autonomy with organizational consistency

● Ensures data products meet organizational standards while allowing for innovation

Benefits:

● Improved agility and scalability

● Better management, sharing, and analysis of data products

● Enhanced collaboration and cross-functional data usage

● Increased operational efficiency and cost optimization

● Support for real-time data processing and personalized customer experiences