Site Reliability Engineering: Systems, cloud and reliability practice
The knowledge behind running reliable services: Linux and networking, AWS core services, SLOs, observability, incident management, release engineering, resilience, high availability, Kubernetes, infrastructure as code and common failure scenarios.
0 of 20 modules complete · 0 in progress · 20 to come
Locked. These lessons are not open to the public yet.
-
01
Introduction
What SRE is and the vocabulary it uses.
0 / 3- 1.1SRE, DevOps and operationsSoon
- 1.2Reliability terms: availability, durability, MTTR, MTBF, RPO, RTOSoon
- 1.3Troubleshooting methodologySoon
-
02
Linux and operating systems
The machine underneath every service.
0 / 6- 2.1Processes, threads and signalsSoon
- 2.2Memory: virtual memory, swap, OOM killerSoon
- 2.3Filesystems, inodes and disk I/OSoon
- 2.4CPU, load average and schedulingSoon
- 2.5Performance tools: top, vmstat, iostat, strace, perfSoon
- 2.6systemd and service managementSoon
-
03
Networking
How packets reach a service and where they get lost.
0 / 7- 3.1OSI model and TCP/IPSoon
- 3.2TCP: handshake, congestion control, timeoutsSoon
- 3.3DNS: records, resolution, TTL and cachingSoon
- 3.4HTTP/1.1, HTTP/2 and TLSSoon
- 3.5Load balancers: L4 vs L7Soon
- 3.6Reverse proxies, forward proxies and CDNsSoon
- 3.7Network tools: ping, traceroute, dig, curl, tcpdump, ssSoon
-
04
Cloud fundamentals
The model every cloud provider shares.
0 / 4- 4.1IaaS, PaaS, SaaS and serverlessSoon
- 4.2Regions, availability zones and edge locationsSoon
- 4.3Shared responsibility modelSoon
- 4.4Pricing models: on-demand, reserved, spotSoon
-
05
AWS compute
Where code runs.
0 / 6- 5.1EC2: instance types, AMIs, EBS-backed and instance storeSoon
- 5.2Auto Scaling groups and launch templatesSoon
- 5.3Lambda and serverless executionSoon
- 5.4ECS and FargateSoon
- 5.5EKS and managed KubernetesSoon
- 5.6Elastic Beanstalk, Lightsail and App RunnerSoon
-
06
AWS networking
The virtual network around your workloads.
0 / 7- 6.1VPC: CIDR blocks, subnets and route tablesSoon
- 6.2Internet gateway, NAT gateway and egressSoon
- 6.3Security groups and network ACLsSoon
- 6.4Elastic Load Balancing: ALB, NLB and GWLBSoon
- 6.5Route 53: routing policies and health checksSoon
- 6.6CloudFrontSoon
- 6.7VPC peering, Transit Gateway, PrivateLink, VPN and Direct ConnectSoon
-
07
AWS storage and databases
Where state lives.
0 / 7- 7.1S3: storage classes, consistency, versioning and lifecycleSoon
- 7.2EBS, EFS and FSxSoon
- 7.3RDS and AuroraSoon
- 7.4DynamoDBSoon
- 7.5ElastiCacheSoon
- 7.6Redshift, Athena and analytics servicesSoon
- 7.7AWS Backup, snapshots and replicationSoon
-
08
AWS messaging and integration
Moving work and events between services.
0 / 5- 8.1SQS: standard vs FIFO, visibility timeout, DLQSoon
- 8.2SNS and EventBridgeSoon
- 8.3Kinesis and MSKSoon
- 8.4Step FunctionsSoon
- 8.5API GatewaySoon
-
09
AWS identity and security
Who can do what.
0 / 5- 9.1IAM: users, roles, policies and STSSoon
- 9.2Organizations, accounts and SCPsSoon
- 9.3KMS, Secrets Manager and Parameter StoreSoon
- 9.4WAF, Shield, GuardDuty and Security HubSoon
- 9.5Encryption in transit and at restSoon
-
10
Service level objectives
Turning reliability into a number.
0 / 4- 10.1SLIsSoon
- 10.2SLOs and SLAsSoon
- 10.3Error budgetsSoon
- 10.4Availability maths: nines, series and parallel dependenciesSoon
-
11
Observability
Seeing what the system is doing.
0 / 8- 11.1Monitoring and the four golden signalsSoon
- 11.2Metrics, histograms and percentilesSoon
- 11.3LoggingSoon
- 11.4Distributed tracing and OpenTelemetrySoon
- 11.5AlertingSoon
- 11.6CloudWatch: metrics, logs, alarms and InsightsSoon
- 11.7CloudTrail, AWS Config and X-RaySoon
- 11.8Prometheus and GrafanaSoon
-
12
Incident management
Responding to and learning from failures.
0 / 5- 12.1On-callSoon
- 12.2Incident lifecycle, severity and rolesSoon
- 12.3PostmortemsSoon
- 12.4Runbooks and playbooksSoon
- 12.5Status pages and incident communicationSoon
-
13
Release engineering
Changing a running system safely.
0 / 6- 13.1CI/CD pipelinesSoon
- 13.2Rolling, blue-green and canary deploymentsSoon
- 13.3Feature flagsSoon
- 13.4RollbacksSoon
- 13.5CodePipeline, CodeDeploy and CodeBuildSoon
- 13.6Configuration managementSoon
-
14
Resilience patterns
Containing failure.
0 / 8- 14.1Timeouts, retries and exponential backoff with jitterSoon
- 14.2Circuit breakersSoon
- 14.3Bulkheads and isolationSoon
- 14.4Load shedding and backpressureSoon
- 14.5Rate limiting and throttlingSoon
- 14.6Cascading failuresSoon
- 14.7Graceful degradationSoon
- 14.8IdempotencySoon
-
15
High availability and disaster recovery
Surviving the loss of a machine, a zone or a region.
0 / 7- 15.1Multi-AZ architecturesSoon
- 15.2Multi-region architecturesSoon
- 15.3DR strategies: backup and restore, pilot light, warm standby, active-activeSoon
- 15.4Failover and health checksSoon
- 15.5Database replication and failoverSoon
- 15.6AWS Well-Architected FrameworkSoon
- 15.7Service quotas and limitsSoon
-
16
Capacity and performance
Having enough, at the right cost.
0 / 5- 16.1Capacity planningSoon
- 16.2Autoscaling policiesSoon
- 16.3Load testingSoon
- 16.4Tail latencySoon
- 16.5Cost optimization and FinOpsSoon
-
17
Containers and Kubernetes
Packaging and orchestrating workloads.
0 / 7- 17.1Containers: namespaces, cgroups and imagesSoon
- 17.2Kubernetes architecture: control plane and nodesSoon
- 17.3Pods, Deployments, StatefulSets and JobsSoon
- 17.4Services, Ingress and CNISoon
- 17.5Scheduling, requests, limits and QoSSoon
- 17.6HPA, VPA and cluster autoscalingSoon
- 17.7Service meshSoon
-
18
Infrastructure as code and automation
The environment, written down.
0 / 6- 18.1Infrastructure as codeSoon
- 18.2Terraform: state, modules and driftSoon
- 18.3CloudFormation and CDKSoon
- 18.4Toil and automationSoon
- 18.5Scripting with Bash and PythonSoon
- 18.6GitOpsSoon
-
19
Chaos and reliability testing
Finding weaknesses on purpose.
0 / 4- 19.1Chaos engineeringSoon
- 19.2AWS Fault Injection ServiceSoon
- 19.3Game daysSoon
- 19.4Testing in productionSoon
-
20
Failure scenarios
Common failures, each with symptoms, causes, checks and fixes.
0 / 10- 20.1High latencySoon
- 20.2Elevated error ratesSoon
- 20.3Memory leaks and OOM killsSoon
- 20.4Disk full and I/O saturationSoon
- 20.5Database failure and failoverSoon
- 20.6Cache stampede and thundering herdSoon
- 20.7DNS and certificate failuresSoon
- 20.8Bad deployments and config pushesSoon
- 20.9AWS service or AZ outageSoon
- 20.10Throttling and quota exhaustionSoon