Cloud & Infrastructure
Cloud platforms, core services, IaC, containerization, and orchestration
Cloud Service ModelsIaaS, PaaS, SaaS, FaaS; shared responsibility model›Major Cloud PlatformsAWS, Azure, GCP core services and global footprint comparison›ComputeEC2/VMs, Lambda/Functions, ECS/ACI, Fargate, App Service›StorageObject (S3/Blob), block (EBS), file (EFS/Azure Files) storage›Cloud NetworkingVPC, subnets, route tables, NAT gateway, VPN, Direct Connect, peering›Identity & Access (IAM)IAM roles/policies, Managed Identities, service accounts, least-privilege›Secrets & Key ManagementAWS Secrets Manager, Azure Key Vault, HashiCorp Vault, KMS›Cloud Security ServicesWAF, Shield/DDoS Protection, GuardDuty, Security Hub, Defender for Cloud›Cloud ObservabilityCloudWatch, Azure Monitor, Cloud Logging, X-Ray, Application Insights›Infrastructure as CodeTerraform, CloudFormation, Pulumi, Bicep; state management, modules›Containerization (Docker)Docker images, layers, multi-stage builds, registries (ECR, ACR, GCR)›Kubernetes (K8s)Pods, deployments, services, ingress, HPA, VPA, operators›Service MeshIstio, Linkerd; mTLS, traffic management, observability, policy enforcement›GitOpsArgoCD, Flux; declarative infrastructure, drift detection, reconciliation loops›Immutable InfrastructureReplace-not-patch philosophy, golden AMIs, Packer›Multi-Cloud & HybridLatency, data gravity, egress costs, governance challenges›Cloud Cost ManagementFinOps maturity model, spot instances, savings plans, reserved capacity›Landing Zone & GovernanceAccount/subscription structure, guardrails, SCPs, blueprints›