Cloud Infrastructure

Architecture begins with requirements

Define workload characteristics, data sensitivity, availability targets and expected demand before selecting a hosting model. Avoid assuming every application needs the same architecture.

Security is a shared responsibility

Cloud providers secure parts of the underlying service while customers remain responsible for configurations, identities, data and application controls according to the service model.

Operate for resilience

Use monitoring, documented changes, tested backups and access reviews. Understand the cost and recovery implications of each dependency.

Practical review checklist

• Define the business objective and the owner accountable for decisions.
• Document the current position and relevant dependencies.
• Assess security, operational and legal implications before making changes.
• Set measurable outcomes and a date to review results.
• Maintain records of approvals, exceptions and lessons learned.

These are general considerations; the appropriate approach depends on the organization, sector and applicable requirements.

Related resources