Risks and Dependencies of Cloud InfrastructureActivities & Teaching Strategies
Active learning works for this topic because students need to see how cloud dependencies affect real systems and people. Mapping their own digital day, reverse-engineering an outage, or designing recovery plans makes abstract risks visible and consequential.
Learning Objectives
- 1Analyze the market concentration of major cloud infrastructure providers and identify the associated risks.
- 2Evaluate the potential impact of a widespread cloud service outage on interconnected global businesses and services.
- 3Justify the necessity of multi-cloud strategies and disaster recovery plans for ensuring digital resilience.
- 4Critique the policy implications of critical national infrastructure relying on a limited number of private cloud providers.
Want a complete lesson plan with these objectives? Generate a Mission →
Dependency Mapping: Your Digital Day
Students list every digital service they used in the past 24 hours. Using a provider lookup guide, they trace each service to its underlying cloud provider. The class aggregates results on a shared board, revealing how concentrated their collective digital lives actually are.
Prepare & details
Critique the risks of relying on a small number of companies for cloud infrastructure.
Facilitation Tip: During Dependency Mapping: Your Digital Day, ask students to trace every app they used in the last 24 hours back to a cloud provider and document the steps aloud to surface hidden dependencies.
Setup: Groups at tables with case materials
Materials: Case study packet (3-5 pages), Analysis framework worksheet, Presentation template
Case Study Analysis: The AWS Outage
Groups analyze the December 2021 AWS us-east-1 outage: what failed, which services went down, and why. They map the organizational response and identify which companies had adequate redundancy versus those that were completely offline. Each group proposes what adequate redundancy would have required.
Prepare & details
Predict the impact of a major cloud service outage on global operations.
Facilitation Tip: For the Case Study Analysis: The AWS Outage, have students annotate a timeline with colored bars showing which companies were affected and when, so they see how one technical failure propagates.
Setup: Groups at tables with case materials
Materials: Case study packet (3-5 pages), Analysis framework worksheet, Presentation template
Design Challenge: Disaster Recovery Architecture
Groups receive a scenario: 'You are the CTO of a hospital. Your electronic health record system runs on a single AWS region.' They design a disaster recovery plan meeting a 4-hour recovery time objective, justify their architectural choices, and estimate the approximate cost increase.
Prepare & details
Justify the need for redundancy and disaster recovery plans in cloud architecture.
Facilitation Tip: When running the Design Challenge: Disaster Recovery Architecture, provide a limited set of building blocks (regions, providers, backup tools) so students focus on trade-offs rather than tool selection.
Setup: Groups at tables with case materials
Materials: Case study packet (3-5 pages), Analysis framework worksheet, Presentation template
Socratic Seminar: Should Governments Regulate Cloud Concentration?
Students read two short articles before class: one arguing for regulatory intervention on critical cloud dependencies, one arguing market forces will drive adequate redundancy. The student-led seminar explores what counts as critical infrastructure and who bears responsibility for outages.
Prepare & details
Critique the risks of relying on a small number of companies for cloud infrastructure.
Facilitation Tip: In the Socratic Seminar: Should Governments Regulate Cloud Concentration?, seat students in concentric circles to rotate perspectives and ensure quieter voices are heard.
Setup: Chairs arranged in two concentric circles
Materials: Discussion question/prompt (projected), Observation rubric for outer circle
Teaching This Topic
Teach this topic through layered examples that move from personal to global scale. Start with students’ own devices and apps to build intuition, then use a documented failure to make risk concrete. Avoid letting discussions drift into vendor comparisons; keep the focus on dependency and resilience patterns. Research shows that when students articulate failure modes in their own words, they retain concepts longer than when they only hear technical definitions.
What to Expect
Successful learning looks like students explaining why cloud concentration matters, identifying single points of failure in familiar apps, and proposing feasible resilience strategies. They should connect technical language (regions, SLAs, outages) to lived experiences of downtime.
These activities are a starting point. A full mission is the experience.
- Complete facilitation script with teacher dialogue
- Printable student materials, ready for class
- Differentiation strategies for every learner
Watch Out for These Misconceptions
Common MisconceptionDuring Dependency Mapping: Your Digital Day, watch for students assuming every app they use is stored in the cloud.
What to Teach Instead
Use the mapping activity to explicitly ask students to distinguish local storage from cloud storage and to identify which services rely on cloud providers for delivery, even if the data is stored locally.
Common MisconceptionDuring Design Challenge: Disaster Recovery Architecture, watch for students believing that adding a backup in the same cloud region is sufficient protection.
What to Teach Instead
Have students test their design by simulating a region-wide outage and observing whether their backup is also inaccessible, then revise their architecture to include geographic separation.
Assessment Ideas
After Dependency Mapping: Your Digital Day, display a word cloud of the cloud providers students identified and ask them to explain which dependencies surprised them most.
During Case Study Analysis: The AWS Outage, circulate and check that students can identify at least two companies affected by the outage and explain the technical cause in their own words.
After Design Challenge: Disaster Recovery Architecture, collect student diagrams and ask them to write one sentence explaining why their chosen strategy reduces single points of failure.
Extensions & Scaffolding
- Challenge: Ask students to propose a policy to reduce cloud concentration risk and present it to a mock regulatory body using evidence from the case study.
- Scaffolding: For the disaster recovery design, provide a partially completed diagram that students must revise with cross-region or multi-cloud alternatives.
- Deeper exploration: Have students research a smaller cloud provider (e.g., Oracle Cloud, IBM Cloud) and compare its outage history and geographic footprint to the Big Three.
Key Vocabulary
| Cloud Infrastructure | The hardware and software components that provide cloud computing services, including servers, storage, and networking, managed by providers like AWS, Azure, and GCP. |
| Market Concentration | A situation where a large portion of the market share is controlled by a small number of companies, leading to potential dependencies. |
| Single Point of Failure | A component or system whose failure would cause the entire system to stop functioning, a significant risk with concentrated cloud providers. |
| Disaster Recovery Plan | A documented process or set of procedures to recover and protect a business's IT infrastructure in the event of a disaster or extended outage. |
| Multi-Cloud Architecture | The use of cloud computing services from more than one cloud provider to host applications and data, enhancing resilience. |
Suggested Methodologies
More in The Architecture of the Internet
Internet Infrastructure and IP Addressing
Students will understand how IP addresses and routers manage the flow of packets across a decentralized network.
2 methodologies
Network Protocols and Communication
Students will investigate the necessity of standardized protocols for global communication.
2 methodologies
Physical Limitations of Data Transmission
Students will explore the physical limitations of sending data across the world at high speeds.
2 methodologies
Symmetric and Asymmetric Encryption
Students will investigate methods for protecting data integrity and privacy through encryption.
2 methodologies
Cybersecurity Threats and Defenses
Students will identify common cybersecurity threats and explore various defense mechanisms.
2 methodologies
Ready to teach Risks and Dependencies of Cloud Infrastructure?
Generate a full mission with everything you need
Generate a Mission