<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>peraleslab.com</title><link>https://peraleslab.com/</link><description>Recent content on peraleslab.com</description><generator>Hugo</generator><language>en-us</language><copyright>peraleslab.com</copyright><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peraleslab.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Building peraleslab.com: Hugo + S3 + CloudFront + Terraform</title><link>https://peraleslab.com/build-logs/building-peraleslab-com-hugo-s3-cloudfront-terraform/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://peraleslab.com/build-logs/building-peraleslab-com-hugo-s3-cloudfront-terraform/</guid><description>&lt;h2 id="why-build-this-myself"&gt;Why build this myself?&lt;/h2&gt;
&lt;p&gt;A conversation I&amp;rsquo;ve encountered repeatedly throughout my career goes
something like this: someone asks how a system is deployed, how a
particular part of the environment works, or why something was designed a
certain way — and the honest answer is, &amp;ldquo;Let me check the documentation. I
didn&amp;rsquo;t build that part.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;That is normal in enterprise IT. No one person owns every layer of a large
system.&lt;/p&gt;</description></item><item><title>About</title><link>https://peraleslab.com/about/</link><pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate><guid>https://peraleslab.com/about/</guid><description>&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m a cloud architect based in Texas with more than 20 years in enterprise
IT, much of that time at IBM working across cloud transformation, migration,
and modernization.&lt;/p&gt;
&lt;p&gt;My career started as a Windows NT administrator, on a pager rotation, keeping
servers running at 2 a.m. From there, I moved through server consolidation,
data center relocations, infrastructure transformation, and eventually into
architecture — leading migration and modernization engagements across
banking, energy, pharmaceuticals, insurance, and government.&lt;/p&gt;</description></item><item><title>Adopting Existing AWS Infrastructure into Terraform</title><link>https://peraleslab.com/build-logs/adopting-existing-aws-infrastructure-into-terraform/</link><pubDate>Thu, 08 May 2025 00:00:00 +0000</pubDate><guid>https://peraleslab.com/build-logs/adopting-existing-aws-infrastructure-into-terraform/</guid><description>&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Bringing hand-built
AWS infrastructure under Terraform management is rarely a clean slate — it&amp;rsquo;s
an exercise in careful importing, refactoring, and stabilizing what already
exists in production.&lt;/p&gt;
&lt;p&gt;Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore.
This post covers a practical, low-risk approach: import first, refactor
second, and never let &lt;code&gt;plan&lt;/code&gt; surprise you.&lt;/p&gt;</description></item><item><title>OIDC Deploy Pipelines with GitHub Actions and AWS</title><link>https://peraleslab.com/build-logs/oidc-deploy-pipelines-with-github-actions-and-aws/</link><pubDate>Mon, 28 Apr 2025 00:00:00 +0000</pubDate><guid>https://peraleslab.com/build-logs/oidc-deploy-pipelines-with-github-actions-and-aws/</guid><description>&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. GitHub Actions can
assume an AWS IAM role directly via its built-in OIDC identity provider,
removing the need to store long-lived AWS access keys as repository secrets.&lt;/p&gt;
&lt;p&gt;Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut
aliquip ex ea commodo consequat. This post walks through configuring the
trust policy, scoping the role&amp;rsquo;s permissions, and wiring the workflow.&lt;/p&gt;</description></item><item><title>Running a Home Lab with Cloudflare Tunnel</title><link>https://peraleslab.com/lab-notes/running-a-home-lab-with-cloudflare-tunnel/</link><pubDate>Sun, 20 Apr 2025 00:00:00 +0000</pubDate><guid>https://peraleslab.com/lab-notes/running-a-home-lab-with-cloudflare-tunnel/</guid><description>&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cloudflare Tunnel
lets home lab services reach the internet without opening a single inbound
port on the router — the tunnel daemon initiates an outbound connection and
Cloudflare handles the rest.&lt;/p&gt;
&lt;p&gt;Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia
deserunt mollit anim id est laborum. This post covers setup, routing multiple
services, and the tradeoffs versus a traditional reverse proxy.&lt;/p&gt;</description></item><item><title>EC2 Right-Sizing: Practical Lessons from Real Assessments</title><link>https://peraleslab.com/migration/ec2-right-sizing-practical-lessons-from-real-assessments/</link><pubDate>Sat, 12 Apr 2025 00:00:00 +0000</pubDate><guid>https://peraleslab.com/migration/ec2-right-sizing-practical-lessons-from-real-assessments/</guid><description>&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Right-sizing EC2
fleets is less about hitting a utilization target and more about
understanding burst patterns, workload shape, and the cost of getting it
wrong in either direction.&lt;/p&gt;
&lt;p&gt;At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis
praesentium. This post walks through a real assessment: the data collected,
the instance families considered, and the recommendation delivered.&lt;/p&gt;</description></item></channel></rss>