When Amazon Web Services’ US-EAST-1 region experienced a multi-hour outage on October 20, 2025, much of the public attention focused on the consumer impact. More than a thousand websites and applications spanning social media, banking, government services, video conferencing, and education saw disruptions as after an internal system failure at AWS triggered a chain reaction that affected hundreds of popular applications and online services. Recovery was uneven, and some applications remained impaired long after AWS initiated mitigation steps.
For healthcare leaders, the story was different. Outages of this scale are reminders that cloud infrastructure has become part of the operational core of modern healthcare. And because so many clinical and administrative systems are now hosted on or indirectly dependent on hyperscale cloud platforms, even a non-security incident can quickly translate into delays, inefficiencies, and increased operational strain.
In today’s healthcare environment, cloud services remain foundational to innovation, affordability, and scalability. But the AWS outage made clear that the sector has not fully accounted for the blast radius created when a highly centralized cloud architecture meets a highly interconnected healthcare environment.
The Power of One: Redefining Healthcare with an AI-Driven Unified Platform
In a landscape where complexity has long been the norm, the power of one lies not just in unification, but in intelligence and automation.
The question is no longer whether the cloud is reliable enough for healthcare. It is whether healthcare organizations are architected to remain reliable when a major cloud provider experiences a sudden, widespread failure.
What actually happened and why the impact was so broad
The October 20 outage originated inside Amazon’s U.S. East cloud region which is one of the busiest cloud hubs in the world. A core internal system failed, and because so many services rely on that system to operate, the disruption spread quickly across major applications and tools.
Even organizations that weren’t directly using the affected service still felt the effects because their applications depended on other cloud functions that slowed down or stalled. In other words, a single failure point created a chain reaction across a large portion of the cloud ecosystem.
RCM Outsourcing: Balancing Human Expertise & Smart Technology
Greenway Health blends smart technology with human expertise to elevate revenue cycle.
What’s important for healthcare leaders to understand is nothing about the incident was malicious. It was a routine technology failure inside a highly mature cloud environment. But the breadth of the disruption showed how dependent the world (not just healthcare) is on a small number of cloud regions operating flawlessly.
This wasn’t a cybersecurity event, yet it still created meaningful operational impact. That is the core challenge healthcare must confront.
Healthcare felt the impact even without a catastrophic failure
Several healthcare organizations publicly reported effects from the outage. These weren’t all headline-grabbing events, but they were operationally meaningful.
In the U.K., at least ten NHS sites using Oracle systems hosted on AWS entered downtime scenarios. Trusts temporarily reverted to paper workflows, and digital health leaders described the incident as disruptive to patient care across multiple locations.
In the United States, Tufts Medicine reported system slowdowns and delays in processing lab results, noting that clinical care continued but workflows were impacted.
And in New York, Westchester Medical Center communicated that its physician practice call center and scheduling systems were taken offline due to the global AWS outage.
These examples share a pattern: outages that did not rise to the level of crisis still created operational friction. A delayed lab result may not be a life-threatening event, and a call center outage may not halt care delivery. But each one represents lost productivity, slower throughput, schedule disruption, and increased administrative burden.
In an industry already operating with tight margins and workforce shortages, even short periods of cloud-related downtime can become costly.
The hidden dependencies executives cannot afford to ignore
What the AWS outage demonstrated is that healthcare organizations are more dependent on underlying cloud infrastructure than many realize. This dependency isn’t just about the systems they explicitly migrate to cloud platforms. It includes:
1. Third-party SaaS providers
Many clinical and administrative tools run on cloud infrastructure without the customer ever seeing that dependency. A single region’s degradation can impact applications that hospitals assume are geographically redundant.
2. Legacy applications refactored “just enough” to run in the cloud
Applications lifted into the cloud without architectural modernization often remain tightly coupled to a single region or availability zone.
3. Region monoculture
For reasons of convenience, cost, and historic defaults, many healthcare workloads (both direct and inherited) run in US-EAST-1. The outage exposed how concentrated the industry’s cloud footprint has become.
4. Limited visibility into cloud architecture
Executives and even security teams frequently cannot see:
- which assets are exposed externally,
- how identities and permissions are structured,
- where misconfigurations create unnecessary risk,
- or how dependencies chain across cloud services.
This is not an indictment of cloud technology. It is an acknowledgment that healthcare’s rapid cloud adoption often outpaced cloud governance.
The business cost of cloud fragility
Downtime in healthcare rarely shows up as a single major number on a financial statement. It accumulates in smaller, harder-to-track ways:
- A morning of delayed lab results can ripple into slower discharge times.
- An offline scheduling system can create appointment backlogs that take days to clear.
- Manual workarounds increase labor hours.
- Interruptions to revenue-cycle tools delay claims and payment cycles.
- IT teams are diverted to troubleshooting instead of strategic work.
Analysts estimate the global direct business impact of the AWS outage in the hundreds of millions of dollars. Healthcare’s share of that is difficult to quantify, but the operational effects are undeniable.
When an outage in a cloud region thousands of miles away affects scheduling, lab workflows, or access to patient portals, it raises an important set of questions for healthcare boards and executives:
- Where are our single points of failure?
- How resilient are the cloud services our vendors depend on?
- How quickly can we detect and respond to misconfigurations or outages?
- Do we have the visibility to understand our cloud footprint in real time?
These are governance questions as much as technical ones.
Where healthcare leaders go from here
No cloud architecture can eliminate outages entirely. The goal for healthcare organizations should be to reduce blast radius, improve visibility, and build operational resilience.
1. Improve architectural resilience
Healthcare systems should review whether mission-critical workloads rely on a single region or availability zone. Multi-region replication, improved failover design, and vendor transparency are all part of reducing dependency risk.
2. Modernize cloud governance
Cloud environments evolve quickly. New services get deployed, identities proliferate, and configurations drift over time. Without continuous monitoring and strong controls, organizations cannot effectively manage cloud risk.
3. Adopt Cloud Security Posture Management (CSPM)
CSPM solutions provide visibility into cloud assets, configuration drift, identity structures, region-level dependencies, and potential exposure points. They serve as an early warning system and a governance tool for leadership, not just a security product.
4. Update downtime and continuity planning for cloud realities
Most healthcare organizations have robust plans for ransomware or EHR downtime. Fewer have plans for cloud service degradation, API failures, or third-party SaaS outages. The AWS incident demonstrated that these scenarios are now part of normal operating risk.
A more realistic framework for cloud resilience
The AWS outage did not break healthcare, and it did not represent a systemic failure. But it was a timely reminder that cloud resilience is not simply a technical concern. It is a leadership responsibility tied directly to operational stability, financial performance, and the continuity of care.
Cloud adoption will continue, and it should. But as more of the healthcare ecosystem depends on large-scale cloud providers, executive teams must ensure they have the visibility, governance, and architectural resilience to withstand the next unplanned disruption whether it lasts minutes or hours.
The goal is not to predict every outage. It is to build an environment where an outage in a distant cloud region does not have an outsized operational impact on hospitals and the communities they serve.
Photo: shylendrahoode, Getty Images
Baxter Lee is President of Clearwater. He was promoted to President in September 2025 after serving as Clearwater CFO beginning in May 2018. Mr. Lee is responsible for leading the company’s strategic growth plan and managing the company’s overall operations.
Formerly, Mr. Lee was CFO of Entrada Health, a mobile health documentation and productivity platform for healthcare providers, acquired by NexGen Healthcare (NASDAQ: NXGN) in 2017. Before his role with Entrada, Lee held multiple positions with Change Healthcare (fka Emdeon), a multi-billion dollar healthcare IT company. His roles included divisional CFO of the Ambulatory and Payer Services divisions and director of corporate development. He focused on mergers, acquisitions, and corporate strategy across Emdeon’s four operating divisions. Prior to joining Emdeon, Mr. Lee was an associate in the Private Equity Group at Harbert Management Corporation and assistant vice president of underwriting in the Healthcare Finance Group at Merrill Lynch Capital.
This post appears through the MedCity Influencers program. Anyone can publish their perspective on business and innovation in healthcare on MedCity News through MedCity Influencers. Click here to find out how.