<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Groups on Neshon Shrestha</title><link>https://neshonshrestha.com/tags/security-groups/</link><description>Recent content in Security-Groups on Neshon Shrestha</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://neshonshrestha.com/tags/security-groups/index.xml" rel="self" type="application/rss+xml"/><item><title>Copying AWS Security Groups Across VPCs</title><link>https://neshonshrestha.com/kb/aws-security-groups-copy/</link><pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate><guid>https://neshonshrestha.com/kb/aws-security-groups-copy/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;Customers often need to replicate security group configurations when migrating workloads across VPCs, regions, or AWS accounts. This comes up during disaster recovery setup, multi-region deployments, or account migrations.&lt;/p&gt;
&lt;h2 id="why-this-isnt-straightforward"&gt;Why This Isn&amp;rsquo;t Straightforward&lt;/h2&gt;
&lt;p&gt;AWS doesn&amp;rsquo;t provide a native one-click way to copy a security group to a different VPC. The console only lets you copy within the same VPC/region. If you&amp;rsquo;re moving across regions or accounts, you&amp;rsquo;re stuck manually recreating rules — which is error-prone when a security group has dozens of rules.&lt;/p&gt;</description></item></channel></rss>