Billions Lost, Multi-Cloud Is Wall Street’s Solution

On Monday, Oct. 20, a widespread outage at Amazon Web Services reverberated through the global economy, offering a stark reminder of the financial industry’s deep dependence on a handful of tech giants. The disruption, primarily centered on AWS’s massive US-EAST-1 region in northern Virginia, caused connectivity issues and elevated error rates for thousands of companies worldwide, immediately disrupting financial services from trading platforms to consumer banking apps.

The incident, attributed by AWS engineers to an issue within the EC2 internal network and later tied to a Domain Name System failure, quickly became a global systemic risk test for finance. Cryptocurrency exchange Coinbase and stock trading app Robinhood both reported service issues, throttling the ability of millions of users to execute trades and manage assets. Payment processor Venmo also saw disruption reports surge, illustrating how a single cloud failure can freeze the flow of digital currency. Across the Atlantic, British institutions, including Lloyds Bank and Bank of Scotland, experienced problems, highlighting the cross-border fragility of modern banking infrastructure.

The financial toll of such events is immense. Mehdi Daoudi, CEO of internet performance monitoring firm Catchpoint, told Al Jezeera that the financial impact of the outage could “easily reach into the hundreds of billions” due to lost productivity and halted business operations. For an industry that measures success in milliseconds and relies on uninterrupted global connectivity, even an eight-hour disruption is catastrophic. The incident underscored the concern among financial regulators that placing too many mission-critical functions in one basket creates unacceptable concentration risk.

Learn more from Forbes, The Data Centers Powering AI Boom In Financial Services.

AWS: The Hidden Engine of Modern Finance

The reason the AWS disruption causes such a deep tremor is that its services are not merely hosting static bank websites; they power the financial industry’s most critical, real-time functions. Over the past decade, financial institutions have aggressively migrated core systems and data infrastructure to the cloud, seeking the speed, agility and resilience promised by Amazon’s platform.

AWS is embedded in everything from personalized wealth management to fraud detection. Institutions like HSBC have implemented cloud-first strategies for their Wealth and Personal Banking divisions, shifting core infrastructure to AWS to allow for rapid innovation and scalable delivery. In capital markets, organizations like the Financial Industry Regulatory Authority, or FINRA, rely on the platform to crunch billions of market events daily for surveillance.

Specifically, AWS databases are foundational. Banks use services like Amazon DynamoDB for high-volume payments and securities transactions, which require low latency and immense throughput. Others leverage Amazon Aurora for core banking systems, seeking its highly fault-tolerant storage architecture, which spans multiple Availability Zones to prevent downtime. The promise of the cloud was always greater resilience, but as experts noted, the outage demonstrates the danger of relying on only one hyper-scaler.

More like this on Forbes, When Payments Become Strategy, Not Just Plumbing.

The Multi-Cloud Solution

In the wake of this and previous outages, financial services firms are intensifying efforts to future-proof their operations and eliminate the single point of failure that a massive regional AWS outage represents. The strategy gaining the most traction is multi-cloud, distributing critical workloads across two or more major providers, such as AWS, Microsoft Azure and Google Cloud.

This strategy is no longer optional; it is becoming a regulatory necessity. In the United Kingdom, regulations like the Bank of England’s SS2/21 emphasize the need for financial institutions to have detailed “stressed exit” plans. These plans require banks to demonstrate how they can maintain operational continuity and shift critical services to a different provider, or even back on-premises, if a key third-party vendor fails or exits the market. The European Union’s Digital Operational Resilience Act, or DORA, similarly mandates robust defenses against cloud concentration risk.

To achieve true multi-cloud resilience, firms are focusing on three strategic pillars:

1. Workload Portability: Moving away from proprietary, vendor-specific cloud services toward open data standards and APIs. This ensures that a crucial application can be deployed instantly to a different provider without requiring a complete code overhaul.

2. Automated Failover: Implementing automated systems that monitor cloud health across providers and reroute transaction traffic seamlessly to the backup cloud in the event of an outage, ideally without customers even noticing a disruption.

3. Data Sovereignty and Residency: Using multi-cloud solutions to adhere to global regulations that require data on citizens to be stored in specific geographic locations.

This AWS disruption serves as a severe, real-world stress test. While the agility and efficiency of cloud computing are indispensable, the incident reinforces a powerful lesson: For the financial services industry, true resilience requires breaking vendor dependence and building systems designed to survive when any single cloud, even the largest one, inevitably falls dark.

Follow Holloman to learn more about the future finance and technology.