This article is based on reporting originally published by Taipei Times and sourced from Bloomberg News, dated April 2020.
A Crisis Lands on Cloud Bills
By mid-March 2020, John Lyotier’s travel software company, Left Technologies Inc, was in freefall. The COVID-19 pandemic had gutted the travel industry almost overnight. Like many small business owners, Lyotier reached out to his office landlord — and got rent relief. Then he contacted Amazon.com Inc, asking to “explore creative financing opportunities” for his monthly cloud-computing bill.
The response from Amazon was blunt: “Nope, that’s the way it is.”
That exchange encapsulates the friction between the commercial reality of cloud computing contracts and the economic devastation experienced by startups and small businesses during the pandemic’s early months.
Cloud Giants: Essential Infrastructure, Rigid Contracts
Amazon Web Services (AWS), Microsoft Azure, and Google Cloud had transformed the internet economy over the prior decade by making enterprise-grade computing accessible on a credit card. The on-demand, pay-as-you-go model was a core part of their pitch to startups: scale up when you need it, scale down when you don’t.
But the actual commercial reality for many established cloud customers looked very different. To attract larger customers and lock in revenue, all three providers had shifted their sales strategy toward long-term committed-spend contracts — agreements where customers receive discounted pricing in exchange for guaranteed minimum annual spend over one or more years.
As of December 2019, those commitments were substantial:
- AWS reported US$29.8 billion in remaining performance obligations from contracts longer than one year.
- Google Cloud disclosed US$11.4 billion in future cloud revenue it planned to book from committed contracts.
- Microsoft sells both cloud services and much of its on-premises software via multiyear agreements, though it did not break out a comparable figure at that time.
For companies whose revenues had cratered, these committed minimums meant their cloud costs were essentially fixed — even as their businesses had stopped generating income.
The Gap Between Flexibility Promised and Flexibility Delivered
“Their revenues have sunk 50 percent or 60 percent, but their costs have remained static,” said Jason Kim, co-founder of Taloflow, a firm that advises businesses on managing AWS expenditure. Kim described the major cloud providers as having been “pretty radio silent” in response to customer appeals for relief.
Half a dozen startup executives interviewed for the original Bloomberg report said that outreach to cloud providers had gone unanswered. None of the three major providers — AWS, Microsoft, or Google — made public announcements about deferring or reducing bills for clients during this period.
According to a person familiar with the decisions cited in the original reporting, AWS was restructuring some large enterprise contracts on a case-by-case basis. Smaller companies, however, were not receiving the same treatment.
One example from the reporting illustrates Google’s position directly: when a California company asked Google Cloud for payment assistance, it was told the only available option was to suspend the account and reopen it 30 days later — essentially losing access to their infrastructure rather than receiving any payment flexibility. This was described in an April 1 email viewed by Bloomberg News.
A Google Cloud spokesperson declined to confirm details, stating: “We treat payment terms with our customers or partners as confidential and we’re not able to disclose details.”
An AWS spokesman acknowledged the difficulty but stopped short of announcing any specific relief program: “This is a very difficult time for some of our customers, and we are actively working across a number of dimensions to help them manage costs.” He also noted that customers can shut off cloud services more easily than they could decommission corporate-owned data centers.
According to a separate report by The Information, both Microsoft and Google did extend payment deadlines for at least some customers.
Contrast With Other Tech Vendors and Regulated Utilities
The restraint from major cloud providers stood in contrast to the actions of older technology companies. Cisco Systems, for example, publicly offered credits to customers facing financial hardship during the same period.
Regulated utilities offered a starker comparison. California state regulators moved to prohibit utility providers from cutting off power to customers who missed payments — treating electricity and water as essential services that could not be interrupted during a public health emergency.
Some smaller cloud and hosting providers took a more pragmatic approach. Pierre-Luc Quimper, CEO of GloboTech Communications — a Montreal-based company offering server and data management services — said that approximately 7 percent of clients had reported payment difficulties that month, and he expected that figure to rise. GloboTech had accommodated the vast majority of affected customers with deferred or staggered payment plans.
“The Internet is an infrastructure that’s become essential to our lives,” Quimper said. “We’re not interested in putting companies out of business just because they’re not paying for a month.”
What This Reveals About Cloud Contract Risk
The COVID-19 period exposed a structural risk that many cloud customers had not fully accounted for: the gap between the flexibility of on-demand cloud usage and the rigidity of committed-spend contracts. The very discounts that made long-term agreements attractive also created exposure when business conditions changed suddenly.
For DevOps and infrastructure teams advising their organizations on cloud strategy, the episode highlights several practical considerations:
- Understand your contractual commitments. Committed Use Discounts (CUDs) on Google Cloud, Savings Plans and Reserved Instances on AWS, and Azure Reserved VM Instances all carry minimum spend obligations. Know what you are locked into and for how long.
- Model downside scenarios. Before signing a multi-year committed contract, stress-test the minimum spend against scenarios where your product usage drops significantly.
- Negotiate exit clauses and flexibility upfront. It is far easier to negotiate force majeure provisions, ramp schedules, or early termination options before signing than after a crisis has begun.
- Diversify where possible. Dependence on a single cloud provider with a large committed contract creates concentration risk. Multi-cloud or hybrid approaches can reduce this exposure, though they carry their own operational complexity.
- Monitor FinOps continuously. Tools and practices around cloud financial operations (FinOps) help ensure your actual usage is aligned with your committed spend, reducing waste and over-commitment.
Cloud as Critical Infrastructure
The pandemic accelerated a debate that had been building for years: whether cloud computing has become critical infrastructure in the same sense as electricity, water, or telecommunications — and whether that status should come with corresponding regulatory obligations or protections for customers.
In 2020, that question went largely unanswered by governments and cloud providers alike. But for the startups caught between collapsing revenue and fixed cloud bills, it was not an abstract policy question. It was a matter of survival.
Original reporting by Bloomberg News, as published by Taipei Times, April 2020.