Skip to content
ExponaBLOG
Series · Day 100 of 100

AWS for Developers

  1. 51
    Use Step Functions instead of retry code for production
    Stop writing retry logic in every Lambda.
  2. 52
    Route 53 DNS: a practical AWS guide for working engineers
    DNS that integrates with everything on AWS.
  3. 53
    Route 53 health checks and failover in AWS for Developers
    Automatic DNS failover between regions or endpoints.
  4. 54
    TLS with ACM: a practical AWS guide for working engineers
    Free certificates, renewed automatically.
  5. 55
    CloudFront certificates live in us-east-1 for production
    The region detail that catches everyone.
  6. 56
    Secrets Manager vs Parameter Store in AWS for Developers
    Where to store configuration and secrets.
  7. 57
    Rotate database credentials: AWS lessons from production
    Static passwords are a liability.
  8. 58
    Encryption with KMS: what every AWS developer should know
    Managed keys for data at rest.
  9. 59
    Envelope encryption: what every AWS developer should know
    How KMS encrypts large data efficiently.
  10. 60
    CloudWatch logs, metrics and alarms in AWS for Developers
    Observability built into AWS.
  11. 61
    Set log retention: what every AWS developer should know
    Never-expire logs quietly grow your bill.
  12. 62
    Tracing on AWS: concepts, trade-offs and production lessons
    Follow requests across Lambda, ECS and APIs.
  13. 63
    Query logs with Logs Insights: a AWS guide for developers
    Find problems in minutes, not hours.
  14. 64
    Infrastructure as Code on AWS: best practices explained
    CDK, Terraform or CloudFormation?
  15. 65
    CDK in TypeScript: what every AWS developer should know
    Infrastructure with types and autocomplete.
  16. 66
    CI/CD to AWS with GitHub Actions: lessons from production
    Deploy without long-lived access keys.
  17. 67
    Replace access keys with OIDC: a AWS guide for developers
    The most valuable CI/CD security upgrade.
  18. 68
    Deploying .NET on AWS: a practical guide for developers
    Options from simple to serverless.
  19. 69
    Deploying Next.js on AWS: a hands-on guide for engineers
    Several paths, different trade-offs.
  20. 70
    A NestJS API on ECS: reference architecture in practice
    The setup I use for production Node APIs.
  21. 71
    Blue/green deployments on AWS: best practices explained
    Switch traffic instantly, roll back instantly.
  22. 72
    Cost optimization on AWS: a hands-on guide for engineers
    The strategies that cut real bills.
  23. 73
    Savings Plans: a complete AWS guide for production teams
    Commit to spend, save on compute.
  24. 74
    The NAT Gateway cost trap: practical tips and trade-offs
    The line item that surprises every team.
  25. 75
    Understand data transfer costs: best practices explained
    Data leaving AWS — or crossing AZs — costs money.
  26. 76
    Tagging and cost allocation: AWS lessons from production
    Know who spends what.
  27. 77
    Budgets and cost anomaly detection in AWS for Developers
    Find surprise bills in days, not at month-end.
  28. 78
    An AWS security baseline: a hands-on guide for engineers
    Services to turn on in every account.
  29. 79
    Turn on CloudTrail everywhere: a AWS guide for developers
    Your audit log for every API call.
  30. 80
    WAF and Shield: a complete AWS guide for production teams
    Protect web apps at the edge.
  31. 81
    Rate-based WAF rules: what every AWS developer should know
    Stop brute force and scraping at the edge.
  32. 82
    High availability patterns: AWS best practices explained
    Design so a single failure isn't an outage.
  33. 83
    Multi-AZ by default: what every AWS developer should know
    AZ failures happen. Plan for them.
  34. 84
    Disaster recovery strategies: a AWS guide for developers
    Four options, four price points.
  35. 85
    RTO and RPO: a practical AWS guide for working engineers
    Two numbers every system should have.
  36. 86
    The Well-Architected Framework: best practices explained
    Six pillars for reviewing any system.
  37. 87
    Run a Well-Architected review: a AWS guide for developers
    A free, structured architecture review.
  38. 88
    A serverless SaaS architecture: best practices explained
    An example stack for a small team.
  39. 89
    When serverless is the wrong choice in AWS for Developers
    Serverless is great — until it isn't.
  40. 90
    Sending email with SES: a practical guide for developers
    Transactional email at low cost.
  41. 91
    Email deliverability basics: AWS lessons from production
    Your emails are useless if they land in spam.
  42. 92
    Authentication with Cognito: AWS lessons from production
    Managed user pools for your apps.
  43. 93
    Cognito or your own auth: a hands-on guide for engineers
    An honest trade-off.
  44. 94
    AI features with Bedrock: a hands-on guide for engineers
    Generative AI inside your AWS account.
  45. 95
    Bedrock or a direct model API: a AWS guide for developers
    Both work. Choose by constraints.
  46. 96
    My AWS architecture review checklist: a practical guide
    Questions I ask before approving a design.
  47. 97
    Common AWS mistakes: a practical guide for developers
    Mistakes I see again and again.
  48. 98
    My production AWS starter architecture, explained simply
    What a typical web product gets from day one.
  49. 99
    How to learn AWS effectively: what developers should know
    Certifications help — projects help more.
  50. 100
    100 days of AWS: lessons — practical tips and trade-offs
    Wrapping up the series.