What cloud is
A collection of network accessible resources delivered on demand and administered through software.
CLOUD SOLUTIONS
Understandthe cloud.Build withconfidence.
Cloud lets you use applications, storage, and servers over the internet without installing everything in your office. The equipment still exists, but it is operated in specialized data centres.
- Provider neutral
- Security by design
- Planned resilience
- 01You make a request
Your phone or computer connects over the internet.
- 02Your access is verified
The service confirms your identity before letting you in.
- 03Cloud responds
Servers in a data centre run the application.
- 04Your data stays recoverable
A separate backup helps recover data after an incident.
UNDERSTAND THE FOUNDATION
Cloud is a way to deliver computing.
Your data still lives on physical servers, storage systems, and networks. What changes is how those resources are reserved, automated, distributed, and billed.What it is not
An automatic backup, a security guarantee, or a universal answer to every problem.
UserInternetCloud regionResources
A data centre
A secured building containing servers, storage, network equipment, power, and cooling.
Example: the physical computers that run an application.A region
A geographic area selected to host services. It contains one or more connected data centres.
Example: choosing Canada to meet a data residency requirement.An availability zone
A physically separate group within a region. Using multiple zones can limit the impact of a local failure.
Important: this redundancy must be selected and configured. It is not implicit for every service.CONCRETE EXAMPLE
An employee opens the payroll application from home.
Here is what happens in a few seconds.- 1The request travels over the internet
The browser finds the service through DNS, the directory that maps a name to a network destination.
- 2Identity is verified
The service checks the password, MFA, device condition, and access rules before opening the session.
- 3The application processes the request
A gateway filters traffic. A load balancer then sends the request to an available application instance.
- 4Authorized data is returned
The application queries the database with limited permissions. The connection and storage are encrypted.
- 5The service is observed and recoverable
Logs, metrics, and alerts help detect problems. Separate backups support restoration after loss or corruption.
WHY BUSINESSES MOVE
Create capacity without losing control.
Scalability
Adjust capacity with demand without buying all infrastructure in advance.
Distributed access
Make applications available to authorized teams, partners, and customers.
Continuity
Distribute services and prepare recovery when disruption occurs.
Faster delivery
Deploy repeatable environments in minutes instead of weeks.
Optimization
Measure usage and align resources with actual needs.
Automation
Reduce manual work with policies, templates, and controlled workflows.
CHOOSE THE RIGHT MODEL
Public, private, hybrid, or multicloud?
The right model depends on workloads, data, skills, latency, and obligations. One organization may use several at the same time.Public cloud
Rapid growth and global reachBroad catalogue, flexible capacity, rapid deployment.
Cost and access governance must be rigorous.
Private cloud
Specialized control or strict constraintsGreater control of the platform and location.
Investment, expertise, and operations remain your responsibility.
Hybrid cloud
Progressive modernizationConnects local systems to cloud services according to their role.
Identity, networking, and dependencies become more complex.
Multicloud
Distinct needs across providersService choice and reduced dependency in selected areas.
Requires shared standards, visibility, and strong skills.
Infrastructure on demand
You manage systems, applications, and data. The provider operates hardware and virtualization.
Like renting an empty space: the structure exists, but you furnish and maintain the inside.Managed platform
You deliver code and data. The provider manages more of the system and runtime.
Like renting an equipped kitchen: you prepare the meal without maintaining the building or appliances.Ready-to-use software
You configure users, access, and data in an application operated by the provider.
Like booking a hotel room: the service is ready, but you remain responsible for your belongings and access.Event-driven functions
Small functions run only when an event invokes them.
Like calling a service only when needed, then stopping payment when the task is complete.MODERN CLOUD ARCHITECTURE
A secure, observable, and recoverable path.
Architecture should not be a simple chain. Security, logging, and governance surround every layer, while backup and recovery form an independent path.Monitoring, logs, and alertsPolicy, encryption, and secretsBackup, testing, and recovery
Containers
Package an application and its dependencies for consistent execution. Docker commonly builds and runs these units.
Kubernetes
Orchestrates containers, capacity, availability, and updates.
Serverless
Runs code or services without directly administering the underlying servers.
CDN & Edge
Moves content and selected processing closer to users to reduce latency.
Infrastructure as code
Describes infrastructure in versioned files using Terraform, Ansible, or native tools.
GitOps
Uses a Git repository as the controlled source for environment changes.
Object and block storage
Object storage suits files and archives. Block storage often supports system disks and databases.
Observability
Combines metrics, logs, and traces to understand service health and behavior.
SECURITY AND RESPONSIBILITY
The provider secures the cloud. You secure what you put in it.
The exact boundary changes across IaaS, PaaS, and SaaS, but your identities, permissions, data, and decisions always matter.IAM
Identity and access management determines who can do what, on which resource, and under what conditions.
Zero Trust
Never grant implicit trust. Verify identity, device, context, and risk level.
Encryption and keys
Protect data in transit and at rest, then separately control the keys that unlock it.
Secrets
Keep passwords, tokens, and certificates in a dedicated vault, never in code.
Logs and detection
Centralize activity to detect abnormal behavior and support investigations.
Data protection
Apply classification, loss prevention, independent backup, and restore testing.
CLOUD PROVIDER
Security of the platform
- Data centres and hardware
- Physical infrastructure
- Managed services according to contract
SHARED RESPONSIBILITY
The boundary moves with the service selected.
YOUR ORGANIZATION
Security of your use
- Accounts, roles, and permissions
- Applications, data, and configurations
- Backup, compliance, and documentation
BEST PRACTICE CHECKLIST
Eight controls to verify now.
- Enable multifactor authentication for everyone, especially administrators.
- Separate everyday accounts from privileged accounts.
- Grant least privilege and review permissions regularly.
- Block public sharing by default and document exceptions.
- Enable logs before an incident and define who reviews them.
- Encrypt sensitive data and protect keys separately.
- Back up critical data outside the primary platform.
- Test recovery against acceptable time and data loss objectives.
CLOUD MISCONCEPTIONS
Simple phrases that hide important responsibilities.
“The cloud automatically backs up everything.”
Service availability, retention, and independent backup are three different things.
“The cloud is always cheaper.”
It can optimize cost, but abandoned resources, transfers, and oversized architectures create waste.
“The provider protects all my data.”
The provider secures its platform. You retain major responsibilities for access, configuration, and data.
“The cloud replaces cybersecurity.”
It provides powerful controls, but they must be configured, monitored, and governed correctly.
DID YOU KNOW?
Many cloud incidents begin with a compromised account or excessive permission, not a platform flaw. Resilience also depends on independent, tested backup.
AI, USE CASES, AND THE FUTURE
Cloud is becoming the foundation for intelligent operations.
Cloud services provide access to GPUs, AI models, agents, vector databases, and automation tools. Value comes from integrating them with trusted data, access controls, and clear human processes.From model to useful capability
An LLM generates language. RAG gives it selected sources. A vector database helps retrieve information. An agent can call tools according to rules. Inference is when the model produces a result.
DataRAGLLMHuman review
- 01
Virtualization
Use hardware efficiently.
- 02
Containers
Make applications portable.
- 03
Kubernetes
Orchestrate at scale.
- 04
Serverless
Run on demand.
- 05
AI and GPU
Access specialized computing.
- 06
Edge
Process closer to the source.
- 07
Confidential cloud
Protect data while it is being processed.
- 08
Intelligent operations
Automate with context and policy.
CLOUD GLOSSARY
Essential terms in plain language.
- IaaS
- Computing infrastructure rented on demand.
- PaaS
- Managed platform for building and running applications.
- SaaS
- Complete application accessed as a service.
- IAM
- Management of identities and permissions.
- VNet / VPC
- Logical private network within a cloud provider.
- Subnet
- Network segment that organizes and isolates resources.
- API
- Controlled interface that allows software to communicate.
- CDN
- Network that delivers content from nearby locations.
- Container
- Lightweight unit containing an application and its dependencies.
- Kubernetes
- Container orchestration system.
- Zero Trust
- Model that verifies every request instead of trusting the network.
- RAG
- Method that provides selected sources to AI before it responds.
FAQ
Common cloud questions.
Direct answers for better architecture and governance decisions.Where does cloud data actually live?+
In physical data centres operated by a provider or organization. Region, replication, and data residency should be selected according to technical, contractual, and regulatory needs.
Is public cloud secure?+
It can provide very strong controls. The outcome still depends on design, identities, permissions, configuration, monitoring, and customer practices.
Should everything move to the cloud?+
No. Each workload should be assessed for dependencies, latency, cost, data requirements, resilience, and business value.
What is the difference between high availability and backup?+
High availability keeps a service running through selected failures. Backup preserves a recoverable copy after deletion, corruption, or attack. Both are needed.
How do we control cloud cost?+
Assign owners, use tags, define budgets and alerts, measure usage, right-size resources, and remove what no longer provides value.
What is shared responsibility?+
The provider protects the infrastructure it operates. The customer remains responsible for several areas, notably data, identities, permissions, and a varying share of configuration depending on the service used.
CLOUD STRATEGY