<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Building/Updating IPsec Tunnels Dynamically in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/building-updating-ipsec-tunnels-dynamically/m-p/170187#M97</link>
    <description>&lt;P&gt;Your DNS idea should work. &amp;nbsp;Another option is to create an address object that gets updated via our API when there is a change but I think the DNS option is cleaner.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or, better yet, can you change the EC2 instance to use an EIP? &amp;nbsp;When the EC2 instances gets blown away the EIP gets disassociated but not released. &amp;nbsp;Then you can re-associate&amp;nbsp;the same EIP to the new EC2 instance. &amp;nbsp;Then the firewall config won't need to change at all.&lt;/P&gt;</description>
    <pubDate>Sat, 05 Aug 2017 22:00:23 GMT</pubDate>
    <dc:creator>Warby</dc:creator>
    <dc:date>2017-08-05T22:00:23Z</dc:date>
    <item>
      <title>Building/Updating IPsec Tunnels Dynamically</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/building-updating-ipsec-tunnels-dynamically/m-p/170128#M96</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have roughly 30-40 VPN tunnels built to AWS from on-prem, each being used by a different business unit for development. What happens though, is during their process they are forced to blow away their EC2 instance and create a new one. AWS then assigns new public IPs to them. Is there any way for us to pull that information in and have our PANs update dynamically for the IPsec peer address? Right now we manually update them which is very time consuimg.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing I've thought of but haven't explore too much assigning each vpn tunnel a DNS record and having an external vendor or AWS provide the updated IP, using FQDN on our PANs.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2017 00:12:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/building-updating-ipsec-tunnels-dynamically/m-p/170128#M96</guid>
      <dc:creator>nicford</dc:creator>
      <dc:date>2017-08-05T00:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: Building/Updating IPsec Tunnels Dynamically</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/building-updating-ipsec-tunnels-dynamically/m-p/170187#M97</link>
      <description>&lt;P&gt;Your DNS idea should work. &amp;nbsp;Another option is to create an address object that gets updated via our API when there is a change but I think the DNS option is cleaner.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or, better yet, can you change the EC2 instance to use an EIP? &amp;nbsp;When the EC2 instances gets blown away the EIP gets disassociated but not released. &amp;nbsp;Then you can re-associate&amp;nbsp;the same EIP to the new EC2 instance. &amp;nbsp;Then the firewall config won't need to change at all.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2017 22:00:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/building-updating-ipsec-tunnels-dynamically/m-p/170187#M97</guid>
      <dc:creator>Warby</dc:creator>
      <dc:date>2017-08-05T22:00:23Z</dc:date>
    </item>
  </channel>
</rss>

