Skip to content
ExponaBLOG
Series · Day 100 of 100

AWS for Developers

  1. 01
    Learning AWS as an application developer for production
    You don't need to know 200 services. You need 20, deeply.
  2. 02
    The AWS mental model: a practical guide for developers
    Regions, zones, accounts and services — how it all fits.
  3. 03
    Use multiple AWS accounts from day one, explained simply
    One account for everything doesn't age well.
  4. 04
    IAM fundamentals: what every AWS developer should know
    Who can do what, on which resource.
  5. 05
    Lock away the root user: real-world lessons and examples
    Root can do anything — including closing your account.
  6. 06
    Reading IAM policies: what every AWS developer should know
    Every policy has the same four parts.
  7. 07
    IAM roles for compute: a practical guide for developers
    Applications should never hold long-term keys.
  8. 08
    AWS CLI profiles and SSO: a hands-on guide for engineers
    Work across accounts without copying keys around.
  9. 09
    IAM Identity Center: what every AWS developer should know
    One login for every AWS account.
  10. 10
    VPC fundamentals: what every AWS developer should know
    The network your resources live in.
  11. 11
    Security groups vs NACLs: a hands-on guide for engineers
    Two firewalls, different jobs.
  12. 12
    VPC endpoints: a complete AWS guide for production teams
    Private access to AWS services — and lower NAT bills.
  13. 13
    Keep databases in private subnets: a practical AWS guide
    Your database should never have a public IP.
  14. 14
    EC2 essentials: a complete AWS guide for production teams
    Virtual machines, chosen and configured well.
  15. 15
    Try Graviton instances: a practical guide for developers
    ARM-based instances with better price-performance.
  16. 16
    Auto Scaling groups: what every AWS developer should know
    Capacity that follows demand.
  17. 17
    Launch templates: what every AWS developer should know
    Versioned instance configuration.
  18. 18
    Load balancers: ALB vs NLB — AWS lessons from production
    Choosing the right entry point.
  19. 19
    ALB listener rules: what every AWS developer should know
    One load balancer, many services.
  20. 20
    Containers with ECS Fargate: AWS lessons from production
    Run containers without managing servers.
  21. 21
    Task role vs execution role: AWS lessons from production
    The ECS distinction everyone confuses.
  22. 22
    ECR and image management: a hands-on guide for engineers
    A private registry for your containers.
  23. 23
    Scan images on push: what every AWS developer should know
    Catch vulnerable packages before they ship.
  24. 24
    EKS: when Kubernetes on AWS makes sense, explained simply
    Powerful, flexible — and a real commitment.
  25. 25
    ECS vs EKS: a practical AWS guide for working engineers
    Pick by team skills, not hype.
  26. 26
    Lambda fundamentals: what every AWS developer should know
    Functions that run on demand.
  27. 27
    Lambda cold starts: what every AWS developer should know
    Why the first request is slower — and what to do.
  28. 28
    Lambda patterns I use: a practical guide for developers
    Where serverless functions shine.
  29. 29
    Lambda and relational databases: lessons from production
    Thousands of concurrent functions can exhaust your DB.
  30. 30
    API Gateway: REST vs HTTP APIs — lessons from production
    Two products with the same name.
  31. 31
    HTTP APIs are cheaper: a practical guide for developers
    Same Lambda backend, a fraction of the gateway cost.
  32. 32
    S3 deep dive: a practical AWS guide for working engineers
    More than a bucket of files.
  33. 33
    Uploads with presigned URLs: AWS lessons from production
    Let browsers upload straight to S3.
  34. 34
    S3 security essentials: a practical guide for developers
    Most cloud data leaks are misconfigured buckets.
  35. 35
    S3 event notifications: a practical guide for developers
    React to uploads automatically.
  36. 36
    CloudFront essentials: a practical guide for developers
    A global CDN in front of everything.
  37. 37
    CloudFront cache policies: practical tips and trade-offs
    What's in the cache key decides your hit ratio.
  38. 38
    RDS PostgreSQL in production: a AWS guide for developers
    A managed database, configured properly.
  39. 39
    Multi-AZ vs read replicas: practical tips and trade-offs
    One is for availability, the other for scale.
  40. 40
    Aurora vs standard RDS: a practical guide for developers
    When Aurora is worth it.
  41. 41
    RDS backups and point-in-time recovery, explained simply
    Know how to restore before you need to.
  42. 42
    DynamoDB fundamentals: a practical guide for developers
    Design for access patterns, not entities.
  43. 43
    Be careful with single-table design in AWS for Developers
    Powerful, but hard for teams to evolve.
  44. 44
    ElastiCache for Redis and Valkey: a practical AWS guide
    Managed in-memory caching.
  45. 45
    Consider Valkey on ElastiCache: best practices explained
    Redis-compatible, open source and cheaper on AWS.
  46. 46
    Queues with SQS: a complete AWS guide for production teams
    Decouple services and smooth out spikes.
  47. 47
    SQS FIFO queues: a complete AWS guide for production teams
    Ordering and deduplication — with limits.
  48. 48
    SNS and EventBridge: what every AWS developer should know
    Fan-out and event routing.
  49. 49
    EventBridge Scheduler: a practical guide for developers
    Cron jobs as a managed service.
  50. 50
    Orchestration with Step Functions: a practical AWS guide
    Workflows with retries, waits and branches.