AWS revenue could hit $1T in a decade, Jassy says

What happened

Amazon chief executive Andy Jassy has said Amazon Web Services (AWS) could reach $1 trillion in revenue within the next decade, a projection tied to surging demand for AI. CIO Dive reported the remarks alongside the company's latest quarterly results.

AWS grew 39% in the third quarter of fiscal 2026, and the reporting links that acceleration to AI reshaping cloud computing. Spend on cloud services has reached $168 billion, a figure that underlines how much of the market's growth now depends on AI workloads rather than traditional hosting.

Why it matters

For leaders in digital transformation, the significance lies less in the headline number than in what sits beneath it. Cloud platforms are becoming the default infrastructure for running AI models, data pipelines and automated services. That means decisions about cloud architecture increasingly shape how quickly an organisation can launch a new digital service, personalise an interaction or respond to a customer problem.

It also raises the stakes for operating models. When a growing share of customer-facing capability runs on a small number of hyperscale providers, questions about reliability, data governance and vendor dependency move from the IT department into the boardroom. Service leaders who treat cloud as a procurement line rather than a design constraint may find those trade-offs surfacing later as service failures.

By the numbers

• 39% growth reported for AWS in the third quarter of fiscal 2026
• $168 billion in spend on cloud services, as cited in the reporting
• $1 trillion in revenue that Jassy suggested AWS could reach within the next decade

The Renascence take

Most readers will treat a trillion-dollar ambition as a statement about one company's scale. We see it as a signal about where customer experience will be built and where it will break. The principle at play is one behavioural economists know well: people judge a service by its least reliable moment, not its average one, and infrastructure decisions made for growth often determine those moments.

The question for customer-obsessed operators is not whether AWS reaches $1 trillion, but how much of their service promise now depends on a provider they do not control. Map every customer journey to the cloud and AI dependencies beneath it, and define the outage and latency thresholds that would change the experience. Then measure resilience in customer terms, such as failed transactions and abandoned journeys, rather than in uptime alone.