title: AWS VPC subnet route table best practices
body: <p>In AWS we have subnets tired like <strong>public</strong> and <strong>private</strong> subnets.</p>
  <p><strong>To simplify the question, I am only referring to the private subnet.</strong></p>
  <p>I know we can use single routing table for private subnets in all AZs, or we can use multiple routing table per private subnets in all AZs (One per AZ).</p>
  <p>My question is, what is the best practice to design this? should I create different routing table for subnets in each AZs or should create single routing table for subnets in all AZs? what would be the recommended approach and what is advantage of the recommended approach?</p>
  <p>Please note, the reason I'm asking this is, I have seen this both approaches being used in different environments and trying to understand what would be the good approach.</p>