Bootcamp
A two-week sprint to be productive in AWS using infrastructure as code, OIDC federation, and modern guardrails.
Bootcamp plan
EXAMPLE
# AWS bootcamp - 10 working days Day 1 - Tooling: AWS CLI v2, profiles, aws-vault, AWS SSO, console basics. Day 2 - IAM fundamentals: principals, policies, roles, conditions, ABAC vs RBAC. Day 3 - Networking: VPC, subnets, security groups, NAT, VPC endpoints. Day 4 - Storage + databases: S3 (encryption, lifecycle), RDS, DynamoDB basics. Day 5 - Compute: EC2 + SSM, Lambda, Fargate; choosing between them. Weekend project: deploy a static site + signed Lambda URL via CDK or Terraform. Day 6 - Observability: CloudWatch Logs + Metrics, X-Ray, OpenTelemetry. Day 7 - CI/CD: GitHub Actions + OIDC, CodePipeline, blue/green for ECS or Lambda. Day 8 - Security: SCPs, AWS Config, GuardDuty, IAM Access Analyzer, Block Public Access. Day 9 - Cost: tags, Cost Explorer, Budgets, Savings Plans, free-tier traps. Day 10 - Production-readiness: multi-account org, audit + log archive, break-glass paths. Capstone: ship a small workload with IaC, OIDC-deployed CI, GuardDuty + Config rules. ## Tips - Multi-account from day one (root + workloads + audit + log archive) - Always OIDC federation; never long-lived access keys - Tag everything (Environment, Owner, CostCentre, Project) - Use SSM Session Manager instead of SSH - Read AWS Well-Architected Framework once - it is the rubric you will be measured against ## Common mistakes - Single account with hand-clicked resources - Long-lived IAM keys in CI - Public S3 buckets behind 'private' assumptions - Drift between IaC and console-edited resources
Why it matters
AWS rewards discipline: IaC, OIDC, multi-account, tagging. The capstone is what hiring managers will look at - ship a small workload with a real CI flow and you have a portfolio piece.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…