<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Patricio Lumbe</title>
    <description>The latest articles on DEV Community by Patricio Lumbe (@patriciolumbe_cloud).</description>
    <link>https://dev.to/patriciolumbe_cloud</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3899159%2F4a3dea89-d190-478e-93fc-8b1a5221b948.jpg</url>
      <title>DEV Community: Patricio Lumbe</title>
      <link>https://dev.to/patriciolumbe_cloud</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/patriciolumbe_cloud"/>
    <language>en</language>
    <item>
      <title>AWS Production-Ready: Beyond the "Hello World" Infrastructure</title>
      <dc:creator>Patricio Lumbe</dc:creator>
      <pubDate>Tue, 28 Apr 2026 06:04:31 +0000</pubDate>
      <link>https://dev.to/patriciolumbe_cloud/aws-production-ready-beyond-the-hello-world-infrastructure-oib</link>
      <guid>https://dev.to/patriciolumbe_cloud/aws-production-ready-beyond-the-hello-world-infrastructure-oib</guid>
      <description>&lt;p&gt;Most portfolios show a single instance. Real production requires layers. I built this project to demonstrate a resilient, secure, and automated AWS ecosystem.&lt;/p&gt;

&lt;p&gt;
  &lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6dvvjpwkln16aaok5jpu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6dvvjpwkln16aaok5jpu.png" alt="AWS Architecture Blueprint" width="800" height="533"&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;Core Tech Stack&lt;br&gt;
IaC: Terraform (Strictly Modular)&lt;/p&gt;

&lt;p&gt;Compute: Multi-AZ EC2 Auto Scaling&lt;/p&gt;

&lt;p&gt;Security: WAFv2 + GuardDuty + Security Hub&lt;/p&gt;

&lt;p&gt;CI/CD: GitHub Actions (OIDC) + Blue/Green CodeDeploy&lt;/p&gt;

&lt;p&gt;SRE: CloudWatch + Lambda SLO Gates&lt;/p&gt;

&lt;p&gt;Key Features&lt;br&gt;
Zero Static Keys: Using OIDC Federation via GitHub Actions. No IAM keys stored in secrets.&lt;/p&gt;

&lt;p&gt;Automated Rollbacks: Blue/Green deployments via CodeDeploy. If health checks fail, it triggers an instant rollback.&lt;/p&gt;

&lt;p&gt;SLO-Driven Pipelines: A Lambda checker monitors the Error Budget. If it's breached, deployments are automatically blocked.&lt;/p&gt;

&lt;p&gt;Compliance as Code: Continuous monitoring via AWS Config to catch non-compliant resources in real-time.&lt;/p&gt;

&lt;p&gt;Repository Structure&lt;br&gt;
Bash&lt;br&gt;
├── modules/&lt;br&gt;
│   ├── networking/   # VPC, NAT GW, Flow Logs&lt;br&gt;
│   ├── security/     # OIDC, WAF, GuardDuty&lt;br&gt;
│   ├── compute/      # ASG, Launch Templates&lt;br&gt;
│   └── cicd/         # CodePipeline, CodeDeploy&lt;br&gt;
└── docs/adr/         # Architecture Decision Records (ADRs)&lt;/p&gt;

&lt;p&gt;How are you handling deployment gates in your current stack? Let's talk in the comments!&lt;/p&gt;

&lt;h1&gt;
  
  
  aws #terraform #devops #architecture
&lt;/h1&gt;

</description>
      <category>aws</category>
      <category>terraform</category>
      <category>devops</category>
      <category>cloud</category>
    </item>
  </channel>
</rss>
