<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security Group on Adam Divall</title>
    <link>/tags/security-group/</link>
    <description>Recent content in Security Group on Adam Divall</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 09 Mar 2023 20:52:16 +0000</lastBuildDate>
    <atom:link href="/tags/security-group/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Field Notes: Using Amazon VPC Prefixes with Security Groups</title>
      <link>/article/troubleshooting/vpc-prefix-sg/</link>
      <pubDate>Thu, 09 Mar 2023 20:52:16 +0000</pubDate>
      <guid>/article/troubleshooting/vpc-prefix-sg/</guid>
      <description>&lt;p&gt;Recently during a Customer engagement I encountered what seemed to be a fairly straightforward issues with a Security Group that was running into a service quota isssue with the number of Inbound or outbound rules per security group.&lt;/p&gt;&#xA;&lt;h3 id=&#34;background-to-the-issue&#34;&gt;Background to the Issue&lt;/h3&gt;&#xA;&lt;p&gt;To give a little bit of context, this particulary security group was associated with a couple of Amazon EC2 Instances that were running Microsoft Windows Server 2019 and performing the function of Active Directory Domain Controllers that were being self-managed by the Customer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
