We begin Part VIII: The Path After the Book, the final stretch, dedicated to your professional development once you master the concepts. And we start with Chapter 32: AWS Certifications, because certifications are an excellent way to validate what you know and boost your career. We start with the gateway, the certification designed for beginners: the AWS Certified Cloud Practitioner. It’s the first step and the ideal place to show (to others and yourself) that you master the fundamentals.
Why Certifications Matter
Before the specific certification, why get certified? A certification is an official AWS credential that proves you have certain knowledge. It gives you:
Benefits of getting certified: ✓ Officially demonstrates your knowledge (to companies, clients) ✓ Improves your resume and job opportunities ✓ Gives you a CLEAR GOAL to study in a structured way ✓ Gives you CONFIDENCE: confirms that you truly master the topic
Analogy: a certification is like a driver’s license for the cloud. Knowing how to drive is good, but the license officially proves it and opens doors (you can rent cars, work as a driver...). Likewise, knowing AWS is good, but the certification accredits it to the world and opens up opportunities. And studying for it makes you drive (use AWS) better.
What is the AWS Certified Cloud Practitioner
The AWS Certified Cloud Practitioner is AWS’s foundational level certification: the gateway, designed for those who are starting out or want to show they understand the basic concepts of the cloud and AWS. You don’t need to be a technical expert or know how to program; it validates that you understand the fundamentals.
AWS Certification Levels (from least to most demanding): 1. FOUNDATIONAL → Cloud Practitioner ← START HERE 2. ASSOCIATE → Solutions Architect Associate, etc. (Ch. 32.2-32.3) 3. PROFESSIONAL → Solutions Architect Pro, DevOps Pro (Ch. 32.2-32.3) 4. SPECIALTY → specialized certifications (Ch. 32.4)
It’s the first step of the entire AWS certification ladder, and the natural starting point.
What it Covers and Who it’s For
The Cloud Practitioner covers the fundamental concepts that, in fact, you’ve learned in this book, especially in its first parts:
Cloud Practitioner Topics (you already know them!): - What the cloud is and its benefits (Part I of the book) - Main AWS services (compute, storage, networking, DBs...) - Basic security concepts (shared responsibility model...) - Pricing and billing concepts (pay-as-you-go, costs...)
Who is it ideal for?
- Those who are starting out in the cloud and want a first certification.
- Non-technical profiles who work with the cloud (sales, managers, etc.) and want to understand the fundamentals.
- As a first step before more technical certifications.
💡 Good news: if you’ve followed this book and understood its concepts (especially Parts I to III), you have an excellent foundation for the Cloud Practitioner. Many of its topics are exactly what we’ve explained: what the cloud is, main services, basic security, costs. You’d just need to review with an exam-oriented approach.
How to Prepare
Some general guidelines to tackle it (applicable to any certification):
- Review the fundamentals: the concepts from the first parts of this book are the foundation.
- Use AWS official resources: AWS offers free training (we’ll see this in Chapter 34, with AWS Skill Builder), including preparatory courses for this certification.
- Take practice exams: getting familiar with the type of questions is very useful. There are sample exams that show if you’re ready.
- Practice on AWS: nothing like using the services (you can start with the free tier) to reinforce what you study. Practice cements the concepts.
Real-world example: someone working in the sales area of a tech company notices that “the cloud” and AWS are increasingly discussed at work, but feels lost in technical meetings. They decide to get the Cloud Practitioner. They study the fundamentals (what the cloud is, main services, how billing works), take a practice exam or two, and pass. Result: now they understand technical conversations, can speak knowledgeably with clients about the cloud, and have improved their professional profile, all without needing to be an engineer. For them, it was the perfect gateway to the world of AWS. And for a technical profile just starting out, it’s the first official stamp before moving up.
What You Should Remember
- AWS certifications officially validate your knowledge, improve your resume and opportunities, give you a clear goal to study, and provide confidence. Like the driver’s license of the cloud.
- The AWS Certified Cloud Practitioner is the foundational level certification (the gateway), designed for those who are starting out or want to show they understand the basic concepts of the cloud and AWS. No need to be a technical expert.
- It’s the first step of the AWS certification ladder (Foundational → Associate → Professional → Specialty).
- It covers fundamentals you already know from this book: what the cloud is, main services, basic security, and pricing/billing. Ideal for beginners and non-technical profiles.
- 💡 If you’ve understood the first parts of the book, you have an excellent foundation for it. Prepare by reviewing fundamentals, using AWS official resources, practice exams, and practicing on AWS.
In the next subchapter, we’ll move up a level to the more technical and in-demand certifications: the Solutions Architect path, from Associate to Professional.
Cloud, AWS & Terraform — From Zero to Expert
Chapter 1 · What is cloud computing
- 1.1 The traditional client-server model
- 1.2 Problems the cloud came to solve
- 1.3 On-premise vs cloud vs hybrid
- 1.4 The three service models: IaaS, PaaS, SaaS
- 1.5 The five pillars of cloud (according to NIST)
- 1.6 Real advantages: elasticity, pay-as-you-go, global availability
Chapter 2 · The cloud market and major providers
- 2.1 AWS, Azure and GCP: differences and market share
- 2.2 Why learn AWS first
- 2.3 Concepts that are universal among providers
Chapter 3 · Regions, availability zones and edge
- 3.1 What is an AWS region and how to choose it
- 3.2 Availability Zones: high availability by design
- 3.3 Edge locations and CloudFront
- 3.4 Latency, resilience and data sovereignty
Chapter 4 · Compute: EC2
- 4.1 Instances: types, families and when to choose each
- 4.2 AMIs, key pairs and Security Groups
- 4.3 Instance lifecycle
- 4.4 Elastic IPs and Placement Groups
- 4.5 Savings Plans vs Reserved vs On-Demand vs Spot
Chapter 5 · Storage: S3
- 5.1 Buckets, objects and keys
- 5.2 Storage classes (Standard, IA, Glacier…)
- 5.3 Versioning and object lifecycle
- 5.4 Bucket policies and ACLs
- 5.5 Static website hosting
Chapter 6 · Networking: VPC
- 6.1 What is a VPC and why you need it
- 6.2 Public and private subnets
- 6.3 Internet Gateway and NAT Gateway
- 6.4 Route Tables and Network ACLs
- 6.5 VPC Peering and endpoints
Chapter 7 · Identity and access: IAM
- 7.1 Users, groups, roles and policies
- 7.2 The principle of least privilege
- 7.3 Identity-based vs resource-based policies
- 7.4 MFA and temporary credentials (STS)
- 7.5 IAM security best practices
Chapter 8 · Managed databases
- 8.1 RDS: engines, Multi-AZ and read replicas
- 8.2 Aurora and its advantages over vanilla RDS
- 8.3 DynamoDB: key-value / document model
- 8.4 ElastiCache for in-memory cache
- 8.5 When to use each type of database
Chapter 9 · Why Infrastructure as Code
- 9.1 Problems with manual provisioning
- 9.2 Declarative vs imperative IaC
- 9.3 Terraform vs CloudFormation vs Pulumi vs CDK
- 9.4 The plan → apply → destroy cycle
Chapter 10 · HCL: the Terraform language
- 10.1 Resource, variable, output, locals blocks
- 10.2 Data types: string, number, bool, list, map, object
- 10.3 Expressions, references and built-in functions
- 10.4 Conditionals and loops (count, for_each, for)
Chapter 11 · Providers and state
- 11.1 How the AWS provider works
- 11.2 The terraform.tfstate file and its importance
- 11.3 Local state vs remote state (S3 + DynamoDB)
- 11.4 Essential commands: init, plan, apply, destroy, fmt, validate
Chapter 12 · Your first real infrastructure in Terraform
- 12.1 Create a VPC with subnets from scratch
- 12.2 Launch a public EC2 instance
- 12.3 Associate a Security Group and an Elastic IP
- 12.4 Outputs and references between resources
- 12.5 Team workflow: PR review of plans
Chapter 13 · Load balancing and auto scaling
- 13.1 Application Load Balancer vs Network Load Balancer
- 13.2 Target Groups, listeners and rules
- 13.3 Auto Scaling Groups: policies and metrics
- 13.4 Warm pools and lifecycle hooks
Chapter 14 · Serverless with Lambda
- 14.1 The Lambda execution model
- 14.2 Triggers: API Gateway, S3, DynamoDB Streams, SQS
- 14.3 Dependency management and layers
- 14.4 Cold starts and strategies to reduce them
- 14.5 Limits and anti-patterns
Chapter 15 · Messaging and events
- 15.1 SQS: standard vs FIFO queues, DLQ
- 15.2 SNS: topics, subscriptions, fan-out
- 15.3 EventBridge: event buses and rules
- 15.4 Patterns: pub/sub, decoupling, saga
Chapter 16 · Content delivery and DNS
- 16.1 Route 53: record types and routing policies
- 16.2 CloudFront: distributions, caches and origins
- 16.3 ACM: free SSL/TLS certificates
- 16.4 WAF integrated with CloudFront
Chapter 17 · Containers on AWS
- 17.1 Docker: quick review of key concepts
- 17.2 ECR: private image registry
- 17.3 ECS: task definitions, services, Fargate vs EC2
- 17.4 EKS: when Kubernetes and when not
Chapter 18 · Modules: reuse and composition
- 18.1 Anatomy of a Terraform module
- 18.2 Input variables, outputs and dependencies
- 18.3 Local modules vs Terraform Registry modules
- 18.4 Module versioning with Git tags
- 18.5 Design of generic vs domain-specific modules
Chapter 19 · Workspaces and environment management
- 19.1 Terraform workspaces: use cases and limitations
- 19.2 Directory strategy per environment (dev/stg/prod)
- 19.3 Terragrunt: DRY for environment configurations
- 19.4 Environment variables and .tfvars files
Chapter 20 · Remote backends and locking
- 20.1 Configure S3 + DynamoDB as backend
- 20.2 State locking: avoiding team corruption
- 20.3 State migration between backends
- 20.4 terraform import: bring existing resources into state
Chapter 21 · Infrastructure testing
- 21.1 Terraform validate and fmt in CI
- 21.2 Checkov and tfsec: static security analysis
- 21.3 Terratest: integration tests in Go
- 21.4 Contract testing between modules
Chapter 22 · Terraform in CI/CD
- 22.1 Basic pipeline: lint → plan → apply in GitHub Actions
- 22.2 Atlantis: GitOps for Terraform
- 22.3 Terraform Cloud / HCP Terraform
- 22.4 Drift detection and automatic reconciliation
Chapter 23 · Defense in depth
- 23.1 AWS Organizations and Service Control Policies
- 23.2 AWS Config: continuous compliance
- 23.3 GuardDuty: threat detection
- 23.4 Security Hub: centralized view
- 23.5 KMS: key management and rotation
- 23.6 Secrets Manager vs Parameter Store
Chapter 24 · Observability: logs, metrics and traces
- 24.1 CloudWatch Logs, metrics and alarms
- 24.2 CloudWatch Dashboards and Contributor Insights
- 24.3 X-Ray: distributed tracing
- 24.4 OpenTelemetry on AWS
- 24.5 Managed Grafana and Managed Prometheus
Chapter 25 · Cost optimization
- 25.1 AWS Cost Explorer and budgets with alerts
- 25.2 Trusted Advisor and Compute Optimizer
- 25.3 Rightsizing: how to detect overprovisioning
- 25.4 Savings Plans vs Reserved Instances: strategic decision
- 25.5 FinOps: culture and processes to control spending
Chapter 26 · High availability and disaster recovery
- 26.1 RTO and RPO: defining objectives
- 26.2 Strategies: backup/restore, pilot light, warm standby, multi-site
- 26.3 Route 53 health checks and automatic failover
- 26.4 AWS Backup: centralized backup policy
Chapter 27 · AWS Well-Architected Framework
- 27.1 The six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, sustainability
- 27.2 Well-Architected Tool: formal reviews
- 27.3 How to apply the framework in design decisions
Chapter 28 · Serverless architectures at scale
- 28.1 Event-driven architecture with Lambda + EventBridge
- 28.2 Saga pattern for distributed transactions
- 28.3 Step Functions: orchestration of complex workflows
- 28.4 Lambda@Edge and CloudFront Functions
Chapter 29 · Data platforms on AWS
- 29.1 Data Lake with S3, Glue and Athena
- 29.2 Kinesis Data Streams and Firehose for streaming
- 29.3 Redshift: data warehousing at scale
- 29.4 Lake Formation: data governance
Chapter 30 · Multi-account and landing zones
- 30.1 Why separate workloads into different accounts
- 30.2 AWS Control Tower and Account Factory
- 30.3 Centralized log and security management
- 30.4 Terraform at multi-account scale with shared modules
Chapter 31 · Platform Engineering and Internal Developer Platform
- 31.1 Golden paths and abstractions over Terraform
- 31.2 AWS Service Catalog
- 31.3 Backstage as a developer portal
- 31.4 Terraform modules as internal product
Chapter 32 · Relevant AWS certifications
- 32.1 Cloud Practitioner: is it worth it?
- 32.2 Solutions Architect Associate → Professional
- 32.3 DevOps Engineer Professional
- 32.4 Specialty: Security, Database, Networking
- 32.5 HashiCorp Terraform Associate
Chapter 33 · Projects to consolidate what you've learned
- 33.1 Project 1: serverless blog (S3 + CloudFront + Lambda + DynamoDB)
- 33.2 Project 2: REST API with ECS Fargate + RDS + ALB
- 33.3 Project 3: data platform with Glue + Athena + Redshift
- 33.4 Project 4: multi-account landing zone with Terraform and Control Tower
