<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Transit-Vpc on The IT Hollow</title>
    <link>https://theithollow.com/tags/transit-vpc/</link>
    <description>Recent content in Transit-Vpc on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Jul 2018 14:05:46 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/transit-vpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Should I use a Transit VPC in AWS?</title>
      <link>https://theithollow.com/2018/07/16/should-i-use-a-transit-vpc-in-aws/</link>
      <pubDate>Mon, 16 Jul 2018 14:05:46 +0000</pubDate>
      <guid>https://theithollow.com/2018/07/16/should-i-use-a-transit-vpc-in-aws/</guid>
      <description>&lt;p&gt;A common question that comes up during AWS designs is, &amp;ldquo;Should I use a transit VPC?&amp;rdquo; The answer, like all good IT riddles is, &amp;ldquo;it depends.&amp;rdquo; There are a series of questions that you must ask yourself before deciding whether to use a Transit VPC or not. In this post, I&amp;rsquo;ll try to help formulate those questions so you can answer this question yourself.&lt;/p&gt;
&lt;h1 id=&#34;the-basics&#34;&gt;The Basics&lt;/h1&gt;
&lt;p&gt;Before we can ask those tough questions, we first should answer the question, &amp;ldquo;What is a Transit VPC?&amp;rdquo; Well, a transit VPC acts as an intermediary for routing between two places. Just like a transit network bridges traffic between two networks, a transit VPC ferries traffic between two VPCs or perhaps your data center.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
