CEOInterviews.AI
Start App
Get an email when Matthew Garman gives a new interview
One email per new interview. Unsubscribe in one click.
Matthew Garman
CEO of Amazon Web Services, Amazon

Inside Amazon’s $1 trillion AWS plan

📅 Nov 10, 2026 Sources Podcast and Alex Heath 52 MIN 322 VIEWS 108 SEGMENTS · 2 SPEAKERS
Amazon thinks its cloud business could generate $1 trillion a year within the next five to ten years. I sit down with AWS CEO Matt Garman in Seattle to understand what gives him that confidence and what could get in the way. Garman explains how AI is pushing companies to move their core operations into the cloud, accelerating the business AWS spent two decades building. We discuss why he thinks inference, the computing required to run AI models, is still below 1 percent of its eventual scale. He says AWS is adding one GPU every 14 seconds and expects capacity shortages for another couple of...

What Matthew Garman said

Written from the verified transcript and checked against it. Every figure links to the moment it was said.

Matthew Garman, CEO of AWS, discussed the company's growth and strategy. He said AWS is at a $182 billion run rate growing 39%, with year-over-year growth accelerating for six straight quarters, driven by customers moving core workloads to the cloud to leverage AI. He acknowledged demand outstrips supply and expects capacity shortages for the next couple of years. He dismissed systemic risk in the compute trade, noting AWS's business is diversified across millions of customers and mostly inference workloads, unlike debt-financed NeoClouds with concentrated training clusters. He called inference 'super early' and said it's not even 1% of its potential. He defended data center practices, citing water-positive commitment by 2030 and being the largest creator of carbon-zero energy. He dismissed space and ocean data centers as impractical, favoring deserts. He confirmed a reset in Nova frontier model strategy but remains invested. He highlighted automated reasoning as a key investment for agent safety, with deployments starting next year.

Key takeaways

  1. AWS is at a $182 billion run rate growing 39% year-over-year, with growth accelerating for six consecutive quarters.
  2. Demand for AWS capacity will outstrip supply for the next couple of years despite record capex.
  3. Inference is 'super early' and not even 1% of its potential, with usage multiplying when costs drop 50%.
  4. AWS will start deploying automated reasoning tools for agent safety next year.
  5. AWS is committed to being water positive by 2030 and is the largest creator of carbon-zero energy in the last 5 years.

Numbers and commitments

FigureWhat it refers toTypeAt
$182 billion AWS annualized revenue run rate metric 1:16
39% AWS year-over-year growth rate metric 1:16
2030 Target year for water positive commitment timeline 20:27
40 US households Water usage of largest data centers compared to households metric 20:27
5 years Period of being largest creator of carbon-zero energy metric 20:27
one GPU every 14 seconds Rate of GPU deployment in data centers metric 29:07
85% Share of workloads still on-premises metric 37:36

Chapters

  1. 0:00AWS growth and trillion-dollar ambition
  2. 2:25AI driving cloud migration
  3. 7:48Customer growth across segments
  4. 10:00Cost management and capacity constraints
  5. 14:10Systemic risk in compute trade
  6. 16:51Inference versus training workloads
  7. 20:03Data center community and environmental impact
  8. 28:21Data center locations: space, ocean, desert
  9. 31:38Inference providers and cloud stack
  10. 36:52Trainium external sales and capacity allocation

Questions asked in this interview

12
  1. 7:48How much of the growth is big customers wanting to spend more versus the long tail?
  2. 16:57It's like where does that tap out and then what does that mean for the training piece of the pie?
  3. 19:15I mean, if you're talking like potentially trillions of dollars in inference that's happening, I'm just like, where is that coming from?
  4. 20:03What do you make of where the country is on data centers, especially given the midterms, what happened in Texas where the governor campaigned on, you know, pausing data centers?
  5. 27:36Are we still on track for our goals?
  6. 28:21What do you think about data centers in space?
  7. 33:54Have you been thinking about that?
  8. 37:22But why not make them have to use it in AWS?
  9. 38:10Like how do you balance that?
  10. 41:08Anything on what you learned in terms of what's kind of driving this reset that you can be more specific on?
  11. 41:37What have your conversations been like on that internally with the team and customers?
  12. 46:31Like have you thought much about that?
Alex Heath 0:00 ↗
Matt, it's great to be with you. I feel like what's happening right now at AWS feels unprecedented in a lot of ways. So, you're the world's biggest cloud computing company. You're the highest capex spender. You have an estimated, I think, like 44 gigawatts of capacity that's coming under development in the US, which is more than Google and Meta combined. And then what just happened was Andy Jassy on the earnings call saying AWS could be a trillion-dollar revenue business in the next 5 to 10 years, which is a huge number, obviously. If my math is correct, I mean, based on the run rate you're already on, that requires roughly 40% compound growth over 5 years or 18-ish over 10 years. And this is off of a massive, massive base. I think a lot of people when they heard that were like, 'Wow, like what are they seeing?' And then I was also looking at the way you all have been talking about the business over the last couple quarters and I think it was towards the beginning of this year, Andy was saying we think roughly 600 billion by around 2036, and then in Q2 he floated the trillion, and then in Q3 it felt like a very strong declarative moment. And I'm curious, like maybe we could start here, like what happened between Q2 and Q3.
Matthew Garman 1:16 ↗
Yeah. Well, look, if I step back, I think we have probably for 20 years thought that the AWS opportunity is just a massive business opportunity and unlike one that we've seen before. And so I've been with AWS for 20 years and we've been growing that whole time. And I think over time we have more and more gotten conviction that the business opportunity is just really, really, really large. And you know, it's surprising but at the point that we're at now, we're at a $182 billion run rate business. And so you're over $180 billion and you're growing at 39%. There's not many companies that hit that spot. And as we've seen, we've actually increased our year-over-year growth rate each of the last six quarters. And so, as we see that acceleration, what happens there is we've always had this view that the majority of workloads still live in on-premise worlds. And as big as the cloud has gotten, there's still a lot of data centers that people have. There's a lot of workloads that live on prem. And there are more workloads that are just being created every single day.
And I would say over the last two years, really what we've gotten excited about is this flywheel where customers now see that there is a massive opportunity that AI affords them to gain efficiencies, to build new businesses, to create new customer experiences, to rethink how work gets done, to build faster for customers. And they don't get that benefit if their core workloads aren't in a cloud environment. If they're running in an on-prem database, if they're running in an on-prem mainframe server, if they're in a VMware cluster in their legacy data center, they just have a hard time having agents talk to those pieces, pulling data from all those different data sources doesn't work. And so what we've actually seen is customers already saw benefits of the cloud. There's cost improvements, there's agility improvements. There's a reason why the AWS business has been growing great for the last 20 years, but it really accelerated when people realized they weren't going to get the benefit of AI if they didn't get those workloads in the cloud, those core workloads as part of it. So, we've actually seen our core business really accelerate over the last couple of years. And the more core workloads get in the cloud, the more they can actually take advantage of AI. And so there's this real positive flywheel effect where actually the revenue growth that we're seeing is significantly accelerating. And I think that's just further bolstered our confidence in the growth of AWS.
I think the other things that we're seeing is just what's possible. I think a couple of years ago, you saw incredible content generation, you saw incredible conversational chatbots being made. And then as we moved into worlds of agents where work was really done, we're now just seeing customers really scratch the surface of what's possible where you have a fully autonomous agent taking advantage of what we see are really powerful models out there that can run longer and longer and do harder and harder things. And they're really starting to think about and see how core parts of their workloads can be automated, improved, and built upon. And that opens up effectively all of the things that enterprises do. And it opens up the pie for everyone. It's not like you're taking from where they used to spend over A and bringing it to B. It's actually creating new businesses, creating new revenue streams for our customers. And they're seeing cloud as a way to get to those places. And so we see that growth across tens of thousands of different startups, enterprises, large companies. And so when we see that growth where we see companies just really scratching the surface of the benefit that they're getting and we're seeing this flywheel effect, it gives us a lot of confidence that there's a huge amount of business going forward for us. And you know, it's far from certain. We've got to do a lot of execution. There's a lot of invention. There's a lot of things that we need to do between here and there. But the opportunity and the space for us to go after and help customers go and grow and take advantage of these technologies is bigger than it's ever been.
Alex Heath 5:18 ↗
This episode is brought to you by Granola, the AI notepad for people in back-to-back meetings. It works everywhere you do and lets you focus on what matters. Try it at granola.ai/sources and use the code sources for 3 months off. This episode is also brought to you by Mercury, AI-native banking that's loved by more than 300,000 entrepreneurs, including me. Visit mercury.com to learn more. Mercury is a fintech, not a bank. Check the show notes for details. This episode is brought to you by Jira by Atlassian, where teams get the context, visibility, and control to move work forward. Try it free at jira.com. That's jira.com.
AI is causing companies to come from, you know, on-prem to the cloud. That's driving a lot of this growth.
Matthew Garman 6:03 ↗
Absolutely.
Alex Heath 6:04 ↗
Interesting. I hadn't thought about that. I mean, you've been saying and the company's been saying for so long, like, we underestimate how much of data is still on prem, and for people who don't know, just means like it's not in the cloud. It's somewhere local. What you all are seeing is people who have resisted the cloud are going towards it because of AI.
Matthew Garman 6:21 ↗
We'll use this as just take something like an analytics workload. Okay, an analytics workload. Traditionally, a customer might say, 'Great, I've got a data warehouse. It's running in my data center. I could move it to the cloud and take advantage of Amazon's analytics capabilities or move it to a Snowflake or a Databricks or something like that. That would be great. I could do that.' And a lot of people did, but they're also like, 'Yeah, but I'm still able to do the analytics here and it's working and maybe I won't move it or maybe I'll do it next year or two years when I can make the project work.' And we saw those migrations happening, by the way, but they're slow and measured and scheduled out. Now we see people saying, 'Okay, actually I can ask an agent to go across all of my sources of data.' And not just can I do my analytics faster or cheaper, but with new technologies that are available in a cloud world, say something like a DuckDB data engine that's working across all of my different data sources, I can actually have an agent go and do all of that. And when I have an agent do that, it has to have all of the data sources accessible. They have to be available to the agent. It has to know where all the data is. But I actually get very new insights and actually can build new businesses, unlock new sources of revenue, new source of profitability when I can do that. Except one of my sources of data is locked up in a mainframe. And so it just draws all of it in because they kind of can start to see where that benefit is. And I think there's a real risk that companies that don't make that move, they're getting passed by the ones that are in the cloud.
Alex Heath 7:48 ↗
How much of the growth is big customers wanting to spend more versus the long tail?
Matthew Garman 7:54 ↗
Well, look, big customers are big, so they spend lots. So, a lot of it is that. But I will say that the long tail is growing bigger. It really is across the board. And as we think about the long tail, I think it's both, you know, it's not a lot of our growth is driven by like, you know, dentist office, like not really kind of real small SMBs. Those are mostly served by a lot of our partners that actually run their software and services on top of AWS. But our customers, we have a really broad swath of whether it's, you know, global top 5,000 enterprises. Actually just this week, I was in the Bay Area meeting a bunch of startups that many of them started less than 6 months ago, and they're really thinking about how do they use AWS to accelerate their growth, accelerate their technology development, accelerate their route to market, and our customers love having access to that capability as well. And so it's across the board. Sometimes it's the very largest banks, the very largest healthcare companies, the very largest governments in the world, and sometimes it's a two-person startup that has an idea and just wants to build. And we're seeing growth from all of those segments. In fact, it's never been easier to build than it is today, to be a two-person startup and go try something and actually get it to scale. And I do not think I've found a two-person startup that goes and tries to find data center space and rack a server to start getting going, right? Like it just doesn't make any sense. And so that's been true for a long time, but now they can use AI to really further amplify the impact that they're going to have and how fast that they can grow. And we're seeing those new companies scale really rapidly when they get that product-market fit, and AWS and the cloud gives them a chance to cycle until they get that product fit.
Alex Heath 9:33 ↗
Something that does feel new though about this moment, I agree with you, but when you scale right now, especially if you're AI-heavy and you're doing a lot of inference, you can, I think it's Fireworks, but I've heard the concept of like you can scale into bankruptcy. There's a sense of like, you know, you can't scale because of the compute, which you have most of. So, I'm curious how you think about that and how you advise, you know, companies and startups you meet with that are facing that issue because I think it's a really real issue.
Matthew Garman 10:00 ↗
It is a very real issue and actually we're thinking deeply and actually investing in more robust cost management tools for companies so that they can do exactly that. Customers want tools that range from, you know, shut my account down when it hits this dollar amount, like I don't care, it's okay, like I'll figure it out, but I don't want to spend more than this, to alert me when I hit this dollar amount, to if it's inference, maybe ratchet my usage from an expensive model to a cheaper model, and we're trying to think about what are all of the tools and controls that we can give customers so that they can actually feel confident about that cost management. Even larger customers, by the way, it's not necessarily the small customers that are worried about, you know, spending $10,000 and not being able to afford it, but even large companies are saying, you know what, I may want this particular person to be able to spend largely uncontrolled, but, you know, Alex, on your personal account, you know, it's $100 and then I shut it down or whatever it is. And so really giving those fine-grain controls so that companies of all sizes have that, I think is incredibly important.
I think from a capacity point of view, that is a real concern. And it's part of why we're spending so much on capex and investing in this infrastructure. We're of this fortunate position. I think a lot of people are worried about things like concentration risk when you're spending capital and things like that. For us, we spread that usage across, you know, we have tens of hundreds of thousands, millions of customers that are all using AWS. And so when I see a lot of that comes from a broad swath of companies, that's where we feel confident that we can go and put down a lot of capital and really grow the amount of compute that's available for customers because we get really good signals as to where they're all growing, what it looks like, what demand is going to look like next year, what it's going to look like the year after that. And we have good signals and many of our larger customers will commit to five, sometimes even 8, 9, 10 year commitments on their spend with us. But most of them are in the kind of, you know, three, four, five, six-year commitments. But that gives us really good visibility as to what their growth is going to look like and oftentimes those customers frankly will outspend their commitments. But it's more a baseline, but it gives us a good sense of where that growth is going to be. And unfortunately, you know, well, fortunately or unfortunately, but right now the demand is far outstripping the supply. And so even spending as much capex as we are, investing as much as we are ahead in capacity, I anticipate that we'll be short of capacity for the next couple years.
Alex Heath 12:25 ↗
Can you see into 2030?
Matthew Garman 12:28 ↗
Some, you know, I think you can see trends. I can't personally, otherwise, you know, you're an alchemist. Yeah, I do some sports betting or something, but we get signals, right? And there's, you know, how we think about it actually, it a little bit goes back to the kind of the supply chain roots of Amazon where we really think about how do we manage our full supply chain and then at AWS we really think about how do I spend money at the last possible minute so that I have as much possible information as I have while giving myself option value to hit the upside, right? Because I'd like to, the optimal is I would have exactly as much capacity as I need. You're never going to be perfect. You don't want to overspend and you don't want to wildly underspend in that capex. And so what we do is you think about what are those long lead time components that you have to go spend on. You have to buy land, you have to acquire power contracts, you have to, you know, get permitting, things like that. Then as you get closer to like landing a data center, you might have to buy networking equipment, you might have to buy generators, you might have to buy some of those other pieces. So, if you're going all the way out to 2030, I might be buying land today that I plan to use in 2030. We're not buying servers, you know, we're not buying all of those things. And so, I can wait for a lot of the capex expenses that I would need to support my 2030 proposed growth until much closer to 2030. And so, I don't have to have perfect views into 2030. You can have directions on where they go. And if we're wrong, I could probably resell land and it's, you know, worst case you lost a little bit on appreciation or not, but mostly it's a durable asset that you can resell. And so we think about our investments kind of staged that way and it takes some of the risk out of there as we think about it. But it requires a lot of long-term planning and thinking and watching kind of the various variables that you have in there.
Alex Heath 14:10 ↗
Everyone in the markets feels like is looking for reasons to doubt the compute trade. And you've seen it with CoreWeave, you've seen it with the NeoClouds in particular and the debt markets. I'd be curious to hear what you make of the moment we're in. You had, I think, kind of alluded to it earlier, but you all are in a different spot obviously, but I do think that there's systemic risk a little bit that everyone's trying to figure out like how bad is it.
Matthew Garman 14:34 ↗
Yeah, I don't think it's systemic risk actually. I do think that the risk is localized because the bets that people are making are materially different. And everybody has to go kind of make their own bets. I think when you've completely debt financed at a relatively high rate, you have much smaller error bars as to like when your cash flows are going to land, you also have much smaller error bars when you have high concentration of customers and concentration of workloads. And so if you go and look at the workloads that are in many of the NeoClouds, they're really large training clusters for the most part. And those really large training clusters are largely being bought by a small number of customers and they're all, you know, debt financed at relatively high rates. That is not the business that we're in. We both have data centers and computers, but other than that, like the business is actually quite different. Most of our business is spread across the millions of enterprises and startups and small medium-sized businesses and everyone, governments that are running on top of us, and much of that business is core compute. It's compute clusters, it's HPC workloads, it's websites, it's backup storage, it's databases, it's, you know, a lot of that kind of workload.
And then the AI workload, the majority of our AI workloads are inference today. And so that inference is effectively just, if you really look at inference today, it is just another building block as part of an application, right? Your applications all just have AI embedded in them. It might be AI that's helping somebody serve better ads. It might be AI that's helping you, you know, autosuggest something in your email. It's, you know, there's a whole bunch of things that it might be doing. It might be AI that's helping traders figure out like what their next stock market trade is going to be, but it's just part of the application that they're using. And so that is a very distributed workload. And so even if the usage is concentrated on Anthropic and OpenAI and a handful of model providers, the actual end users are thousands and thousands and thousands and thousands of folks out there running inference for us. And so the systemic risk of like one or two companies not doing well, even if it's one of those model providers, it'll fall over to another, like people aren't going to stop doing inference, they'll find a different model to use, one might be an open-weight model, it might, you know, but we're going to have computers, you can put it on those computers, and so for us that risk is very different.
Alex Heath 16:51 ↗
You all have very large investments in OpenAI and Anthropic and they're huge partners obviously.
Matthew Garman 16:56 ↗
We want them to do well just like...
Alex Heath 16:57 ↗
You want them to do well, of course. I think everyone's like, you know, everyone's on pins and needles about Anthropic IPO, but I'm curious about the training versus inference workloads you're seeing because you have such great visibility. Do you expect training to be a smaller piece of the pie going forward? And it feels early on inference, but I think everyone's trying to figure out like how big is inference going to actually be? I mean, when you see stats like 2% of Americans have even paid for AI or, you know, companies are barely using it and yet inference is exploding. It's like where does that tap out and then what does that mean for the training piece of the pie?
Matthew Garman 17:29 ↗
Yeah, I think, by the way, that stat just seems a little bit misleading. It may be that 2% of the people have paid directly for a model usage, but I bet a higher percentage of people like have a Netflix account and it recommends a movie to them, so they actually have used it. So, it's like, it is like, it's yes and no. Like it's like how many, what percentage of Americans have paid for a database? Like probably a really small percentage, but I bet they all like use it on a daily basis anytime they log in somewhere. And so, you know, I think that's a misleading stat into how integrated it is into every single application. People are going to that Amazon website every single day and when they search for a product, AI is kind of embedded in how they're searching. They pay for it, but they kind of paid for it. And so from that perspective, I think inference is a huge business. It's massive. And you've seen in some of the Anthropic filings kind of what their revenue looks like. So, it's a very good and large business. I think training is a good business, too. It's just very concentrated. And so we'll continue to support training clusters. We do support training clusters today, but it's the minority of our business for the most part just because the main source of our business we want to do is support the millions of customers we're building and growing on top of us.
Alex Heath 18:38 ↗
How early is inference, do you think?
Matthew Garman 18:40 ↗
Super early. I think it's, I think you're almost doing a disservice to say that it's at like 1% of what it's going to be. I don't think it's even 1%. I think there is a massive runway and look, every time we see inference get, you know, 50% cheaper, we see an order of magnitude more usage and so people kind of wring their hands, they're like, look how cheap it's getting, and yet the revenue is higher every single year. I think that we're still very early on that path and it's why we also feel good about the investment we're making with regards to infrastructure because I just think there is so much more that can and will be done.
Alex Heath 19:15 ↗
Do you think about that spend that's driving that inference? Is it coming out of existing budgets or is it net new? Like where is that capital? I mean, if you're talking like potentially trillions of dollars in inference that's happening, I'm just like, where is that coming from?
Matthew Garman 19:29 ↗
Yeah, I think it's all those things. I think that sometimes it's creating new value. Sometimes it's coming out of other budgets and I do think that there's no one answer to that. I think it's a lot of those things. Sometimes it's allowing you to create products and services and capabilities much faster than you could before which drives revenue, we'll call it like new sources of revenue. Sometimes it's driving efficiencies where it's supplementing. I don't need to necessarily hire a new person. I can get twice as much work done with the person that I, the thing that I have. And I think both of those things are true.
Alex Heath 20:03 ↗
What do you make of where the country is on data centers, especially given the midterms, what happened in Texas where the governor campaigned on, you know, pausing data centers? And I know you guys have your approach where you do a lot of, you know, renewable energy. You know, you're very conservative with water, but at the same time, I just think it's such a lightning rod issue and it seems like it's going to get worse before it gets better, maybe.
Matthew Garman 20:27 ↗
Yeah, I think, look, there's a couple of things here and I think it's incumbent on us to help educate folks as to that all data center producers are not created equal. And that's true for lots of industries, but today it's largely painted with one brush. And I think that there are a handful of us in the industry that spend a lot of time thinking about how do we make sure that we are great citizens and great community members as part of this. And we learned this early on with some of our fulfillment centers and other things like that. And we learned with data centers, we need to work with local politicians. We need to work with community members. We need to show that we're bringing high-paying jobs in communities. We need to make sure that we have low impact on the communities that we operate in. Our data centers, you know, we bring power and pay for all the power we bring to the grid. We oftentimes in many of the communities we work in actually reduce the tax load by thousands of dollars per person in the communities that we operate in. As you think about the environmental impact, we're the single largest creator of new carbon-zero energy sources over the last 5 years in the world and we continue to bring more carbon-zero energy to the grid every single year. Huge investments on that front. We were very early in thinking about how we use water. Actually, we have a commitment that by 2030 we'll be water positive where we bring more water to every community that we operate in than we use. And even our data centers, our largest data centers today use less water than 40 US households. Like it's like a block of households. Like it's actually a relatively small amount of water.
Alex Heath 22:01 ↗
I saw a stat that like golf courses use more water than...
Matthew Garman 22:04 ↗
By far. My golf friends don't like that I use that stat, but yes.
But yeah, I mean, there's actually, I mean, there are a lot of things out there that use way more water than our data centers. There are ways to run data centers that use lots of water, so we don't do that. And not everybody takes that path that we do. And I think that it's brought a bad name to people that proudly stand up and say, you know, I go against regulations. I don't even listen. I don't get permits. I just build data centers anyway. They kind of like proudly go against working with the community. That is just not how we do it. Unfortunately, it's kind of brought this bad name to data centers and I think it's something we're going to have to work through. But I also think that many of the folks, and even you mentioned the midterms, we work quite closely with many of the folks that are both Democrats and Republicans, and we have and we will continue to do that. We've done that for five different administrations, and they appreciate it, like they will work with them. We don't always agree on all topics, but we work there, debate there, and figure out how there's win-win scenarios with those things. And we'll continue to do that. So, I feel very good about where we are and I'm excited and congratulations to everybody who won in the elections, and we feel good about what we've brought to communities and where we'll continue to go. I think technology is so important to our economy today that we can't just turn it off and decide to not have it. I don't think that that would be good for our country. Some people want that.
Alex Heath 23:30 ↗
They want that.
Matthew Garman 23:31 ↗
They think they do. They think they do. But then if you ask them like, 'Are you going to give up your Netflix subscription?' They're like, 'Well, no, not that.' And be like, 'Okay, are you going to stop like Instagramming your friends?' Like, 'Well, okay, not that.' Are you going to stop asking Amazon to deliver stuff to you? No, okay, not that either. But those things all require data centers. Like it's like there's a weird disconnect there. And so a lot of the things that people want, I think, is, I think they want responsible. They don't want the kind of technology elites to tell them what to do, but they do like it when people build good products for them that they want to use. And our view is that there is a great way to do both of those things. You don't have to, you don't have to do that.
Alex Heath 24:06 ↗
So when you woke up the next day after the results and you saw everything, was there anything you thought about like, man, what do we, what do we do? Like what do we do as an industry? I mean, you've talked about what Amazon does, but like does the industry as a whole need to do more? Is there anything the industry can do?
Matthew Garman 24:22 ↗
I do think, and we've been working with several of the governors in the states that we operate in, and thinking about how do we help codify some of the stuff that we actually do and some of the things that they want to do into more structured programs that everybody has to follow, and I think that's one of the things that we need to do to very, to both clearly highlight why it's good to have a data center in your community because it actually brings a tax base, it brings high-paying jobs, and why it's important for the country because the alternative is technology will still progress. We would go there, you know, it would happen somewhere else. And I think that would be bad for the security of our country. It would be bad for the economy of our country, but the world is not going to stop. And so kind of thinking about how do you balance what's great for communities, great for people, great for our country, and good and reasonable for companies so that they're still incentivized to go work on these problems. And I am very convinced that there is a path there.
Alex Heath 25:21 ↗
Framer is the AI website builder that powers the Sources podcast website at podcast.sources.news. Framer brings AI agents into the same canvas where your website is designed, managed, and published so you can move faster without giving up your taste or control. I use Framer to make the Sources podcast website be the destination for everywhere you can find the show. Plus, you can also see recent issues of my newsletter. Start building with agents for free today at framer.com/sources for 30% off a Framer Pro annual plan. framer.com/sources. Rules and restrictions may apply. I spend a lot of time context switching between meetings, often with no time to process one before the next starts. Thankfully, Granola runs in the background the whole time. It's an easy-to-use AI notepad for meetings that works everywhere, even on phone calls. I use Granola to recall what was said in meetings and create helpful summaries. I use it every day to stay on top of what I need to get done with my team. It connects to my email and suggests follow-ups for me to quickly review and send, saving me valuable time. Granola isn't just a core part of my workflow. It's basically my second brain. Try Granola at granola.ai/sources and use the promo code sources for 3 months off. Mercury is a modern take on banking built for startups like mine. When I decided to start my media business, Mercury was by far the most...
straightforward, full-featured banking solution for me to set up quickly. The interface is intuitive and simple, saving me valuable time every day. I use Mercury to track my spending, bills, and invoicing. I love that I can delegate permissions to my team so they can keep things running for me in exactly the way I want them to. My favorite part is how forward-looking Mercury is with AI. Legacy banks are stuck in the past, but Mercury is built for how modern software works today. I use its built-in command assistant to analyze cash flow and help me move money. And Mercury also connects to other AI tools like ChatGPT and Claude. I use this feature all the time, and the folks at Mercury actually let me know that I'm one of the top users of it. So, trust me, it's finally easy to get real-time financial data about your business wherever you need it. Visit mercury.com to learn more and apply online in minutes. Mercury is a fintech company, not a FDIC insured bank. Banking services provided through Choice Financial Group and Column NA, members FDIC.
As you move faster and bring in more AI agents, keeping tabs on what's actually happening gets harder. Who's working on that? What did that agent just change? Are we still on track for our goals? That's why teams rely on Jira for visibility across their work, whether it's done by people or agents. Jira is powered by Atlassian's teamwork graph, which connects work across Jira, your most-used tools and apps, and your agents. That means your agents share the same context your team has, like the goal behind the work, the decision made yesterday, and the project plan, so they work faster and more accurately. You get oversight, track agent progress right alongside human work, spot blockers sooner, and connect your work to goals. You don't have to choose between shipping fast and staying in control.
I want to get your reaction to like three areas that people are talking about putting data centers right now. So there's space, ocean, and desert. These are people are excited about these to varying degrees. Okay, maybe we can start with space. What do you think about data centers in space?
Matthew Garman 28:37 ↗
I think that it is highly unlikely to be economically feasible or practical in the next decade or two.
Alex Heath 28:44 ↗
Decade or two.
Matthew Garman 28:45 ↗
Yeah.
Alex Heath 28:46 ↗
Okay. So that's a no on space then. I mean, here's the thing is it sounds good. You get free energy and it's up there somewhere.
Matthew Garman 28:54 ↗
That's great. Number one, launches are still relatively infrequent and expensive.
Alex Heath 29:01 ↗
Mhm. Elon's trying to fix that. But yes.
Matthew Garman 29:04 ↗
Okay.
Alex Heath 29:05 ↗
Yeah. But to your point, still waiting. Yeah. Yeah.
Matthew Garman 29:07 ↗
Like it's a great, I appreciate it, but one person is not going to fix it. And still there's, we as a world don't do one launch a day today. The whole world in a data center. We're landing in a data center today, one GPU every 14 seconds.
Alex Heath 29:23 ↗
Wow.
Matthew Garman 29:25 ↗
So, we don't do a launch a day for the world. And that's just us doing one GPU, you know, now there's obviously like, so let's say one launch, and by the way, a rack of GPUs, you know, might weigh a ton. Yeah. So, I don't even know if you can stick that on a launch vehicle or how many you can get up there. You know, people talk about gigawatt data centers and megawatts of racks and whatever. Like most solar panels and things drive kilowatts, not gigawatts. So you need these gigantic things that are up there. There's still, they're really hot, right? And everyone's like space is cold. Space also doesn't have air. Actually, dissipating heat in space is actually quite hard. And so that's actually, it's just a really hard environment. There's radiation everywhere. So you have to build things. It's going to be way more expensive to build servers. From a serviceability point of view, by the way, these are all technically solvable problems. And it's just going to take a while. Like it's like I'm not saying any of these things that I could highlight are not impossible. And I just think that it's way far out.
Alex Heath 30:18 ↗
Okay. Oceans though.
Matthew Garman 30:20 ↗
Oceans, there's some of those same problems. I think you get cooling, which is good. You have things floating in the water and moving. It's a little harder. So I find oceans to be also probably impractical. I think deserts of those three that you mentioned are by far the most likely. There's a, you have relatively good environmental areas. You actually have heat sinks. You have solar areas that you could do it. I think deserts are very interesting and potentially also when you go to liquid cooling, actually cooling the data center becomes actually a little bit of an easier problem in some dimensions with regards to energy usage at least. So I think oceans or deserts could be an interesting place particularly because yeah, like you can also lay a cable. Like it turns out that actually the data transfer and stuff is pretty useful and there's no people there which may be good for the climate we're in.
Alex Heath 31:14 ↗
Well yeah, I mean look, yes, although then there's no one to benefit from kind of an increased tax base or anything like that too. So there like, there are...
Matthew Garman 31:22 ↗
It turns out people like living in towns, they like where they have high-paying jobs. Like there's a bunch of things that like having those things nearby. It just means the high-paying jobs aren't going to be in your town. The tax base is not going to be in your town. Like there's a lot of those things that are not great.
Alex Heath 31:34 ↗
Yeah.
Matthew Garman 31:35 ↗
That people kind of say like, oh, actually I do want that.
Alex Heath 31:38 ↗
I'm really curious what you make of all of these inference providers that are popping up. So Baseten, Fireworks, Modal, Fal, the list goes on, and they're servicing a very important, growing part of I guess you could call it cloud stack. Very AI-native, very model-heavy tuning, and then there's a whole post-training inference world that's developing. Yeah. When you look at that and you all obviously have that as well, what do you make of that? Is that in your mind a new kind of cloud market that's forming or is it just a moment in time? Like how do you think about that?

50 more exchanges in this transcript

Sign in free to read the rest of this interview. No card required.

Sign in to read the full transcript

Cite this transcript

APA, MLA, BibTeX
APA

Garman, M. (2026, November 10). Inside Amazon’s $1 trillion AWS plan [Interview transcript]. Sources Podcast and Alex Heath. CEOInterviews.AI. https://ceointerviews.ai/interview/3239572/

MLA

Matthew Garman. "Inside Amazon’s $1 trillion AWS plan." Sources Podcast and Alex Heath, 10 Nov. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/3239572/.

BibTeX
@misc{garman2026_3239572,
  author       = {Matthew Garman},
  title        = {Inside Amazon’s $1 trillion AWS plan},
  howpublished = {Interview transcript, Sources Podcast and Alex Heath. CEOInterviews.AI},
  year         = {2026},
  month        = {nov},
  url          = {https://ceointerviews.ai/interview/3239572/},
  note         = {Speaker-attributed transcript with timestamps}
}