<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Well Architected on My AWS Rocks!</title><link>https://www.myaws.rocks/tags/well-architected/</link><description>Recent content in Well Architected on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 06 Dec 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.myaws.rocks/tags/well-architected/index.xml" rel="self" type="application/rss+xml"/><item><title>How to use NACLs and Security Groups</title><link>https://www.myaws.rocks/how-to-use-nacls-and-security-groups/</link><pubDate>Tue, 06 Dec 2022 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/how-to-use-nacls-and-security-groups/</guid><description>&lt;p&gt;Following up from my last post &lt;a href="https://www.myaws.rocks/nacl-vs-security-group/"&gt;here&lt;/a&gt; on what Network Access Control Lists (NACLs) and Security Groups (SGs) are, I will now take a look at where and how I think you should use them to ensure you have a secure network.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll use a basic scenario of a VPC (10.0.0.0/16) split into two public subnets, with access to the internet (10.0.0.0/24 and 10.0.1.0/24), and two private subnets, with no route the the internet (10.0.10.0/24 and 10.0.1.0/24). The application is running on 2 EC2 behind an application load balancer to discuss the options.&lt;/p&gt;</description></item></channel></rss>