LFCA 73 🐧 Major Cloud Providers — AWS, Azure, GCP
The previous chapters covered what cloud computing is and how the three service models — IaaS, PaaS, and SaaS — divide responsibility between the provider and the consumer. This chapter is about the three companies that dominate that market: Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). They are called the “hyperscalers” because of the scale of their infrastructure, and together they account for roughly two-thirds of global cloud infrastructure spending .
The LFCA exam places this topic under Cloud Computing Fundamentals, which carries 18–20% of the total weight . The study plan explicitly lists “Cloud provider overview: AWS, Azure, GCP” as a topic for Week 2 . The exam does not expect deep knowledge of any single provider’s services. It expects you to know what each provider is, where its strengths lie, and which use cases it naturally fits.
Key point: The three providers are not interchangeable. AWS is the oldest and broadest, with the largest service catalog and the deepest ecosystem. Azure is the strongest for organizations already using Microsoft software — Windows, Active Directory, Office 365, .NET. GCP is the strongest for AI and machine learning workloads, with custom TPU chips and BigQuery analytics . The “best” provider is the one that matches the organization’s existing stack and workload requirements.
Why the provider choice matters
Choosing a cloud provider is not a permanent decision, but it is a consequential one. The provider’s services, pricing model, regional footprint, and compliance certifications shape what the organization can build and how much it costs to run.
The ecosystem problem. An organization already using Windows Server, Active Directory, and SQL Server will find Azure offers the smoothest path. The existing licenses can be reused through Azure Hybrid Benefit, the identity system integrates natively with Entra ID, and the development tools are the same ones the team already knows . An organization building cloud-native applications on Linux will find AWS or GCP equally natural. The provider that matches the existing stack reduces friction and training costs.
The AI and data problem. AI and machine learning are now the primary drivers of cloud growth. Google Cloud’s investment in TPUs (Tensor Processing Units) — custom chips designed for machine learning — and its Vertex AI platform give it a genuine advantage for AI workloads . Azure’s partnership with OpenAI gives it exclusive access to GPT models with enterprise controls, making it the natural choice for organizations building on large language models within the Microsoft ecosystem . AWS has the broadest set of GPU instances and the most mature ML platform in SageMaker, but its AI differentiation is less sharp than the other two .
The cost problem. GCP is generally 5–10% cheaper than AWS for equivalent compute, and its automatic sustained-use discounts remove the need for upfront commitments . Azure’s pricing sits in the middle, but Azure Hybrid Benefit can dramatically reduce costs for Microsoft-stack shops . AWS has the deepest maximum discounts for organizations willing to commit to long-term reserved instances, but its on-demand pricing is the highest of the three . The cheapest provider depends on the workload and the commitments.
The lock-in problem. Every provider has proprietary services that make migration expensive. Moving from one provider to another is not impossible — all three now waive egress fees for migrations — but it is a significant project. The organization should choose a provider with the expectation of staying for years, while designing systems that minimize dependence on provider-specific services where possible.
The trade-off. There is no objectively best provider. AWS has the largest market share and the broadest ecosystem. Azure has the strongest enterprise integration. GCP has the strongest AI and data tooling. The right choice depends on what the organization already has, what it is building, and what it values.
a. AWS — The Market Leader
Amazon Web Services launched in 2006 and was the first major public cloud. It has been the market leader since the cloud infrastructure market formed, and it remains the largest provider by revenue . In Q2 2026, AWS generated $42.2 billion in revenue, representing a $169 billion annual run rate, and held 28% of the global cloud infrastructure market .
The breadth of AWS’s service catalog is its defining characteristic. It offers more than 240 services covering compute, storage, databases, networking, analytics, machine learning, security, and developer tools . For almost any cloud requirement, AWS has a managed service. This breadth is valuable for organizations that want to avoid managing infrastructure themselves and prefer to assemble applications from managed building blocks.
AWS’s strengths are:
Service breadth. The largest catalog of managed services of any provider. If a service exists in the cloud, AWS likely has it .
Compliance certifications. The broadest portfolio of compliance certifications — SOC, ISO, PCI DSS, FedRAMP, HIPAA, and country-specific frameworks. AWS GovCloud provides dedicated infrastructure for US government workloads .
GPU and custom silicon. The widest selection of GPU instances, including NVIDIA H100s, plus custom chips: Trainium for training and Inferentia for inference .
Ecosystem and talent. The largest partner network, the most third-party tools, and the largest pool of engineers who already know AWS .
AWS’s weaknesses are:
Highest on-demand pricing. AWS’s on-demand compute is generally the most expensive of the three .
Billing complexity. More overlapping discount mechanisms — Savings Plans, Reserved Instances, Spot — than the other providers, which makes cost forecasting harder .
EKS control plane fee. AWS is the only one of the three that charges for its managed Kubernetes control plane .
AWS is the natural choice for organizations that value the broadest possible toolset, need the most mature compliance story, or are already invested in AWS certifications and tooling.
b. Azure — The Enterprise Integration Provider
Microsoft Azure launched in 2010, four years after AWS, and has grown to become the second-largest provider. In Q2 2026, Microsoft’s Intelligent Cloud segment (which includes Azure) generated $39.3 billion in revenue, and Azure held 20% of the global cloud market . Microsoft does not report Azure revenue separately; it is included in the Intelligent Cloud segment .
Azure’s defining characteristic is its integration with Microsoft’s enterprise software. Organizations that already use Windows Server, Active Directory (now Entra ID), SQL Server, Office 365, or .NET find that Azure offers technical continuity that neither AWS nor GCP can match . Existing Microsoft licenses can be reused through Azure Hybrid Benefit, which can reduce costs significantly .
Azure’s strengths are:
Microsoft ecosystem integration. Native integration with Microsoft 365, Teams, Entra ID, SQL Server, and Dynamics 365. Existing licenses are reusable through Azure Hybrid Benefit .
Hybrid cloud maturity. Azure Arc and Azure Stack are the most mature solutions for managing hybrid architectures that span on-premises infrastructure and multiple clouds .
OpenAI partnership. Azure OpenAI Service provides enterprise access to GPT models with Microsoft’s security, compliance, and networking controls. This is the strongest AI offering for organizations already in the Microsoft ecosystem .
Regional footprint. Azure has the widest regional footprint of the three providers, with 60+ regions, which matters for data residency and sovereignty requirements .
Azure’s weaknesses are:
Service maturity. Some individual services are less mature than their AWS equivalents, particularly for newer AI-related offerings .
Documentation consistency. Documentation quality is less consistent across services than AWS’s .
Portal complexity. The Azure portal and tooling draw frequent complaints from platform teams .
Azure is the natural choice for organizations already using Microsoft software, government agencies, and enterprises with hybrid cloud requirements.
c. GCP — The AI and Data Specialist
Google Cloud Platform launched in 2008 as Google App Engine and grew into a full cloud platform. It is the smallest of the three providers by market share, holding 15% in Q2 2026, but it is also the fastest-growing . Google Cloud generated $24.8 billion in revenue in Q2 2026, an 82% year-over-year increase, and reached a $99 billion annual run rate .
GCP’s defining characteristic is its strength in AI, machine learning, and data analytics. Google invented Kubernetes and TPUs, and its data warehouse BigQuery is widely considered the best in the market . The company’s full-stack AI strategy — custom chips, frontier models (Gemini), and integrated tooling — has driven its rapid growth .
GCP’s strengths are:
AI and ML tooling. Vertex AI, BigQuery ML, and TPU access. Google’s custom TPUs deliver strong price-performance for training large models, and they are not available from any other provider .
BigQuery. Widely regarded as the best cloud data warehouse for price-performance and ease of use. For many data teams, BigQuery alone justifies choosing GCP .
Kubernetes maturity. Google invented Kubernetes, and GKE is considered the most operationally mature managed Kubernetes service .
Pricing. GCP is generally 5–10% cheaper for equivalent compute than AWS, with automatic sustained-use discounts that require no commitment .
GCP’s weaknesses are:
Smallest service catalog. About 150+ services versus AWS’s 240+ .
Smallest ecosystem and talent pool. Fewer third-party tools and fewer engineers with GCP experience .
Enterprise support. Historically lagged AWS and Azure, though Google has invested heavily in closing the gap .
GCP is the natural choice for AI and ML workloads, data analytics, Kubernetes-native platform teams, and organizations that value clean APIs and engineering quality.
Complete Example Session
This session explores the three providers through the lens of common workloads and demonstrates how the same workload maps differently to each.
# ============================================
# PART 1: THE THREE PROVIDERS AT A GLANCE
# ============================================
# AWS (Amazon Web Services)
# Launched: 2006
# Market share Q2 2026: 28%
# Revenue Q2 2026: $42.2B
# Annual run rate: $169B
# Growth rate: 37% YoY
# Services: 240+
# Strengths: breadth, compliance, GPU variety, ecosystem
# Azure (Microsoft)
# Launched: 2010
# Market share Q2 2026: 20%
# Revenue Q2 2026 (Intelligent Cloud): $39.3B
# Annual run rate: $157B
# Growth rate: 32% YoY (Intelligent Cloud)
# Regions: 60+
# Strengths: Microsoft integration, hybrid, OpenAI
# GCP (Google Cloud Platform)
# Launched: 2008
# Market share Q2 2026: 15%
# Revenue Q2 2026: $24.8B
# Annual run rate: $99B
# Growth rate: 82% YoY
# Services: 150+
# Strengths: AI/ML, BigQuery, Kubernetes, pricing
# ============================================
# PART 2: THE MICROSOFT-STACK ENTERPRISE
# ============================================
# A company running Windows Server, Active Directory,
# SQL Server, and Office 365.
# Choice: Azure
# Why:
# - Entra ID integrates natively
# - Azure Hybrid Benefit reuses existing licenses
# - SQL Server on Azure VMs is the same product
# - Office 365 integration is seamless
# - The team already knows Microsoft tooling
# The cost savings from Hybrid Benefit alone can
# make Azure cheaper than the alternatives.
# ============================================
# PART 3: THE AI STARTUP
# ============================================
# A startup building an AI product that trains models
# and runs inference at scale.
# Choice: GCP
# Why:
# - TPUs are the cheapest way to train large models
# - Vertex AI provides end-to-end ML workflows
# - BigQuery handles the data pipeline
# - GCP is 5-10% cheaper for compute
# - Automatic sustained-use discounts
# The startup's primary cost is GPU/TPU compute.
# GCP's AI infrastructure is the differentiator.
# ============================================
# PART 4: THE CLOUD-NATIVE SAAS COMPANY
# ============================================
# A SaaS company building a multi-tenant application
# that needs a wide variety of managed services.
# Choice: AWS
# Why:
# - The broadest service catalog
# - The most mature managed services
# - The largest partner ecosystem
# - The deepest pool of engineers who know the platform
# - The most mature compliance certifications
# The company values breadth and ecosystem over price.
# ============================================
# PART 5: THE REGULATED INDUSTRY
# ============================================
# A healthcare or financial services company
# with strict compliance requirements.
# Choice: AWS or Azure
# Why:
# - AWS has the broadest compliance portfolio
# - Azure has strong enterprise and government credentials
# - Both offer dedicated regions for regulated workloads
# - GCP is catching up but has fewer certifications
# The choice depends on the existing stack and the
# specific regulatory framework.
# ============================================
# PART 6: THE DATA ANALYTICS TEAM
# ============================================
# A team that needs a cloud data warehouse
# and analytics platform.
# Choice: GCP
# Why:
# - BigQuery is widely considered the best
# - Price-performance is excellent
# - BigQuery ML runs ML models in SQL
# - Integration with the rest of GCP's AI stack
# For many data teams, BigQuery alone justifies GCP.
# ============================================
# PART 7: THE KUBERNETES PLATFORM TEAM
# ============================================
# A platform team building on Kubernetes.
# Choice: GCP
# Why:
# - Google invented Kubernetes
# - GKE is the most operationally mature
# - GKE has a free standard control plane
# - Native integration with GCP's networking
# AWS EKS charges for the control plane.
# Azure AKS is easier for Microsoft teams but GKE is more mature.
# ============================================
# PART 8: THE COST-SENSITIVE STARTUP
# ============================================
# A startup with limited budget and variable workloads.
# Choice: GCP or AWS
# Why GCP:
# - Lower baseline pricing
# - Automatic sustained-use discounts
# - Always Free tier is the most useful
# Why AWS:
# - Startup credit programs
# - The largest pool of engineers and tools
# - The broadest service catalog for future growth
# The choice depends on the workload and the team's skills.
# ============================================
# PART 9: THE MULTI-CLOUD PATTERN
# ============================================
# Many organizations now use more than one provider.
# The most common patterns in 2026:
# - AWS primary + GCP for AI and BigQuery
# - AWS primary + Azure for Office 365 integration
# - GCP primary + AWS for services GCP lacks
# The pattern reflects the reality that no provider
# is best at everything.
# ============================================
# PART 10: THE SUMMARY
# ============================================
# AWS:
# The market leader. Broadest services. Deepest ecosystem.
# Highest on-demand pricing. Best for breadth and compliance.
# Azure:
# The enterprise integrator. Best for Microsoft stacks.
# Strongest hybrid cloud. OpenAI partnership.
# Middle pricing. Best for Windows/.NET/Office 365 shops.
# GCP:
# The AI and data specialist. Best for ML, BigQuery, K8s.
# Lowest baseline pricing. Fastest growing.
# Smallest ecosystem. Best for AI and data workloads.The ten parts cover the three providers at a glance, the Microsoft-stack enterprise, the AI startup, the cloud-native SaaS company, the regulated industry, the data analytics team, the Kubernetes platform team, the cost-sensitive startup, the multi-cloud pattern, and the summary.
Quick Reference
The Three Providers
| Attribute | AWS | Azure | GCP |
|---|---|---|---|
| Launched | 2006 | 2010 | 2008 |
| Market share (Q2 2026) | 28% | 20% | 15% |
| Revenue (Q2 2026) | $42.2B | $39.3B | $24.8B |
| Annual run rate | $169B | $157B | $99B |
| Growth (Q2 2026) | 37% | 32% | 82% |
| Services | 240+ | 200+ | 150+ |
| Regions | 30+ | 60+ | 43 |
| Primary strength | Breadth | Microsoft integration | AI/ML |
The Strengths by Provider
| Provider | Best For |
|---|---|
| AWS | Breadth, compliance, GPU variety, ecosystem |
| Azure | Microsoft stacks, hybrid cloud, OpenAI |
| GCP | AI/ML, BigQuery, Kubernetes, pricing |
The Pricing Comparison
| Aspect | AWS | Azure | GCP |
|---|---|---|---|
| On-demand compute | Highest | Middle | Lowest |
| Committed discounts | Deepest | Strong | Automatic |
| Egress | Highest | Middle | Lowest |
| Free tier | 12-month | 12-month | Always Free |
The Use Case Matrix
| Workload | Best Provider |
|---|---|
| Microsoft stack (AD, .NET, SQL Server) | Azure |
| AI/ML training at scale | GCP |
| Regulated fintech/healthcare | AWS |
| Video/media with heavy egress | GCP |
| Multi-region global SaaS | Azure |
| Kubernetes-native platform | GCP |
| Broadest service catalog | AWS |
Best Practices
✅ Do This:
# Match the provider to the existing stack
# Microsoft shop → Azure # ✅# Match the provider to the workload
# AI/ML → GCP; Microsoft → Azure; breadth → AWS # ✅# Consider the total cost, not just the list price
# Hybrid Benefit, sustained-use discounts, egress # ✅# Design for portability where it matters
# Containers and Kubernetes reduce lock-in # ✅# Use the free tier to evaluate before committing
# All three offer free tiers for experimentation # ✅❌ Don’t Do This:
# Don't assume AWS is always the right choice
# Azure and GCP have genuine advantages for specific workloads # ❌# Don't ignore egress costs when planning
# Data transfer out is where bills explode # ❌# Don't choose a provider based solely on price
# The ecosystem and skills matter more long-term # ❌# Don't assume migration between providers is trivial
# Egress fees are waived for exits, but the work is real # ❌Common Pitfalls
| Pitfall | Why It Happens | Fix |
|---|---|---|
| Wrong provider for the stack | Chose based on price alone | Match to existing tools and skills |
| Unexpected egress costs | Ignored data transfer pricing | Model egress before committing |
| Lock-in surprise | Used provider-specific services | Standardize on containers and open APIs |
| Cost overrun on AWS | On-demand pricing is highest | Use Savings Plans or Reserved Instances |
| GCP ecosystem gaps | Fewer third-party tools | Evaluate tool availability before choosing |
Real-World Examples
1. AWS Provisioning
aws ec2 run-instances --image-id ami-xxx --instance-type t3.medium2. Azure Provisioning
az vm create --resource-group myRG --name myVM --image UbuntuLTS3. GCP Provisioning
gcloud compute instances create my-vm --zone=us-central1-a4. AWS S3 Storage
aws s3 mb s3://my-bucket5. Azure Blob Storage
az storage container create --name mycontainer6. GCP Cloud Storage
gsutil mb gs://my-bucket7. AWS Bedrock (AI)
aws bedrock list-foundation-models8. Azure OpenAI
az cognitiveservices account create --kind OpenAI9. GCP Vertex AI
gcloud ai models list10. Multi-Cloud
# AWS primary + GCP for AI/BigQuery
# AWS primary + Azure for Office 365Visual
The Three Providers
┌──────────────────────────────────────────────┐
│ THE HYPERSCALERS │
│ │
│ AWS: │
│ ████████████████████████████ 28% │
│ Oldest, broadest, largest ecosystem │
│ │
│ Azure: │
│ ████████████████████ 20% │
│ Microsoft integration, hybrid, OpenAI │
│ │
│ GCP: │
│ ███████████████ 15% │
│ AI/ML, BigQuery, Kubernetes, pricing │
│ │
│ Combined: 63% of global cloud market │
│ │
└──────────────────────────────────────────────┘The Strengths Matrix
┌──────────────────────────────────────────────┐
│ PROVIDER STRENGTHS │
│ │
│ AWS: │
│ ├─ 240+ services │
│ ├─ Broadest compliance │
│ ├─ Deepest GPU variety │
│ └─ Largest talent pool │
│ │
│ Azure: │
│ ├─ Microsoft 365/AD integration │
│ ├─ Hybrid cloud (Azure Arc) │
│ ├─ OpenAI partnership │
│ └─ 60+ regions │
│ │
│ GCP: │
│ ├─ TPUs and Vertex AI │
│ ├─ BigQuery │
│ ├─ GKE (Kubernetes) │
│ └─ Lowest baseline pricing │
│ │
└──────────────────────────────────────────────┘The Use Case Decision Flow
┌──────────────────────────────────────────────┐
│ CHOOSING A PROVIDER │
│ │
│ Already using Microsoft stack? │
│ └─ YES → Azure │
│ │
│ Primary workload is AI/ML or BigQuery? │
│ └─ YES → GCP │
│ │
│ Need broadest services and compliance? │
│ └─ YES → AWS │
│ │
│ Price-sensitive and Linux-based? │
│ └─ YES → GCP or AWS (evaluate) │
│ │
└──────────────────────────────────────────────┘The Multi-Cloud Pattern
┌──────────────────────────────────────────────┐
│ MULTI-CLOUD PATTERNS │
│ │
│ Pattern 1: │
│ AWS primary + GCP for AI/BigQuery │
│ (Most common new pattern) │
│ │
│ Pattern 2: │
│ AWS primary + Azure for Office 365 │
│ (Established enterprise pattern) │
│ │
│ Pattern 3: │
│ GCP primary + AWS for GCP gaps │
│ │
│ No provider is best at everything. │
│ │
└──────────────────────────────────────────────┘Summary
| Item | Value |
|---|---|
| AWS | Market leader, 28% share, 240+ services, breadth |
| Azure | Second, 20% share, Microsoft integration, hybrid |
| GCP | Third, 15% share, AI/ML, BigQuery, Kubernetes |
| AWS strength | Service breadth, compliance, ecosystem |
| Azure strength | Microsoft stack, hybrid, OpenAI |
| GCP strength | AI/ML, BigQuery, pricing, Kubernetes |
| AWS weakness | Highest on-demand pricing, billing complexity |
| Azure weakness | Service maturity, documentation consistency |
| GCP weakness | Smallest ecosystem and talent pool |
| LFCA weight | Cloud Computing Fundamentals, 18–20% |
Key takeaways:
- AWS is the oldest and broadest provider. It has the largest service catalog, the deepest compliance certifications, and the largest ecosystem of partners and engineers. Its on-demand pricing is the highest, but its maximum committed discounts are the deepest .
- Azure is the enterprise integration provider. Its strength is the Microsoft ecosystem: Windows Server, Active Directory, SQL Server, Office 365, and .NET. Azure Hybrid Benefit reuses existing Microsoft licenses, and Azure Arc is the most mature hybrid cloud solution .
- GCP is the AI and data specialist. TPUs, Vertex AI, and BigQuery give it genuine advantages for AI/ML and data analytics workloads. It is generally 5–10% cheaper than AWS for equivalent compute, with automatic sustained-use discounts .
- The provider choice should match the existing stack and the workload. A Microsoft shop should default to Azure. An AI startup should evaluate GCP first. An organization that needs the broadest toolset and compliance story should consider AWS .
- The three providers account for roughly two-thirds of global cloud spending. AWS holds 28%, Azure 20%, and GCP 15% as of Q2 2026. Google Cloud is the fastest-growing, with 82% year-over-year revenue growth .
- The market is shifting toward AI. All three providers are investing heavily in AI infrastructure, and AI is the primary driver of cloud growth. Azure has the OpenAI partnership, GCP has TPUs and Gemini, and AWS has the broadest GPU selection and SageMaker .
- Multi-cloud is increasingly common. Many organizations use more than one provider — AWS for primary infrastructure and GCP for AI and analytics, or AWS for primary and Azure for Office 365 integration. The pattern reflects the reality that no provider is best at everything .
Remember: AWS, Azure, and GCP are not competing products with a single winner. They are different platforms optimized for different workloads. AWS is the broadest and most mature. Azure is the strongest for Microsoft-centric organizations and hybrid cloud. GCP is the strongest for AI, data analytics, and Kubernetes. The LFCA exam expects you to know what each provider is, what it is best at, and which use cases it naturally fits. The right choice depends on the organization’s existing stack, its workload requirements, and its constraints. There is no universal best provider — only the one that matches the situation.
Stop using slow, ad-bloated tool sites! 🤮
🔎 Search “KandZ Tools” on Google to use many professional utilities for free.
KandZ.me is the ultimate minimalist hub for:
✅ Finance (Mortgage, Interest, Inflation)
✅ Tech (Base64, JSON, Dev Suite, IP)
✅ Health (BMI, BMR, TDEE)
✅ Productivity (Timer, Workspace, QR)
⚡️ Fast & Private
🔒 No data leaves your device
💎 100% Free
🔗 Use it now: https://tools.kandz.me
🔖 Bookmark it—you’ll need it later!