Jonathan Lalou's Blog

Posts Tagged ‘AWSReInvent2025’

Lecturer

Tom Godden is an Executive in Residence at Amazon Web Services (AWS), where he draws on his prior role as Chief Information Officer at Foundation Medicine, a leading genomics diagnostics company in Cambridge, Massachusetts. Ian (co-presenter) offers additional insights from regulated environments.

Abstract

Regulated industries face a persistent dilemma: how to deliver software rapidly while satisfying stringent compliance requirements. Traditional development models, with their linear handoffs and manual processes, often exacerbate this tension, producing delays, fragmented evidence, and a compliance burden that feels detached from core engineering work. Modern approaches, however, demonstrate that compliance can emerge naturally from practices focused on quality and automation. By integrating tools like version control and continuous pipelines, organizations generate robust audit trails as a byproduct of efficient delivery. This article examines the flaws in legacy methods, details the mechanisms of contemporary practices, explores the leadership needed for change, and considers the broader implications, illustrated by experiences in genomics diagnostics under standards such as FDA 21 CFR Part 11, ISO 13485, and GMP Annex 11.

The Inefficiencies and Risks of Traditional Sequential Development

Many organizations continue to structure software development in a sequential manner, akin to an assembly line in manufacturing. Requirements are defined by one group, passed to designers, then to developers, testers, and finally to those responsible for deployment. Although this approach may appear structured, it introduces fundamental inefficiencies that become especially problematic in regulated settings.

A primary issue is the idle time that arises during handoffs. Teams often wait for deliverables from previous stages, creating bottlenecks that extend project timelines significantly. In complex projects, these delays compound, turning weeks into months and hindering the ability to respond to new insights or market demands.

Context loss during these transitions compounds the problem. When knowledge moves between specialized groups, critical details—such as the rationale for design choices or awareness of subtle edge cases—frequently fail to transfer completely. This leads to misunderstandings, rework, and the accumulation of technical debt that makes systems increasingly difficult to maintain.

Documentation suffers particularly in this model. It is often treated as a separate, post-development activity, requiring teams to reconstruct events after the fact. The resulting records tend to be incomplete or inconsistent, as memories fade and priorities shift. In regulated industries, where auditors demand clear, contemporaneous proof of every decision and change, this creates ongoing anxiety and resource-intensive preparation.

The sequential structure also reinforces organizational silos. Quality and compliance teams position themselves as final gatekeepers, reviewing work produced by others. This can foster adversarial dynamics, with engineers perceiving oversight as obstructive and assurance personnel viewing development as insufficiently rigorous. Compliance thus becomes an added layer of work rather than an integrated aspect of engineering.

In fields like medical devices or pharmaceuticals, where software directly influences patient safety, these inefficiencies carry high stakes. They delay innovations that could improve outcomes and consume resources that could be directed toward scientific advancement.

How Modern Practices Generate Compliance Inherently

Contemporary methodologies offer a fundamentally different approach, one where compliance evidence arises automatically from the act of building high-quality software. At the heart of this shift is the use of distributed version control systems like Git. Every change to code is recorded with precise details: who made it, when, and why, along with links to related discussions or requirements. This creates a complete, immutable history that serves as a reliable source of truth.

Automated testing builds on this foundation. Tests execute whenever code changes, generating detailed reports on coverage, results, and any regressions. These reports provide objective validation that the software functions as intended, without requiring manual creation.

Continuous integration and delivery pipelines integrate these elements into a cohesive flow. They define and enforce the exact steps for building, testing, and deploying software, ensuring consistency across environments. Human approvals can be incorporated where necessary, but they become part of the automated process rather than separate hurdles.

The pipeline itself receives the highest level of governance. Changes to deployment logic undergo the same review as application code, recognizing that the mechanism responsible for consistency must be trustworthy.

In this ecosystem, evidence accumulates continuously and effortlessly: commit histories, test executions, pipeline runs, approval records, and deployment details, all linked and timestamped. There is no need for a parallel compliance effort; the work of engineering excellence produces the required proof.

This also transforms the role of compliance specialists. Instead of reviewing completed work, they collaborate early to design effective controls and automations. Their expertise helps prevent issues rather than detect them late.

Transformation in Practice: The Genomics Diagnostics Example

Foundation Medicine’s experience provides a concrete illustration of these principles in action. The company develops genomic tests for cancer treatment, and its software falls under FDA classification as medical devices, requiring rigorous control and traceability.

Initially operating with sequential processes and manual documentation, the organization faced the common challenges: slow releases, high administrative overhead, and stressful audits.

Tom Godden led a comprehensive shift to automated, AWS-hosted pipelines. These became the most carefully controlled components, with any modification subject to thorough review.

The outcomes were substantial. Release cycles shortened dramatically, enabling faster incorporation of new scientific knowledge into clinical tools. Defect rates decreased as automated checks identified issues early. Audits became collaborative, with inspectors able to trace production releases directly to source changes, tests, and approvals.

Compliance teams moved from policing to partnering, contributing to system design and improving overall quality. Time previously spent on documentation and audit preparation was redirected toward advancing patient care.

This case demonstrates that modern practices not only meet regulatory demands but exceed them, delivering better software faster and with less risk.

The Essential Role of Leadership in Driving Change

Implementing these changes requires strong leadership to overcome inertia and align the organization. Executives must clearly articulate the vision: compliance is not a separate goal but a natural result of building reliable software quickly.

Building a coalition of advocates across engineering and compliance creates internal momentum. Transparency, such as dashboards showing adoption progress, can harness positive competition.

Temporary parallel operations—running old and new processes side by side—provide undeniable evidence of improvement, reducing skepticism.

Reorganizing into cross-functional squads eliminates silos and aligns incentives, so that success is shared.

Leaders grant teams autonomy in how they achieve outcomes, within defined guardrails, to maintain engagement and innovation.

Long-Term Benefits and Strategic Implications

Short, focused initiatives—such as ninety-day sprints—allow steady progress without disrupting ongoing work.

Leveraging built-in telemetry for evidence archiving minimizes additional effort.

Over time, the old “compliance theater” fades, replaced by systems where pipelines enforce standards reliably and evidence flows continuously.

Organizations gain multiple advantages: faster innovation, higher quality, lower risk, and compliance that enables rather than constrains. In regulated markets, this can become a competitive differentiator, allowing leadership in both technology and responsibility.

Relevant links and hashtags

Links:

• Session Video

Lecturer

Abhijit Chakravarty, Mike Bechtel, and Michael J. Kavis
Abhijit Chakravarty is a seasoned technology leader at LogicMonitor, focusing on the intersection of artificial intelligence and infrastructure monitoring. Mike Bechtel serves as the Chief Futurist at Deloitte Consulting LLP, where he leads research into emerging technologies and their long-term impact on the enterprise. Michael J. Kavis is a Managing Director at Deloitte Consulting and a renowned expert in cloud computing and enterprise architecture, having authored multiple books on cloud transformation. Together, they represent a convergence of industry-leading monitoring solutions and strategic advisory expertise, specifically targeted at preparing global organizations for the complexities of the agentic AI era.

Abstract

As enterprise IT environments grow in scale and complexity, traditional AIOps frameworks—which primarily focused on pattern recognition and anomaly detection—are evolving into “Agentic AIOps.” This article explores the conceptual transition from systems that merely observe and alert to autonomous agents capable of reasoning, planning, and executing remediation tasks. By examining the integration of Large Language Models (LLMs) with operational telemetry, the study highlights a methodology centered on reducing “mean time to repair” (MTTR) and minimizing human intervention in repetitive incident management cycles. The analysis delves into the maturity model for agentic adoption, the necessity of rigorous data grounding, and the evolving role of the human operator in a supervised autonomous ecosystem. The findings suggest that agentic AIOps is not merely an efficiency tool but a fundamental redesign of IT governance and service reliability.

The Conceptual Evolution: From Observability to Autonomy

The IT landscape has historically progressed through distinct phases of monitoring. Early systems were reactive, relying on static thresholds to trigger alerts. This gave way to the first generation of AIOps, which utilized machine learning for event correlation and root cause analysis. However, even these advanced systems remained largely “human-in-the-loop,” where the AI identified a problem, but a person had to decide and act on the solution.

Agentic AIOps represents a paradigm shift where the AI moves from an advisor to a doer. Unlike traditional automation, which follows a rigid, pre-defined script (e.g., “if X, then do Y”), agentic systems utilize the reasoning capabilities of LLMs to handle “non-deterministic” scenarios. These agents can interpret natural language incident reports, query multiple databases to gather context, and generate a step-by-step remediation plan that adapts to the specific nuances of the failure.

Methodology: Reasoning, Tool-Use, and Grounding

The architecture of a modern agentic AIOps system, such as LogicMonitor’s “Edwin AI,” relies on three core pillars: reasoning, tool-use, and grounding.

Strategic Reasoning and Planning

The “brain” of the agent is the LLM, which processes incoming alerts through a reasoning framework—often employing the “ReAct” (Reason + Act) pattern. When an incident occurs, the agent first decomposes the problem into smaller, manageable sub-tasks. It formulates a hypothesis about the root cause and identifies the necessary information required to validate that hypothesis.

Dynamic Tool-Use

To act on its reasoning, the agent must be able to interact with the environment. This is achieved through “function calling” or tool-integration. An agent might have access to a suite of tools, including:

• Infrastructure APIs: To restart services, scale resources, or modify configurations.
• Knowledge Bases: To retrieve historical documentation or runbooks.
• Communication Platforms: To update Slack channels or create ServiceNow tickets.

The Grounding Requirement

A critical challenge in applying generative AI to IT operations is “hallucination.” To ensure the agent makes decisions based on facts rather than probability, the methodology emphasizes “grounding” via Retrieval-Augmented Generation (RAG). The system feeds the LLM real-time telemetry from LogicMonitor alongside enterprise-specific runbooks. This ensures that the agent’s reasoning is constrained by the actual state of the infrastructure and the organization’s approved operating procedures.

Implementation: The Agentic Maturity Model

Adopting agentic AIOps is not an “all-or-nothing” proposition; it follows a maturity curve that balances autonomy with risk management.

1. Assisted Mode: The agent acts as a co-pilot, summarizing incidents and suggesting remediation steps to a human operator for approval.
2. Supervised Autonomy: The agent executes low-risk tasks autonomously (e.g., clearing disk space) while requiring permission for higher-impact changes (e.g., rebooting a production database).
3. Full Autonomy: The system operates independently within strictly defined guardrails, only involving humans for unprecedented or catastrophic failures.

This tiered approach allows organizations to build trust in the agent’s decision-making while gradually reducing the cognitive load on Site Reliability Engineering (SRE) teams.

Consequences for Enterprise IT and the Workforce

The shift toward agentic operations necessitates a change in the mindset of IT leadership. The focus moves from “managing tasks” to “managing outcomes.” The role of the human operator evolves from a manual troubleshooter to a “curator of intent.” Engineers will spend less time reacting to pagers and more time defining the policies, objectives, and constraints within which the agents must operate.

Furthermore, the integration of LogicMonitor with platforms like Worldwide Technologies (WWT) and NTT highlights a growing ecosystem of partnerships designed to provide the testing grounds (labs and POVs) necessary for enterprises to validate these autonomous workflows. The ultimate consequence is a significant reduction in noise—where thousands of alerts are distilled into a handful of actionable, or even self-resolving, insights.

Conclusion

Agentic AIOps marks the beginning of the autonomous enterprise. By combining the deep visibility of infrastructure monitoring with the sophisticated reasoning of generative AI, organizations can finally address the scale and speed requirements of modern digital services. While the technology is revolutionary, its success remains rooted in the fundamentals: high-quality data, clear governance, and a phased approach to building autonomous trust.

Links:

• AWS re:Invent 2025 – Agentic AIOps: How LogicMonitor Prepares Enterprises for AI-Driven IT (AIM232)
• LogicMonitor Official Website
• Deloitte Consulting – Emerging Technology Research
• Worldwide Technology (WWT) – LogicMonitor Partnership

Lecturers

Resh Desai, Zach Miller, and Jake Farrell presented this session. Resh Desai works as a solutions architect at Amazon Web Services, driving forward developments in secrets management. Zach Miller is a Senior Worldwide Security Specialist Solutions Architect at AWS, specializing in cryptography, keys, secrets, and certificates. Jake Farrell serves as Senior Director of Engineering at Acquia, which provides open digital experience platforms.

Abstract

The presentation sheds light on the evolution of secrets management, highlighting AWS Secrets Manager as a central tool for handling the complete lifecycle of sensitive credentials. It weighs the advantages and drawbacks of centralized versus decentralized approaches, outlines key capabilities like encryption, automated rotation, cross-region replication, and high-volume retrieval, and details Acquia’s comprehensive migration efforts. In addition, it explores strategies for multi-tenant separation, patterns for Kubernetes integration, future synergies with agentic AI, and the latest service improvements that support third-party rotations and easier container-based deployments.

Core Functionalities of AWS Secrets Manager

AWS Secrets Manager provides a purpose-built service dedicated to managing the entire lifecycle of application secrets, database credentials, and API keys, setting it apart from IAM for identity management or KMS for cryptographic operations. By design, every secret undergoes envelope encryption with AWS-managed KMS keys, though users can opt for customer-managed keys to support scenarios such as cross-account sharing.

This setup integrates smoothly with CloudTrail to deliver thorough auditing of all actions, from creation and modification to deletion. Automation through Lambda enables rotation schedules that align precisely with enterprise policies, whether set at 30 or 90 days. For resilience, multi-region replication ensures secrets remain available during regional failovers. The service handles up to 10,000 transactions per second for retrieval, further enhanced by an open-source agent that implements caching with configurable time-to-live periods, thereby improving both efficiency and the overall developer experience.

Together, these features create a secure and traceable environment that integrates seamlessly with the wider AWS security landscape.

Navigating Centralized and Decentralized Deployment Choices

When designing secrets storage, architects must decide between consolidating secrets in a single dedicated account or distributing them closer to the applications that consume them. Centralized configurations often resonate with organizations in regulated sectors, as they allow for standardized practices in naming, tagging, and permission enforcement—typically achieved through enforced CI/CD pipelines or bespoke abstraction layers. Such consistency bolsters monitoring and control across the enterprise, although it requires significant initial investment in development and can introduce latency when adopting newly released capabilities.

On the other hand, a decentralized model empowers individual application teams to manage secrets directly via consoles or SDKs, offering greater adaptability to unique requirements. This approach streamlines onboarding and accommodates specialized needs more naturally, but it calls for robust supplementary governance to ensure alignment with broader standards.

In practice, the ideal configuration depends on factors like secret creation processes, ongoing management, replication demands, access patterns, and visibility needs, reflecting insights gathered from diverse customer experiences rather than a one-size-fits-all rule.

Acquia’s Migration Experience and Multi-Tenant Architecture

Acquia maintains oversight of over 300,000 distinct secret paths distributed across multiple AWS accounts, supporting millions of daily ephemeral pod instances and tens of thousands of hourly API interactions. Moving away from older systems required careful categorization of secrets into groups such as customer-supplied elements (including third-party tokens and environment variables), internal service communications, and emerging hybrid forms suited to AI agents.

To manage this complexity, Acquia developed a custom fronting API that applies type-specific rules for validation, scoping, and lifecycle policies, such as mandatory rotation or timed expiry. Rigorous least-privilege principles ensure complete separation between platform operations and customer data. For delivery into runtime environments, the organization relies on open-source components like the External Secrets Operator combined with AWS CSI drivers, which synchronize and inject secrets into Kubernetes as variables, configuration templates, or command-line flags. Strategic caching layers further reduce direct API calls, delivering noticeable gains in speed and expense control.

Through this disciplined, layered framework, Acquia achieves robust multi-tenancy while addressing gaps that IAM alone cannot fully cover in interconnected service scenarios.

Future Directions in Agentic AI Collaboration

Looking ahead, Acquia’s designs feature an AI gateway that provides a unified point for observing model invocations routed through Amazon Bedrock, complemented by a standardized factory for quickly provisioning secure agents. By embedding Secrets Manager deeply, the platform enables on-demand injection of properly scoped credentials, allowing smooth evolution alongside emerging AI features without compromising protective measures.

This ongoing partnership with AWS has yielded tangible benefits in operational streamlining, lower maintenance burdens, and enhanced overall performance.

Latest Service Developments and Their Wider Impact

Innovations continue to simplify adoption in container environments, with EKS add-ons now automating the installation and configuration of CSI drivers. The introduction of managed external secrets brings one-click rotation capabilities to external providers like Salesforce, removing the need for custom scripting and eliminating risks of desynchronization.

Native integrations now span more than 55 AWS services, making secret management largely invisible to end users. These progresses reduce entry barriers to advanced security practices, enabling teams to concentrate on innovation even as autonomous systems increase demands on privilege management.

In essence, effective secrets governance forms the bedrock of durable, expandable systems vital for both current operations and forthcoming intelligent workloads.

Links:

• Lecture Video
• Jake Farrell on LinkedIn
• Acquia Official Website

Lecturer

Elizabeth Fuentes is a Senior Developer Advocate at Amazon Web Services (AWS), specializing in the intersection of Artificial Intelligence and DevOps practices. With extensive experience in cloud architecture and software engineering, Elizabeth focuses on how Generative AI can streamline complex CI/CD pipelines and enhance Site Reliability Engineering (SRE). She is a key contributor to AWS educational initiatives, having co-developed advanced courses on AI-driven automation. Joining her is Laas Alina, a software architect and open-source enthusiast who focuses on implementing multi-agent systems and the Model Context Protocol (MCP) to solve observability challenges at scale.

Abstract

As software systems grow increasingly distributed and complex, traditional observability—centered on manual log analysis and reactive dashboards—is becoming insufficient. This article explores the paradigm shift toward AI-driven observability, where Generative AI serves not just as a query tool, but as an active participant in failure detection, correlation, and resolution. By leveraging Amazon Bedrock and Amazon Q, organizations can transition from “reactive” to “predictive” DevOps. The discussion analyzes the methodology of building AI agents that simulate architectural stress, automatically explain multi-layered failures, and provide traceable, actionable recommendations. We examine the implementation of the Model Context Protocol (MCP) in establishing sophisticated multi-agent systems (MAS) that transform raw data into contextual understanding, ultimately reducing the Mean Time to Resolution (MTTR) and enhancing systemic resilience.

The Evolution of Observability: From Metrics to Contextual Understanding

The traditional pillars of observability—metrics, logs, and traces—provide the “what” of a system’s state but often fail to provide the “why” in real-time. In high-velocity DevOps environments, the sheer volume of telemetry data can overwhelm human operators, leading to “alert fatigue” and delayed responses to critical incidents. Elizabeth posits that the integration of Generative AI marks the fourth pillar of observability: Contextual Intelligence. This evolution moves the industry beyond simple threshold-based monitoring toward systems that understand the semantic relationship between a failed deployment, a spike in latency, and a specific line of code.

By utilizing Large Language Models (LLMs) through Amazon Bedrock, DevOps teams can ingest vast amounts of unstructured log data and receive summaries that highlight anomalies that might be missed by traditional regex-based filters. The methodology involves training the AI to recognize “normal” operational patterns and identifying deviations not just by value, but by the intent of the system’s behavior. This contextual layer allows for a more nuanced interpretation of system health, where the AI can distinguish between a benign resource spike and a precursor to a cascading failure.

Architecting AI Agents for Predictive Troubleshooting

The transition to AI-driven observability is characterized by the deployment of “Micro-agents”—specialized AI entities designed to handle specific segments of the DevOps lifecycle. These agents operate within a Multi-Agent System (MAS), where they collaborate to solve complex incidents. For instance, a “Monitoring Agent” might detect a performance degradation and immediately trigger a “Diagnosis Agent” to correlate the event with recent CI/CD pipeline changes.

Elizabeth and Laas Alina emphasize the importance of the Model Context Protocol (MCP) in this architecture. MCP acts as the communication backbone, allowing agents to share context without losing the “lineage” of a decision. When an AI agent recommends a specific architectural change or a rollback, it must provide clear traceability. This is crucial for maintaining trust in automated systems. The agents do not operate in a vacuum; they interact with tools like Amazon Q to provide developers with instant explanations of failures directly within their Integrated Development Environment (IDE) or chat interface.

// Example of an AI-driven Observability Agent Configuration
agent:
  name: "IncidentDiagnosticAgent"
  provider: "AmazonBedrock"
  model: "claude-3-sonnet"
  capabilities:
    - log_analysis
    - metric_correlation
    - trace_summarization
  mcp_config:
    protocol_version: "1.0"
    shared_context: "deployment_metadata"
  safety_guardrails:
    - max_token_usage: 4000
    - human_in_the_loop_required: true

Transforming CI/CD through Generative AI and Simulation

Beyond reactive troubleshooting, AI-driven observability empowers proactive system design. One of the most innovative concepts discussed is the use of AI agents to simulate “stress-test” scenarios within a digital twin of the production environment. These agents can intentionally inject failures—similar to Chaos Engineering—and then observe how the observability stack responds. This creates a feedback loop where the AI helps engineers identify “blind spots” in their monitoring before a real incident occurs.

Furthermore, Generative AI transforms the CI/CD pipeline by automatically generating “failure explanations.” Instead of a developer sifting through a 5,000-line build log, Amazon Q can provide a concise summary: “The build failed because the new database schema in commit X is incompatible with the connection pool settings in environment Y.” This level of automated insight accelerates the “inner loop” of development, allowing engineers to focus on innovation rather than infrastructure archeology.

The Human-AI Partnership: Strategic Implications

A common concern in the industry is the replacement of human engineers by AI. However, Elizabeth argues that the future belongs to the “augmented engineer.” AI is a force multiplier that automates the repetitive, “drudge work” of observability—log parsing and initial triage—allowing human experts to focus on high-level strategy and complex architectural decisions. The goal is to transform teams from being “reactive” (fighting fires) to “proactive” (preventing fires).

Implementing these systems requires a cultural shift toward AI-literacy within DevOps teams. Organizations must establish safety guardrails to ensure that AI-driven recommendations are validated and that automated actions (like auto-remediation) have clear rollback paths. By embracing AI as a strategic tool, DevOps and SRE teams can achieve a level of operational excellence that was previously unattainable, ensuring that as systems grow in scale, their reliability grows in parallel.

Links:

• Amazon Bedrock Service Page
• Amazon Q Developer Information
• AWS DevOps Solutions
• Model Context Protocol (MCP) Specification

Lecturer

Mortaza Chowri is the Head of Product Management for the AWS Transform team, where he leads the development of next-generation tools for complex workload migration. He is an expert in leveraging generative AI to automate technical debt reduction for large-scale enterprises. Joining him are Alexi and Ravi, who serve as senior architects within the AWS Transform division, specializing in agentic AI implementation and the creation of composable system frameworks. The session also features strategic insights from the leadership team at Capgemini, who collaborate with AWS to deliver industry-specific modernization solutions for global banking and automotive clients.

Abstract

Enterprise modernization is frequently paralyzed by the extreme complexity of legacy systems, particularly decades-old mainframes and aging Windows-bound .NET applications. This article explores the innovative framework of AWS Transform, a centralized service that utilizes “Agentic AI” to automate and streamline the migration process. The methodology centers on the concept of composability, which allows AWS partners to integrate their proprietary industry knowledge and specialized tools with foundational AI agents. By utilizing a sophisticated chat-based interface and automated business rule extraction, the platform enables a seamless transition from legacy COBOL and .NET Framework 4.x to modern, cloud-native architectures. The analysis demonstrates how these composable agents create a continuous feedback loop that significantly reduces manual effort, improves documentation, and ensures business logic remains intact during high-risk migrations.

Context: The Burden of Technical Debt and Knowledge Atrophy

Many of the world’s most critical systems, particularly in finance and manufacturing, are still dependent on infrastructure built in the late 20th century. These legacy environments present three primary obstacles that prevent organizations from achieving modern agility. First, knowledge atrophy has become a critical risk, as the original architects of these mainframe systems have often retired, leaving behind “black box” applications that lack contemporary documentation. Second, the technical debt associated with older languages like COBOL is immense, as these systems were never designed to leverage modern cloud features such as serverless compute or elastic auto-scaling.

Third, the mission-critical nature of these systems creates a state of risk aversion, where the fear of breaking a core business process during a manual rewrite often leads to stagnation. AWS Transform was specifically developed to break this cycle of inertia. By providing a unified experience that integrates discovery, assessment, and modernization into a single platform, AWS allows enterprises to view their legacy code as an asset to be reimagined rather than a liability to be feared.

Methodology: Agentic AI and the Composable Framework

The core technical innovation of AWS Transform is the transition from static point solutions to a dynamic, “unified experience” powered by specialized AI agents. These agents are designed to perform complex technical tasks with a level of autonomy that far exceeds traditional automation scripts. The methodology is built upon several key pillars of agentic behavior. Discovery agents are tasked with automatically mapping technical artifacts, such as physical servers and complex database schemas, to their optimal cloud-native equivalents.

Modernization agents, specifically those tuned for mainframe environments, perform the difficult work of extracting business rules from legacy code. This process generates comprehensive documentation that allows current engineers to “comprehend” the underlying logic of systems they did not build. The most transformative aspect of this methodology is its composability for partners. AWS provides the foundational intelligence and large language models, while partners such as Capgemini can “compose” these with their own specialized knowledge bases and custom transformation rules. This enables the creation of industry-specific agents, such as a modernization assistant specifically optimized for banking regulations or complex automotive production logic.

Technical Analysis of Mainframe Rule Extraction

The implementation of these agents in real-world scenarios, particularly through the collaboration with Capgemini, highlights a sophisticated “forward engineering” approach. In this workflow, the AI agents first scan the legacy code to identify core business logic and immutable rules. This extraction phase is critical because it ensures that while the code is updated, the essential business functions remain perfectly intact. Following extraction, the reimagination phase begins, where these rules are integrated into a modern architecture that meets cloud-native standards for security and performance.

Practitioners interact with these systems through a chat experience within the AWS Transform interface, allowing them to query both the AI agents and integrated domain experts directly. This interaction model democratizes the modernization process, making it accessible to developers who may not have expertise in COBOL but are proficient in modern languages like Java or Python. The platform serves as a bridge, translating the “what” of legacy business logic into the “how” of modern cloud execution.

Outcomes: Efficiency, Consistency, and Continuous Learning

The deployment of composable AI agents has fundamentally altered the economics and speed of enterprise modernization. By automating the most labor-intensive parts of code comprehension and translation, organizations have reported a reduction in manual effort by as much as 80%. This allows teams to focus on high-value innovation rather than the repetitive task of line-by-line code migration. Furthermore, the platform ensures architectural consistency across a large organization, preventing the fragmentation that often occurs when different teams use varying migration tools.

One of the most significant consequences of this approach is the continuous improvement of the agents themselves. Every modernization task performed through the platform provides feedback data that enhances the underlying AI models. As these agents encounter more diverse enterprise environments, their ability to handle edge cases and complex business rules grows exponentially. This creates a virtuous cycle where each successful migration makes the next one faster and more reliable, effectively solving the problem of knowledge atrophy for the long term.

Conclusion

The shift toward agentic AI and composable architectures represents a milestone in the evolution of enterprise IT. AWS Transform provides a robust framework that allows organizations to tackle their most daunting legacy challenges with a level of confidence and speed that was previously impossible. By allowing partners to integrate their unique industry expertise into a centralized AI system, AWS has created a scalable ecosystem that transforms modernization from a risky, multi-year endeavor into a manageable and continuous strategic process.

Links:

• AWS Transform Service Overview
• Capgemini Mainframe Modernization
• AWS Partner Central
• Watch the Technical Deep Dive

Lecturer

Aditi is a Senior Product Manager for Amazon FSx at Amazon Web Services (AWS). With years of experience working directly with customers on high-performance workloads, she focuses on pushing the technical boundaries of what is possible with cloud storage to meet the demands of modern compute-intensive applications.

Abstract

This article examines the critical role of high-performance storage in supporting modern AI/ML, analytics, and High-Performance Computing (HPC) workloads. As organizations scale their compute resources—incorporating hundreds or thousands of CPU and GPU cores—storage often becomes the primary bottleneck, preventing linear performance scaling. We explore the technical architectures of Amazon FSx and Amazon S3, focusing on how these services address the needs of both “lift-and-shift” file-based applications and “cloud-native” S3-based data lakes. By analyzing customer use cases in genomics, media rendering, and large language model (LLM) training, we detail the methodologies for achieving peak performance at scale.

The Storage Bottleneck in Compute-Intensive Workloads

Modern high-performance workloads are characterized by their extreme reliance on massive datasets and high-core-count compute clusters. In an ideal cloud environment, adding more compute resources should lead to a proportional increase in work completed—a concept known as linear scaling. However, traditional storage solutions often fail to keep pace with the throughput demands of these clusters, leading to a performance plateau.

When storage becomes the bottleneck, compute instances sit underutilized as they compete for access to the same data store. This is particularly detrimental given that 90% to 95% of the expenditure for these workloads is typically allocated to compute resources. Consequently, an inefficient storage layer not only extends the time to insight but also significantly increases the total cost of ownership (TCO). To avoid this, storage must be architected to scale linearly alongside compute.

Navigating the Path to the Cloud: File Systems vs. Object Storage

Organizations generally approach high-performance storage on AWS from two distinct backgrounds: those with long-standing on-premises file-based workflows and those who have built native cloud applications around object storage.

The Persistence of File-Based Architectures

Despite the rise of object storage, file systems remain the preferred interface for many researchers and developers due to three primary factors: Familiar Interface: The intuitive nature of files and directories simplifies complex data management for data scientists and developers.
* Granular Permissions: File systems provide robust POSIX permissions, allowing for fine-grained control over which users can read, write, or execute specific files.
* Consistent Data Access:* For workloads where multiple users or compute nodes access the same data simultaneously, the strong consistency of file systems ensures that all parties see the most recent data updates.

Amazon FSx for High-Performance File Access

Amazon FSx addresses these needs by providing fully managed file systems that offer the performance of local storage with the scalability of the cloud. For “lift-and-shift” scenarios, FSx allows organizations to move their existing HPC and AI/ML pipelines to AWS without refactoring their applications.

Accelerating Generative AI and ML Workloads

The emergence of generative AI has placed a renewed emphasis on data strategy. Whether an organization is building a model from scratch or fine-tuning a foundational model, the quality and accessibility of its proprietary data are the primary differentiators.

Retrieval Augmented Generation (RAG)

To move beyond generic AI responses and reduce hallucinations, many organizations are implementing Retrieval Augmented Generation (RAG). RAG allows foundational models to access evolving, large-scale data lakes without requiring the data to be manually loaded into a prompt.

The RAG methodology involves:
1. Vectorization: Converting organizational data into vectors—numeric representations that capture semantic meaning.
2. Semantic Search: Using spatial similarity to compare a query vector against the data lake’s vectors to find the most relevant information.
3. Augmentation: Feeding the retrieved context back into the model to generate a more accurate and business-specific response.

Ingestion and Data Strategy with Amazon S3

Amazon S3 serves as the foundational data lake for these AI workflows due to its cost-effectiveness and virtually unlimited scalability. Organizations typically utilize two ingestion patterns:
* Batch Ingestion: Suitable for static or infrequently changing data such as historical records and product catalogs.
* Real-Time Ingestion: Essential for agentic workflows where AI models must respond to the latest available information.

Modernizing Self-Managed Databases with Amazon FSx

While fully managed services like Amazon RDS are popular, certain business and technical requirements drive organizations toward self-managed database architectures on AWS.

Drivers for Self-Managed Databases

Organizations choose to self-manage databases like Oracle, SQL Server, or SAP HANA for several reasons:
* Granular Control: The ability to choose specific versions of the database engine and the underlying operating system.
* Custom Protection Policies: Implementing specific backup intervals and recovery procedures that may not be available in managed services.
* High Resilience: Scaling databases across multiple Availability Zones or regions with custom failover configurations.

Optimization through Storage Features

A common oversight in database deployment is the potential for the storage layer to add significant value beyond simple data persistence. Amazon FSx file systems (including FSx for NetApp ONTAP, OpenZFS, and Windows File Server) enable features like:
* Snapshots and Cloning: Facilitating rapid testing and database upgrades by creating near-instantaneous copies of production environments.
* Performance Tuning: Choosing the right FSx service can significantly optimize the TCO and performance of database environments, particularly for high-transaction workloads.

Conclusion

As compute power continues to expand, the storage layer must evolve from a passive repository into a high-performance engine. By leveraging Amazon FSx and S3, organizations can eliminate storage bottlenecks, enabling their most demanding AI, HPC, and database workloads to scale linearly and cost-effectively in the cloud.

Links:

• Amazon FSx Product Page
• Amazon S3 Product Page
• AWS re:Invent 2025 – High-performance storage for AI/ML, analytics, and HPC workloads (STG336)
• AWS re:Invent 2025 – Accelerate gen AI and ML workloads with AWS storage (STG201)
• AWS re:Invent 2025 – Improve self-managed database performance and agility with Amazon FSx (STG337)

Lecturer

Danny Leybovich is a Product Lead at Anthropic, dedicated to building the infrastructure and models that empower the next generation of AI developers. With a focus on high-reasoning models and developer experience, Danny has been instrumental in the launch of Claude Code and the evolution of Anthropic’s agentic framework. His work centers on the practical realities of moving AI from “cool demo” to “reliable autonomous system.”

Abstract

2025 marked a pivotal shift in the artificial intelligence landscape: the transition from interactive chatbots to autonomous AI agents. This article synthesizes the key discoveries made by Anthropic during this transformative year, particularly through the development of Claude Code and the deployment of the Opus 4.5 frontier model. It explores the “agentic architecture” required for long-horizon autonomous work, emphasizing the critical roles of context engineering and skill acquisition. The analysis examines the shift toward “agent-first” workflows, where the model is no longer a passive assistant but an active participant with multi-hour reasoning capabilities. By investigating patterns of reliability and the evolution of AI engineering practices, this article provides a roadmap for the next wave of agentic AI.

The Shift to Agent-First Workflows

In the early stages of generative AI, the predominant interaction pattern was the “chat” interface—a stateless exchange where a human provided a prompt and the model provided a response. 2025 saw the obsolescence of this limited model in favor of “agent-first” workflows. In an agentic architecture, the model is granted the autonomy to use tools, manage its own memory, and pursue goals over extended periods—sometimes lasting hours.

This shift changes the fundamental role of the developer. Instead of engineering a single prompt, the developer now engineers an environment in which an agent can succeed. This involves defining clear objectives, providing access to necessary APIs, and implementing “guardrails” that ensure the agent remains on track during autonomous loops. The rise of “Claude Code”—an agent that can autonomously file GitHub issues and build applications—serves as the flagship example of this transition.

Advanced Context Engineering: Beyond the Context Window

While early AI discussions focused heavily on the size of the “context window,” Anthropic’s experience in 2025 highlighted that quality of context is far more important than raw volume. Context engineering is the practice of strategically selecting and formatting the information provided to the model to maximize reasoning accuracy and minimize hallucinations.

Effective context engineering for agents involves:

1. State Management: Keeping track of what the agent has already done and what remains to be accomplished.
2. Relevant Document Retrieval: Using RAG (Retrieval-Augmented Generation) to pull only the most pertinent information into the reasoning loop.
3. Semantic Chunking: Ensuring that the information is presented in a way that the model can easily digest and connect to other data points.

By focusing on context engineering, developers can enable agents to maintain “state” across long horizons, allowing for complex tasks like refactoring an entire codebase or conducting multi-step regulatory research without losing the thread of the original objective.

Tool Construction and Skill Acquisition

A primary differentiator for AI agents is their ability to interact with the world through tools. In 2025, Anthropic refined the methodology for “teaching” agents new skills through tool construction. A “skill” is essentially a well-defined tool—such as a Python interpreter, a SQL query engine, or a web search function—that the model knows how and when to invoke.

The engineering challenge lies in creating “reliable” tools. If a tool’s output is ambiguous or inconsistent, the agent’s reasoning loop will break. Therefore, tool writing has become a core discipline within AI engineering. Developers must create tools that provide “structured feedback” to the model, allowing the agent to self-correct if a tool call fails. This iterative loop of tool use and self-correction is what allows agents to handle “long-horizon” tasks that were previously impossible for LLMs.

Analyzing the Performance of Opus 4.5

The release of the Opus 4.5 frontier model provided the reasoning “horsepower” necessary for the agentic revolution. Unlike smaller models that might prioritize speed, Opus 4.5 is optimized for high-reasoning tasks. Its performance characteristics include a significant reduction in “logic drift”—the tendency of a model to lose focus during long sequences of thought.

In production environments, Opus 4.5 has demonstrated an ability to navigate “deep” decision trees. For example, when tasked with finding a bug in a complex software system, the model can formulate a hypothesis, write a test to prove it, analyze the test results, and then iteratively refine its approach. This capability for “autonomous debugging” is a hallmark of the newest wave of AI, where the model’s intelligence is leveraged not just for text generation, but for problem-solving in dynamic environments.

Code Sample: Defining a Secure Tool for Claude Agentic Workflows

'''
 Conceptual tool definition for an Anthropic Agent
 This tool allows the agent to safely query a database
''' 

def get_tool_definition():
    return {
        "name": "query_database",
        "description": "Allows the agent to execute read-only SQL queries to retrieve customer data.",
        "input_schema": {
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "The SQL query to execute. Must be read-only."
                },
                "max_rows": {
                    "type": "integer",
                    "default": 10
                }
            },
            "required": ["query"]
        }
    }

'''
This structure enables the model to 'reason' about when it needs 
to fetch data versus when it can rely on its internal knowledge.
'''

Long-Horizon Autonomous Reliability

The final frontier explored in 2025 was the challenge of reliability. For an agent to be truly useful, it must be able to work for hours without human intervention. This requires a robust infrastructure that can handle model timeouts, API failures, and unexpected edge cases.

Anthropic’s research into long-horizon agents suggests that reliability is not a feature of the model alone, but a result of the model-infrastructure synergy. This includes:

• Checkpointing: Periodically saving the agent’s state so it can resume after a failure.
• Human-in-the-Loop (HITL) Triggers: Designing the agent to “ask for help” when it reaches a confidence threshold that is too low.
• Verification Loops: Implementing a secondary model or a deterministic process to verify the agent’s output before it is committed.

These patterns are what define the current state of the art in AI engineering, moving the industry toward a future where agents are trusted partners in the enterprise.

Conclusion

The lessons of 2025 are clear: the future of AI belongs to autonomous agents. By mastering the disciplines of context engineering, tool construction, and long-horizon reliability, developers can leverage models like Claude Opus 4.5 to solve problems of unprecedented complexity. As we look ahead, the trends established this year—particularly the move toward agent-first workflows—will define the next decade of technological innovation. The demo era is over; the production era of agentic AI has begun.

Links:

• Anthropic Official Website
• Claude Model Documentation
• Anthropic on AWS Bedrock

Lecturer

The session is delivered by product managers from Amazon Web Services who oversee the development and roadmap of AWS CloudFormation and the AWS Cloud Development Kit.

Abstract

This article provides an exhaustive and detailed retrospective on the notable progress achieved throughout the past year in AWS infrastructure as code services, with particular emphasis on both AWS CloudFormation and the AWS Cloud Development Kit (CDK). It meticulously examines a range of enhancements, including improved validation mechanisms, clearer error diagnostics, expanded construct libraries, seamless integration with artificial intelligence assistance through Model Context Protocol servers, and advanced troubleshooting utilities. The discussion analyzes how these collective innovations substantially elevate deployment reliability, enhance developer productivity, and introduce greater intelligence into infrastructure management practices for organizations of all scales.

The Critical and Enduring Role of Infrastructure as Code in Modern Cloud Architectures

Infrastructure as code has firmly established itself as an indispensable discipline for enterprises striving to achieve consistency, traceability, and accelerated iteration in their cloud operations. AWS CloudFormation offers a robust declarative approach, allowing practitioners to define resources through structured templates in JSON or YAML formats, thereby guaranteeing identical provisioning outcomes across development, staging, and production environments.

Complementing this, the AWS Cloud Development Kit empowers developers with programmatic flexibility, enabling infrastructure definition in familiar programming languages while automatically generating underlying CloudFormation templates. This duality accommodates diverse team preferences and skill sets.

The advancements introduced over the year have strategically bridged these paradigms, delivering unified capabilities that address contemporary challenges related to scale, complexity, and the evolving demands of developer experience in dynamic cloud ecosystems.

Significant Refinements Enhancing AWS CloudFormation Reliability and Practitioner Usability

AWS CloudFormation has benefited from meaningful improvements in change set validation processes, enhanced clarity in error messaging, and more intuitive management of deployment workflows. These refinements work collectively to substantially reduce the frequency of failed deployments by surfacing potential conflicts, resource constraints, or configuration incompatibilities earlier in the provisioning lifecycle.

Furthermore, the introduction of server-side APIs now enables programmatic pre-validation of proposed changes, allowing integration into continuous integration pipelines for automated safeguards that prevent runtime disruptions and promote greater confidence in infrastructure updates.

Substantial Growth and Maturation Within the AWS Cloud Development Kit Ecosystem

The AWS Cloud Development Kit has experienced considerable expansion in supported programming languages and the availability of high-level constructs. Numerous libraries, both community-contributed and AWS-maintained, have progressed from experimental developer preview stages to full general availability, covering an extensive array of common architectural patterns across networking, security, serverless computing, and data processing domains.

This maturation process provides developers with higher-level abstractions that encapsulate established best practices, thereby significantly reducing the amount of boilerplate code required and promoting greater architectural consistency across distributed teams.

Transformative Integration of Artificial Intelligence Assistance Through Model Context Protocol Servers

One of the most pivotal innovations involves the creation of specialized Model Context Protocol servers tailored specifically for CDK and CloudFormation contexts. These servers curate and expose AWS-specific expertise—including recommended practices, construct libraries at various maturity levels, and detailed cloud context information—directly to artificial intelligence-powered coding assistants.

As a result, developers receive highly contextually relevant suggestions that align precisely with AWS service conventions and idioms, dramatically accelerating the creation of secure, efficient, and idiomatic implementations while substantially lowering the cognitive burden associated with recalling intricate service details.

Strengthening Troubleshooting and Validation Tooling for Proactive Issue Resolution

New diagnostic capabilities encompass server-side APIs designed for interrogating deployment states and identifying root causes of issues, complemented by local static analysis utilities that perform early detection of syntax errors within CDK source code.

These tools operate across both programmatic CDK definitions and the generated CloudFormation templates, enabling practitioners to identify and resolve configuration problems well before they manifest during actual deployments.

Community-Driven Construct Libraries and Enhanced Cloud Context Integration

The ecosystem continues to benefit from active contributions spanning AWS internal teams and external community participants, with constructs systematically progressing through alpha evaluation and eventual general availability phases.

Additional cloud context features further enrich artificial intelligence interactions by providing service-specific insights and recommendations.

Practitioners are strongly encouraged to explore dedicated workshops that offer guided paths for understanding and implementing MCP server integration in real-world scenarios.

Measurable Organizational Benefits and Strategic Adoption Considerations

These multifaceted improvements collectively lower entry barriers for effective infrastructure management while delivering tangible advantages. Development teams realize enhanced confidence in deployment outcomes, accelerated onboarding for new members, and improved adherence to evolving architectural standards across projects.

The incorporation of artificial intelligence guidance represents a fundamental paradigm shift toward more intelligent, assisted development experiences that amplify human expertise rather than seeking to replace it.

Looking Toward the Future of Intelligent Infrastructure Orchestration

Continued investment in these areas clearly signals an ongoing commitment to deepening the convergence between programmatic expressiveness and declarative safety, increasingly augmented by artificial intelligence capabilities that guide practitioners toward optimal architectural outcomes.

Organizations that fully leverage these evolving tools position themselves advantageously for sustained operational excellence amid the accelerating complexity of modern cloud environments.

Links:

• Lecture Video

Lecturer

Joshua Smith is a Senior Solutions Architect at Amazon Web Services (AWS), specializing in financial services. He collaborates closely with major institutions to design scalable, secure cloud architectures.
Vara Maharivan serves as Director of Machine Learning and Artificial Intelligence at Coinbase, leading the company’s efforts to integrate advanced AI and machine learning capabilities across its cryptocurrency platform.

Abstract

This session examines how Coinbase, a leading cryptocurrency exchange, has deployed a unified generative AI platform built on Amazon Bedrock to transform three critical operational domains: customer support, regulatory compliance, and internal developer productivity. The presentation details the architectural approach, key AWS services leveraged, real-world performance metrics, and the strategic roadmap ahead. By combining retrieval-augmented generation (RAG), tool execution, and domain-specific agents, Coinbase has achieved substantial automation, cost efficiencies, and enhanced user experiences while maintaining rigorous security and compliance standards.

The Evolution of Generative AI in Financial Services

Joshua Smith opened the discussion by contextualizing the rapid maturation of generative AI within financial services. In 2023, early adoption centered on foundational concerns such as data trust and secure retrieval mechanisms. By 2024, the introduction of Amazon Bedrock enabled broader experimentation in areas like customer support, with focus shifting toward scalability, granular access controls, and integration with existing enterprise tools. Entering 2025, the landscape has progressed toward fully agentic, multi-agent systems capable of autonomously orchestrating complex workflows.

Smith emphasized that the primary challenge is no longer prototyping conversational interfaces but rather re-engineering entire business processes to deliver measurable impact on key performance indicators. This shift demands robust infrastructure, advanced security primitives, and operational frameworks tailored for agentic workloads.

AWS Services Enabling Production-Grade Agentic AI

Central to the discussion was Amazon Bedrock, a fully managed service providing access to leading foundation models through a unified API. Bedrock supports private model customization, guardrails for safety, cost-latency optimization, and, notably, Agent Core—a suite of capabilities designed to operationalize agents at scale.

Agent Core addresses critical production gaps: a serverless runtime supporting long-running multimodal agents (up to eight hours), checkpointing and recovery, identity management compatible with existing providers, secure token vaults, shared and private memory, tool discovery with fine-grained controls, and centralized observability combining logs, traces, and metrics. These components collectively mitigate risks highlighted in industry reports, such as escalating costs, unclear value, and insufficient security, which threaten the viability of agentic initiatives.

Coinbase’s Strategic Vision for AI Integration

Vara Maharivan outlined Coinbase’s mission to increase economic freedom through a trusted global cryptocurrency platform. The company rests on three pillars: building trust via top-tier security, enhancing accessibility through intuitive experiences, and scaling operations efficiently across more than 100 countries.

AI and machine learning have long underpinned fraud detection, risk assessment, personalization, and infrastructure scaling at Coinbase. Recent innovations include graph neural network-based risk scoring for blockchain addresses, ERC-20 scam token detection combining smart contract auditing with ML, and predictive scaling models to handle market volatility.

With the advent of large language models, Coinbase identified three high-impact generative AI domains: customer support automation, compliance process acceleration, and developer productivity enhancement.

Transforming Customer Support with Agentic Workflows

Crypto markets exhibit extreme volatility, driving unpredictable spikes in user inquiries that challenge traditional human-staffed support models. Coinbase addressed this through a unified generative AI platform granting fluid access to models and internal data via standardized interfaces.

The architecture features a virtual assistant handling routine interactions autonomously and an agent-assist tool empowering human representatives. The virtual assistant resolves straightforward cases end-to-end, while the assistive tool synthesizes real-time information from knowledge bases and tools, providing agents with contextual summaries, suggested responses, and multilingual capabilities.

Results demonstrate significant impact: approximately 65% of customer contacts are now automated, yielding nearly five million annualized employee-hour savings. Automated cases resolve in under ten minutes—contrasting sharply with up to forty minutes for human-handled escalations—dramatically improving customer satisfaction and operational efficiency.

Streamlining Compliance through AI-Augmented Investigations

Regulatory compliance in financial services demands rigorous processes such as KYC, KYB, and transaction monitoring. These workflows are labor-intensive, require exhaustive explainability, and must adapt to diverse jurisdictional requirements.

Coinbase augmented traditional ML-based risk detection models (deployed via Anyscale on AWS EKS) with generative AI. A compliance-assist tool aggregates data from internal systems and open-source intelligence, producing narrative summaries and risk signals for human reviewers.

At the core lies an autoresolution engine orchestrating holistic reviews. Upon a high-risk alert, the engine coordinates data synthesis, automated actions, human-in-the-loop feedback, and customer information requests. Final decisions—such as filing Suspicious Activity Reports—remain with human compliance officers, preserving accountability while accelerating throughput and consistency.

Boosting Developer Productivity across the SDLC

Developer efficiency emerged as another strategic priority. Coinbase provides multiple best-in-class coding assistants (e.g., Claude Code, Cursor) powered by Anthropic models via Bedrock, allowing engineers to select preferred tools.

A custom GitHub Action automates pull-request reviews: summarizing changes, generating natural-language comments, enforcing conventions, identifying testing gaps, and offering debugging guidance for CI failures. This shifts human review toward higher-value architectural concerns.

For quality assurance, an in-house UI testing tool translates natural-language test descriptions into autonomous browser actions across form factors, achieving parity with human accuracy, triple the bug-detection rate, and 86% cost reduction versus manual testing.

Quantifiable outcomes include nearly 40% of daily code being AI-generated or influenced (targeting 50%), 75,000 annual hours saved via automated PR reviews, and dramatically faster test introduction.

Future Directions and Platform Modernization

Coinbase aims to democratize agentic AI across the organization, enabling every employee to experiment and innovate. Ongoing efforts focus on modernizing existing tools and scaling enterprise-wide impact.

Agent Core features—secure deployment, robust identity management, advanced memory, and interoperability—are viewed as pivotal for the next phase of expansion.

Conclusion

The Coinbase case illustrates a mature approach to generative AI deployment: leveraging a unified platform on Amazon Bedrock to address volatility-driven operational challenges while upholding security and regulatory standards. By combining autonomous agents, human augmentation, and rigorous evaluation, the company has realized substantial automation, cost savings, and quality improvements across support, compliance, and engineering functions. As agentic systems evolve, such integrated architectures offer a blueprint for financial institutions seeking transformative efficiency without compromising trust.

Links:

• Lecture video

Lecturer

Chris Benyarko is Executive Vice President of Direct-to-Consumer at the NBA, overseeing fan engagement and digital strategies. Andy Oh serves as Principal of Live Sports Events at Prime Video, leading NBA broadcasting partnerships. Kristen Schaff is Global Director of Sports Partnerships at AWS, managing collaborations across major leagues. Relevant links include Chris Benyarko’s LinkedIn profile (https://www.linkedin.com/in/chris-benyarko-/) and Kristen Schaff’s LinkedIn profile (https://www.linkedin.com/in/kristen-schaff/).

Abstract

This article investigates the NBA’s digital transformation via AWS, focusing on AI-driven analytics, fan personalization, and broadcasting innovations. It analyzes partnerships enhancing game strategies, viewer experiences, and global engagement, with implications for sports technology scalability.

The NBA-AWS Partnership: Shared Vision and Technological Foundations

The NBA’s strategic alliance with AWS, formally unveiled on October 1st, is rooted in a mutual commitment to innovation and an unwavering focus on fan experiences. Chris Benyarko emphasizes that this partnership transcends mere technology provision, positioning AWS as a true collaborator in advancing the league’s goals. At its foundation lies a shared philosophy: while the NBA prioritizes fan and future fan obsession, AWS brings its renowned customer-centric approach, creating a synergy that amplifies their joint efforts. This alignment enables the league to harness AWS’s robust infrastructure for seamless integration across various operations, ultimately accelerating the pace of technological advancements.

In the broader context of basketball’s ongoing evolution, the need for sophisticated, data-driven solutions has never been more pressing. AWS offers a scalable cloud platform that excels in handling complex analytics, artificial intelligence, and machine learning tasks, converting vast amounts of raw data into meaningful insights that inform decision-making at every level. Kristen Schaff highlights what drew AWS to the NBA, pointing out the league’s dynamic, fast-paced nature and its abundance of data as ideal attributes that align perfectly with AWS’s technological strengths. From player performance tracking to predictive modeling, this collaboration leverages AWS’s tools to address the unique demands of professional sports.

The methodology underpinning this partnership involves a comprehensive migration of workflows to AWS services, ensuring low-latency streaming and personalized content delivery that reaches audiences worldwide. By combining the NBA’s deep domain knowledge with AWS’s technical prowess, the alliance not only enhances current offerings but also paves the way for future innovations that could redefine the sport.

AI and Analytics Transforming Gameplay and Strategy

Artificial intelligence is at the forefront of reshaping basketball analytics, influencing everything from individual player development to collective team strategies during games. Chris Benyarko delves into the capabilities of Second Spectrum’s optical tracking system, which deploys 29 cameras in each arena to capture an astonishing 100 million data points per night. These metrics encompass detailed aspects such as player speed, defensive positioning, and shot quality, providing coaches and analysts with granular information that was previously unattainable.

AWS plays a pivotal role in this transformation by powering machine learning models that forecast game outcomes and simulate various scenarios, thereby assisting coaches in refining their tactics. The implications are significant, as teams can now gain substantial competitive advantages through data-informed decisions, while fans benefit from enriched content on platforms like NBA League Pass, including automated highlight reels that capture the most thrilling moments. Andy Oh complements this by describing how Prime Video integrates AWS for real-time statistical overlays, which add layers of depth to the viewing experience and foster greater immersion.

Nevertheless, challenges such as data latency persist, and the partnership addresses these through continuous infrastructure optimizations, ensuring that the flow of information remains timely and reliable.

Enhancing Fan Engagement Through Personalization

Personalization has emerged as a key driver in elevating fan engagement, utilizing AI to deliver content that resonates on an individual level. Chris Benyarko explains the progression of NBA League Pass, which now employs AI to generate highlights in multiple languages, offer alternate viewing streams focused on specific players, and provide predictive elements like real-time win probabilities. These features not only cater to diverse global audiences but also deepen the connection between fans and the game.

AWS’s extensive global network facilitates this by guaranteeing low-latency delivery to over 200 countries, making high-quality experiences accessible regardless of location. Kristen Schaff underscores the importance of data privacy within these personalization efforts, ensuring that the NBA’s fan-first principles are upheld through secure, unified data management practices.

An analysis of this approach reveals its potential to shift traditional passive spectatorship toward more interactive and tailored interactions, which in turn boosts viewer retention and opens new avenues for monetization through precisely targeted advertising.

Broadcasting Innovations and Latency Challenges

Prime Video’s integration of NBA content exemplifies how AWS enables groundbreaking broadcasting innovations. Andy Oh outlines the process of capturing feeds directly from arenas and minimizing transmission hops to achieve near-real-time delivery, a critical factor especially for integrations involving live betting.

Among the notable advancements is AI-generated commentary available in various languages, powered by AWS Bedrock for natural and accurate translations. The broader implications extend to democratizing access to premium content, thereby expanding the NBA’s global footprint and attracting new demographics. However, the persistent challenge of avoiding spoilers drives an ongoing emphasis on latency reduction, with AWS tools providing the means for continuous monitoring and swift adjustments to maintain optimal performance.

Implications for Sports and Broader Industries

The NBA-AWS partnership offers valuable insights that transcend the realm of sports, demonstrating the power of real-time data platforms, personalized content delivery, and AI in production environments. Chris Benyarko envisions extending these technologies to non-professional leagues, potentially increasing participation by making advanced analytics more widely available.

Looking ahead, AI could further innovate by predicting injuries or optimizing training regimens, fundamentally altering athletic preparation and performance. These developments not only enhance the sport but also provide scalable models applicable to other industries seeking to leverage data for competitive advantage.

Conclusion

The synergy between AWS and the NBA vividly illustrates the transformative potential of AI in sports. By enhancing analytics, personalization, and broadcasting through advanced cloud technologies, this collaboration redefines fan engagement and sets a precedent for innovation across various sectors.

Links:

• https://www.youtube.com/watch?v=pZczwGVzWxo
• https://www.linkedin.com/in/chris-benyarko-/
• https://www.linkedin.com/in/kristen-schaff/