Architecting Large-Scale Migrations with Fannie Mae and the NRO (AWS re:Invent 2025 – WPS201)

Published: (December 13, 2025 at 08:48 AM EST)
4 min read
Source: Dev.to

Source: Dev.to

Why large migrations are hard

The session opens by revisiting familiar migration drivers: lowering compute costs and increasing innovation velocity as organizations move from on‑premises environments to rehosted, replatformed, and cloud‑native architectures.
The speaker frames migration strategy in terms of the “7 Rs,” emphasizing that large‑scale programs almost always use a mix of these approaches rather than a single pattern.

Strategy

StrategyDescriptionBest For
Rehost“Lift and shift” to cloudQuick migration, minimal changes
RelocateMove to different infrastructureHypervisor‑level migrations
RepurchaseMove to SaaS solutionsReplacing custom applications
RetainKeep on‑premisesCompliance or latency requirements
RetireEliminate unused applicationsReducing technical debt
ReplatformMinor cloud optimizationsModerate benefits with low risk
RefactorRedesign for cloud‑nativeMaximum cloud benefits

Key Message: Tooling alone is not enough, especially when dealing with diverse legacy systems, complex databases, and tight budgets. Organizations with limited cloud experience must invest early in automation, governance, and repeatable mechanisms for account management.

The session recommends using an AWS Migration Readiness Assessment (MRA) as an on‑ramp for any large program. The MRA process helps:

  • Inventory applications and discover dependencies
  • Determine appropriate migration strategies per workload
  • Avoid one‑off, unstructured decisions

Migration Assessment Phases

PhaseFocusKey AWS Tools
AssessDiscovery & planningApplication Discovery Service, Migration Readiness Assessment
MobilizeSetup & preparationControl Tower, Landing Zone, Account vending
Migrate/ModernizeExecution & optimizationMigration tools, Well‑Architected reviews

In parallel, organizations should establish an AWS Control Tower‑style landing zone or “account vending machine” to provision new accounts quickly and consistently, with built‑in guardrails for security, compliance, and governance.

AWS Well‑Architected Framework

The framework serves as the backbone for design and review. The six pillars are positioned as a way to reason about trade‑offs for each workload, not as a checklist to satisfy after migration.

PillarFocus AreaKey Considerations
Operational ExcellenceRunning & monitoring systemsAutomation, procedures, continuous improvement
SecurityProtecting information & systemsIdentity, permissions, data protection
ReliabilitySystem availability & recoveryFault tolerance, backup, disaster recovery
Performance EfficiencyUsing resources effectivelyRight‑sizing, monitoring, technology selection
Cost OptimizationDelivering value at lowest costResource optimization, pricing models
SustainabilityMinimizing environmental impactEfficiency improvements, renewable energy

Practical Tip: Ask business stakeholders which pillars matter most for each application. Some workloads may emphasize reliability and operational excellence, while others prioritize cost or performance. These decisions should drive architecture choices, capacity planning, and operational runbooks.

Cloud Center of Excellence (CCoE)

A cross‑functional team spanning:

  • ☁️ Cloud architecture
  • 🖥️ Infrastructure
  • 🔒 Security
  • ⚙️ Operations
  • 💻 Software engineering

CCoE Responsibilities

  • ✅ Standardizing landing zones and network patterns
  • 🔐 Defining IAM controls and security policies
  • 💰 Establishing cost‑management practices
  • 📚 Codifying best practices and lessons learned
  • 🚀 Enabling innovation across business units

Both Fannie Mae and the NRO leveraged CCoEs to significantly increase their “innovation velocity” after completing initial migrations.

Fannie Mae Forecast Transformation

Business Context

  • Purchases home loans from lenders
  • Packages them into mortgage‑backed securities
  • Sells securities to investors

Accurate, timely forecasting of portfolio performance is mission‑critical.

Challenges

ChallengeImpact
Spreadsheet‑heavy processesManual errors, limited scalability
Fragmented systemsData silos, integration complexity
End‑of‑life infrastructurePerformance bottlenecks, maintenance costs
Spread‑thin expertiseKnowledge silos, single points of failure
Heavy customizationsSlow change cycles, brittle systems

Program Goals (Forecast Transformation Program – launched Sep 2023)

MetricBeforeTargetImprovement
Forecasting lifecycle~80 days~10 days87.5 % reduction
Stress‑test executionSequentialParallelConcurrent processing
System consolidation~80 systems1 platform98.75 % reduction
Calculations consolidated~2,000UnifiedSingle source of truth
Loan records capacityLimited1.5 B per runMassive scale

Key attributes of the solution:

  • ⚡ Auto‑scaling compute based on demand
  • 🔒 Strict regulatory compliance (security, auditability, data quality)
  • 🎭 Holistic approach – tackling people, process, technology, and governance simultaneously

Architecture Overview

ComponentAWS ServicePurposeKey Benefits
Data BackboneAmazon S3Unified data domainStores input data, model outputs, calculation results, analytics data
Compute EngineAmazon EMRBig data processingHandles billions of loan records across multiple clusters; auto‑scales
OrchestrationAWS Step FunctionsEnd‑to‑end workflowCoordinates data ingestion, models, calculations, system integration
Metadata & ConfigAurora + DynamoDBConfiguration managementStores scenarios, model parameters, calculation rules
User InterfaceAngular on AWS FargateBusiness user experienceEnables scenario definition, input specification, execution triggers
AnalyticsAmazon SageMaker + TableauReporting & analysisSupports regulatory reporting and internal analytics

Business Rules in YAML

A clever design encodes business calculations in YAML, which:

  • ✅ Decouples business logic from application code
  • ✅ Enables business‑driven changes without code redeployment
  • ✅ Reduces development cycle time for rule updates
graph TD
    A[Business User Input] --> B[Data Ingestion]
    B --> C[S3 Data Backbone]
    C --> D[Model Execution]
    D --> E[EMR Calculations]
    E --> F[Output Processing]
    F --> G[Analytics & Reporting]

Workflow steps

  1. User Input: Business users select scenario types and enter assumptions via UI.
  2. Data Ingestion: Platform pulls data from multiple systems of record.
  3. Data Storage: All data written to the S3 data backbone.
  4. Model Execution: Invokes existing and new platform‑specific models.
  5. Rule Application: EMR applies thousands of YAML‑defined business rules.
  6. Output Distribution: Results routed to downstream systems via APIs and SNS.
  7. Analytics Preparation: Data prepared for regulatory and management tools.

Implementation Challenges

ChallengeScaleSolution Approach
Team coordination100+ engineersStandardized guardrails, coding standards, integration patterns
System integration76 upstream/downstream systemsCareful API design, minimal disruption approach
Program durationMulti‑year timelineConsistent governance, incremental delivery, automated testing

The session highlighted that combining proven migration patterns, a strong governance framework, and a dedicated Cloud Center of Excellence enables organizations like Fannie Mae and the NRO to execute large‑scale migrations while maintaining security, compliance, and operational excellence.

Back to Blog

Related posts

Read more »