<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration on EdFig.dev</title><link>https://hugo.edfig.dev/tags/migration/</link><description>Recent content in Migration on EdFig.dev</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 24 Feb 2026 14:20:19 -0800</lastBuildDate><atom:link href="https://hugo.edfig.dev/tags/migration/index.xml" rel="self" type="application/rss+xml"/><item><title>Formatting AWS Security Groups for a VMware Migration</title><link>https://hugo.edfig.dev/docs/posts/security-groups/</link><pubDate>Wed, 05 Feb 2025 00:00:00 +0000</pubDate><guid>https://hugo.edfig.dev/docs/posts/security-groups/</guid><description>&lt;h1 id="the-problem">The Problem&lt;a class="anchor" href="#the-problem">#&lt;/a>&lt;/h1>
&lt;p>At work we&amp;rsquo;re in the middle of a large lift and shift migration from VMware to AWS (for the same reason everyone is). Hundreds of servers across multiple departments, moved in waves.&lt;/p>
&lt;p>The firewall rules for these servers come from everywhere. Palo Alto firewalls, host-based firewalls, department-specific switches, department-specific IT teams, random appliances that predate much of the current staff. Years of accumulated rules from multiple sources, and now they all need to become AWS security groups.&lt;/p></description></item></channel></rss>