AWS Data Governance for Financial Services: SageMaker Unified Studio Analysis
- Daniel Rolles
- Jul 3
- 4 min read
Updated: Jul 3
Last week, I had the privilege to be invited to AWS's Generative AI and BI Global Roadshow for Financial Services at their London office, where industry leaders from Aegon UK and NatWest Group shared insights alongside AWS experts. I was particularly privileged to see the demonstrations and get hands-on with the solutions.
The event showcased Amazon SageMaker Unified Studio, Amazon Q Business, and Amazon QuickSight - but more importantly, it revealed AWS's evolving approach to integrated Data and AI governance that has profound implications for how financial institutions should think about these two capabilities.
The Unified Studio Vision
What struck me most was AWS's commitment to a unified business catalogue through Amazon SageMaker Catalog. Built on Amazon DataZone, this isn't just another data catalogue - it's positioning itself as the single source of truth for all data, ML, AI, and compute assets across an organisation.
Beyond Traditional Business Intelligence
Bhasi Mehta's QuickSight demonstration was particularly compelling. The scenario analysis capabilities, blending insights from generative AI directly into traditional BI dashboards, showed how AWS is moving beyond static reporting. Roy Yung's insurance dashboard demo was genuinely impressive - the real-time blending of AI-generated insights with structured data analysis represents a significant evolution in how we think about business intelligence.
This aligns perfectly with what we've been advocating through our D/I O11y framework: observability isn't just about monitoring - it's about creating actionable insights that connect data investments to business outcomes.
The Amazon Q Business Revolution
Ben Haller's demonstration of Amazon Q Business highlighted something crucial for financial services: the integration potential. With M365 and Chrome plugins, plus DBT lambda integration, Q Business isn't just another AI chatbot - it's becoming the conversational interface to your entire data ecosystem.
What particularly impressed me was Amazon Q's democratization approach, built on a three-layered architecture:
Easy, instant insights for everyone through Amazon Q's Generative BI capabilities
Choice of consumption formats including Modern Dashboards, Pixel-Perfect Reports, ML/NLQ, Embedded Analytics, and Data Stories
Unique architecture for performance at scale with auto-scaling, cloud economics, and simple management
Customer Voice
Jey Perayeravan from Aegon shared their rollout to a large body of external users. We loved their approach to deploying internal data to external users in a cost-effective way, demonstrating that enterprise-scale conversational AI deployment is not just possible but practical.
What This Means for Financial Services Data Strategy
Three key observations from the roadshow have significant implications for how banks and financial institutions should approach their data strategy:
1. The Convergence of BI and AI
The blending capabilities demonstrated in QuickSight represent more than feature enhancement - they signal the convergence of traditional business intelligence with generative AI. Financial institutions need to think beyond "AI projects" and start considering how AI-generated insights integrate with existing reporting and analytics.
2. Governance Must Be Built-In, Not Bolted-On
AWS's unified approach to governance across all data and AI assets reflects a fundamental shift. Traditional approaches that treat data governance as a separate concern from AI development are becoming obsolete. The SageMaker Catalog approach embeds governance into every workflow.
3. Conversational Data Access at Scale
Amazon Q Business's integration patterns suggest that conversational interfaces to data will become standard, not exceptional. The ability to scale to tens of thousands of users while maintaining security and governance is no longer a technical barrier.
The Observability Connection
What resonates most with our work at BearingNode is how AWS's integrated approach addresses the core challenge we've identified in traditional data governance: you can't improve what you can't see, and you can't govern what you can't observe.
The SageMaker Unified Studio architecture provides comprehensive observability across:
Discovery and Lineage: Automatic cataloguing and relationship mapping (see the post on OpenLineage Compliance for DataZone here)
Quality and Compliance: Built-in data quality monitoring and regulatory compliance tracking
Value Attribution: Clear connections between data assets and business outcomes
Usage and Performance: Real-time observability of how data and AI assets are being utilised (human or machine consumption events are critical - watch this space on the blog)
This mirrors the core capabilities of our D/I O11y framework, but delivered as an integrated platform rather than assembled from disparate tools.
Looking Forward: The Platform vs. Framework Decision
For financial institutions evaluating their data strategy, the AWS roadshow highlights a critical decision point: platform consolidation versus best-of-breed integration.
AWS is clearly betting on platform consolidation - the vision is compelling, and the integration is impressive. However, most financial institutions operate in multi-cloud, multi-vendor environments where complete platform consolidation isn't realistic.
This is where frameworks like our D/I O11y approach become crucial. Whether you're fully committed to AWS's unified platform or operating in a heterogeneous environment, the principles of comprehensive Data and Information observability remain the same:
Connect data investments to business value
Embed governance into operational workflows
Provide real-time visibility into data quality and usage
Enable conversational access while maintaining security
The Practical Next Steps
For financial services leaders considering how to respond to AWS's vision:
Vendor Strategy: What's your vendor strategy? Is it "hard bind" to AWS? If you are looking at multi-cloud and vendor independence - how can you replicate the unified functionality?
Data Architecture: Evaluate your current data architecture against the unified catalogue model - where are your governance gaps?
Pilot conversational AI interfaces: like Amazon Q Business to understand the change management implications - BUT - think about your Gen AI governance (see point above about being built-in and not bolted on).
Assess your BI strategy in light of AI-native analytics capabilities
Consider how your existing tools and processes map to an observability framework (see our post on this here)
The AWS roadshow demonstrated that the future of data and AI in financial services isn't just about better tools - it's about fundamentally different approaches to how we discover, govern, and extract value from data assets.
Whether you adopt AWS's platform or build your own integrated approach, the principles of comprehensive Data and Information observability are becoming essential for competitive advantage.



