<?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 API keys for Autoscale with GWLB deployment in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/api-keys-for-autoscale-with-gwlb-deployment/m-p/532453#M1817</link>
    <description>&lt;P&gt;We are attempting to deploy Cloud Formation Templates to create the autoscaling groups and firewalls but there are some steps around API keys that are confusing. From the pictures seen below, we are being asked for API keys for the panorama, and for the firewalls, and then the csp lisence key. My confusion points are as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. For the firewall API keys, we can't generate those as the firewalls aren't stood up yet. It's a chicken-and-egg scenario where it's asking for them in order to stand them up...???&lt;/P&gt;
&lt;P&gt;2. Not really sure why it's asking for the csp license key as another step has us create an authcodes file and put it in the /license folder in the bootstrap location in s3.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Verac22_1-1677589320646.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/48226i508E154106E0AFDF/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Verac22_1-1677589320646.png" alt="Verac22_1-1677589320646.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Verac22_0-1677589313584.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/48225i7B6E4A41DB3263A9/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Verac22_0-1677589313584.png" alt="Verac22_0-1677589313584.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any insight into this is much appreciated!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2023 13:04:12 GMT</pubDate>
    <dc:creator>Verac22</dc:creator>
    <dc:date>2023-02-28T13:04:12Z</dc:date>
    <item>
      <title>API keys for Autoscale with GWLB deployment</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/api-keys-for-autoscale-with-gwlb-deployment/m-p/532453#M1817</link>
      <description>&lt;P&gt;We are attempting to deploy Cloud Formation Templates to create the autoscaling groups and firewalls but there are some steps around API keys that are confusing. From the pictures seen below, we are being asked for API keys for the panorama, and for the firewalls, and then the csp lisence key. My confusion points are as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. For the firewall API keys, we can't generate those as the firewalls aren't stood up yet. It's a chicken-and-egg scenario where it's asking for them in order to stand them up...???&lt;/P&gt;
&lt;P&gt;2. Not really sure why it's asking for the csp license key as another step has us create an authcodes file and put it in the /license folder in the bootstrap location in s3.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Verac22_1-1677589320646.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/48226i508E154106E0AFDF/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Verac22_1-1677589320646.png" alt="Verac22_1-1677589320646.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Verac22_0-1677589313584.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/48225i7B6E4A41DB3263A9/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Verac22_0-1677589313584.png" alt="Verac22_0-1677589313584.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any insight into this is much appreciated!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2023 13:04:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/api-keys-for-autoscale-with-gwlb-deployment/m-p/532453#M1817</guid>
      <dc:creator>Verac22</dc:creator>
      <dc:date>2023-02-28T13:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: API keys for Autoscale with GWLB deployment</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/api-keys-for-autoscale-with-gwlb-deployment/m-p/533756#M1835</link>
      <description>&lt;P&gt;I eventually received a response from support. Apparently even though the API key looks different, it is still valid if generated on a device using a same user/password pair and then reused on a new device.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 12:52:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/api-keys-for-autoscale-with-gwlb-deployment/m-p/533756#M1835</guid>
      <dc:creator>Verac22</dc:creator>
      <dc:date>2023-03-09T12:52:09Z</dc:date>
    </item>
  </channel>
</rss>

