AWS Financial Services United States Company newsroom

Capital One

IT Operations Automation · Risk Management

Capital One needed early detection of volume anomalies in critical digital transactions such as mobile-app login flows, but as the anomaly-detection model was expanded to cover more transactions, the team faced growing data volume, long training and processing times, memory limits for ML libraries, and significant DevOps toil and scalability challenges in its prior architecture.

"Lambda’s limit at the moment is 15 minutes"
"more than 2,000 applications in AWS"
"more than a third of our apps leveraging serverless infrastructure"
"reduce to only an order of magnitude data from the original data volume"

Reported impact

Business outcome

Capital One successfully moved the anomaly-detection model to a serverless architecture, improving scalability and provisioning, reducing maintenance burden on DevOps teams, and helping the company identify customer-facing transaction issues faster so fixes can be made more quickly.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Capital One migrated its anomaly-detection machine learning workload from a legacy container-oriented design to a serverless implementation on Amazon Web Services (AWS), centered on AWS Lambda. Transaction-volume data from Capital One’s digital platforms, including mobile-app and web-channel critical transactions, is prepared for model training and inference in smaller components rather than one large monolith. To make the workload fit serverless constraints, the team sampled training datasets to cut data volume while preserving model performance, then packaged ML dependencies with Lambda layers and, where necessary, compressed and dynamically installed additional libraries at runtime. Capital One also reviewed any function exceeding Lambda’s runtime ceiling and refactored code or used an AWS asynchronous ML inference option for longer-running steps. Databases on the AWS host automatically scale with demand, while model components are deployed as independently managed microservices to improve scalability, reduce maintenance effort, and speed remediation of customer-impacting anomalies.

Data flow

Volume data from Capital One's mobile-app and web critical transactions is collected in AWS, sampled to reduce training size, and processed by anomaly-detection functions running in AWS Lambda. Those functions load ML libraries through Lambda layers or compressed runtime installs, interact with automatically scaling databases, and return anomaly signals so teams can investigate and fix customer-impacting transaction issues quickly.

Solution architecture

2 components · 2 layers
  1. Compute
    • AWS Lambda Runs the anomaly-detection model's serverless functions, using layers and selective dynamic library installation to fit ML dependencies.
  2. Uncategorized
    • Amazon Web Services (AWS) Provides the cloud environment and serverless ecosystem hosting Capital One's machine learning model and supporting databases.

Architecture clues

  • Capital One describes itself as serverless-first on AWS.
  • Lambda layers were used to package ML libraries, with compressed dynamic installs for additional dependencies.
  • Long-running functions were reviewed individually and some work was redirected to an AWS asynchronous ML inference option.
  • The ML model was decomposed into smaller independently deployed components in a microservices-style architecture.
  • The team relied on automatically scaling databases in AWS when higher data volumes were sent to the host.

Evidence from the source

"Because serverless is a full stack of services you pay for as you go, provisioning is simple."
"Now we are entirely hands-off with maintenance functions."
"The Capital One team used layers to implement each of the libraries."
"We built an ML solution that detects volume anomalies for those critical transactions, allowing any necessary fixes to be made as quickly as possible so we can minimize the impact to customers."
"We started to sample our datasets in order to reduce the size of data and still keep enough information to train the model."
"We successfully moved our ML model to serverless architecture, and found three major improvements."
Transparency Evidence & methodology 90/100 reference value · 94% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Capital One

    Capital One customer story

    First-party
    https://www.capitalone.com/tech/machine-learning/serverless-machine-learning/
    Source type
    Customer-published story
    Published
    Aug 8, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Aug 8, 2024 · Capital One · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.