Amazon Q3: A $496 Billion Backlog And Negative Free Cash Flow

Amazon reports Q3 on October 29 after AWS grew 37% year over year in Q2, with a $496 billion backlog and growth accelerating for a fifth straight quarter. Q3 revenue guidance of $197–$202 billion appears soft, though the article attributes most of the slowdown to Prime Day shifting into Q2 and FX headwinds. The key concern is $220 billion in 2026 CapEx, which has pushed trailing-12-month free cash flow to -$7.6 billion; 2027 CapEx is expected to be higher.

Analysis

The key question is whether investment is converting into durable, cash-generative AWS demand—not whether capex is large in isolation. A backlog is not near-term revenue: conversion pace, customer deployment timing, and utilization will determine whether the build earns an adequate return. If capacity comes online ahead of workloads, depreciation and power costs can pressure margins before revenue catches up; if capacity is constrained, Microsoft and Google Cloud may win workloads that AWS cannot serve promptly.

Near term, Prime Day timing and FX complicate the headline revenue comparison, so the more informative read-through is AWS growth, operating income, and management’s explanation of capacity utilization and incremental investment. Over 1–3 months, explicit evidence of backlog conversion and demand coverage could support the shares despite weak free cash flow. Over 6–18 months, the risk is that rising infrastructure commitments outpace monetization, keeping cash generation weak and limiting multiple expansion. The contrarian risk to a bearish read is that investors focus on current cash burn while underestimating the option value of scarce, usable cloud capacity. The supplied figures alone do not establish valuation or financing stress.

Key Decisions for Investors

• Avoid initiating a large outright AMZN position immediately ahead of the October 29 report; event risk is asymmetric, and the supplied data do not establish whether the current valuation discounts the investment cycle.
• Consider a staged long only if the report confirms AWS demand is converting into revenue and operating income, while management provides credible utilization or capacity-coverage evidence. Reassess if AWS growth decelerates materially or investment rises without a clear monetization path.
• Treat a short AMZN thesis as conditional, not a base case: stronger evidence would be weaker AWS growth or margins alongside higher investment and continued deterioration in cash generation. The thesis is falsified by improving AWS operating performance and convincing evidence that new capacity is being absorbed.
• For the call, verify whether the capex figure refers to cash outlays versus commitments, the expected timing of depreciation, AWS backlog conversion, and the extent of FX and Prime Day effects. Without these details, do not infer near-term earnings sensitivity from the headline figures alone.