<?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>Restore on The IT Hollow</title>
    <link>https://theithollow.com/tags/restore/</link>
    <description>Recent content in Restore on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Oct 2018 14:03:21 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/restore/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Restore or Resize an AWS Transit Router</title>
      <link>https://theithollow.com/2018/10/22/restore-or-resize-an-aws-transit-router/</link>
      <pubDate>Mon, 22 Oct 2018 14:03:21 +0000</pubDate>
      <guid>https://theithollow.com/2018/10/22/restore-or-resize-an-aws-transit-router/</guid>
      <description>&lt;p&gt;A transit VPC is a pretty common networking pattern in an AWS environment. [Transit VPCs](http://Should I use a Transit VPC in AWS?) can limit the number of peering connections required to connect all your VPCs by switching from a mesh topology of peers to a hub and spoke method with transit. While transit VPCs offer some nice features, it also requires a bit more management overhead since you need to manage your own routers. Cisco makes the deployment of transit routers very easy but sometimes you need to make some changes to the routers after they&amp;rsquo;re deployed like if you need to resize them. Also, sometimes bad things happen and those routers can be destroyed by accident. This post shows how you can resize your Cisco CSRs and/or restore an old configuration from snapshot.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
