Cloud computing
Understand cloud services through their operating model, resource lifecycle, and the identity, data, and recovery decisions that remain with customers.
The idea
Cloud computing provides computing resources as services rather than requiring customers to own every underlying component. Service models include infrastructure, platform, and software offerings. Public, private, and hybrid deployments describe different arrangements. Elasticity and managed operation can help delivery, but customers still need to manage identities, data, configuration, and their contractual responsibilities. Know which service you use before deciding who patches or secures each layer.
In practice
A team uses a hosted collaboration service instead of running a mail server, yet still manages user access, sharing, retention, and account-security settings.
A common misunderstanding
Moving to the cloud does not transfer every security responsibility to the provider.
Check your understanding
What determines the security division?
Think it through: The specific service model, product, configuration, and agreement—not merely the word “cloud.”
Follow a service rather than a buzzword
Imagine a fictional academy replaces a locally operated collaboration server with a hosted document service. The team no longer manages the same machines, but it still decides who may sign in, which documents may be shared, and how long learner records should remain.
The change redistributes work instead of removing every responsibility. Start with the service's actual capabilities, agreement, and configuration. Cloud terminology helps organize the discussion, while the product documentation explains the precise operational boundary.
Elastic resources still need governance
Suppose a team can create temporary development environments quickly. That flexibility supports experimentation, but forgotten identities, storage, and public endpoints can outlive the original project. Track resource ownership and removal conditions alongside creation.
An automatically scaling application can also scale resource consumption during a malfunction or abusive workload. Budgets, limits, and monitoring should match the business requirements rather than assuming elasticity is an unrestricted availability guarantee.
Plan data movement and exit
A hosted application becomes a dependency for everyday work. Understand export formats, restoration, retention, and the effects of account closure before an incident makes those questions urgent. A provider's backup capability may solve a different problem from recovering one customer's accidentally deleted record.
For the academy, test a small non-sensitive export and verify that the team can interpret and reuse it. Record the identities and keys needed for recovery. This makes the service's benefits compatible with a realistic continuity plan.
For a paper exercise, compare the local server and hosted service using five responsibilities: maintenance, access, sharing, monitoring, and recovery. Assign an owner to each in both arrangements. Explain which tasks changed and which remain with the academy. The useful understanding is the new operating model and its dependencies, not merely where the hardware is located.
Keep exploring
References & further reading
Original explanations, with primary references for deeper study.
AWS: Shared Responsibility ModelNIST: Definition of Cloud Computing