What Amazon put on the balance sheet

On July 7, Amazon sold at least 25 billion dollars of bonds in eight tranches, with maturities running from three to forty years and a mix of fixed and floating rates, tagged for general corporate purposes that include capital spending and debt paydown. Barclays, Goldman Sachs, JPMorgan and Morgan Stanley led the deal. It follows about 54 billion dollars of bonds issued earlier in the year and a 10 billion dollar Canadian offering in June, taking Amazon's 2026 borrowing to roughly 89 billion dollars, and the company said it does not plan to issue more debt this year.

The money underwrites a spending year of a different order. Amazon has guided investors toward about 200 billion dollars in capital expenditure for 2026, up from roughly 131 billion in 2025, most of it data centers and chips for AWS. AWS revenue grew 28 percent in the most recent quarter, and Amazon's own Trainium and Graviton silicon is now projected to generate more than 10 billion dollars a year. The scale is not the surprise. The funding mix is: the largest cloud provider is now borrowing, at size, to keep building.

The tell in the order book

The interesting number is not the 25 billion, it is what happened underneath it. Orders for the deal peaked near 62 billion dollars, then were pared to about 41 billion once the banks trimmed the spread, leaving demand at roughly 1.6 times the size. To get there, Amazon had to offer extra yield relative to where its bonds normally price. A double-A borrower dangling a concession to fill a book is a small signal with a large meaning: the cheap-money phase of the AI build-out is closing, and even the strongest names now pay a premium to finance it.

Amazon is not alone. Alphabet, Microsoft, Meta and Oracle are all tapping debt and equity markets, with the group collectively pointing at more than 700 billion dollars of AI infrastructure spending this year. When that much capital is being raised against a demand curve nobody can yet prove, the market starts asking whether the returns will arrive on the timeline the debt assumes. That question does not have to end badly to matter. It just has to make lenders, and customers, price the risk.

What it means if your stack runs on AWS

For an operator running on AWS, the read is two-sided. The commitment side is real: chief executive Andy Jassy has said demand for AI capacity is outrunning what Amazon can bring online, so the capacity you may be queuing for is being built at speed. But demand outrunning supply is also an allocation-and-pricing statement. Capacity that is scarce and expensive to finance does not get cheaper for the customer first. A build-out funded by 40-year bonds carries a fixed obligation that has to be repaid whether or not the AI demand curve cooperates, and repayment pressure tends to travel downstream into list prices and contract terms.

The practical move is to treat cloud cost as a multi-year durability question rather than a monthly line. Model what your AWS bill looks like if committed-use discounts tighten, read renewal terms for the right to reprice, and keep a credible second option warm even if you never use it. None of this means leaving AWS. It means recognizing that the provider has just put its AI build-out on credit, and that the interest on that credit is one of the inputs that will eventually shape what you pay.