<?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 PA outbound security policy - Terraform to AWS console in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-outbound-security-policy-terraform-to-aws-console/m-p/1231238#M5966</link>
    <description>&lt;P&gt;We have an on-prem dev environment with outbound access through a PA-3220 running&amp;nbsp;&lt;SPAN&gt;11.0.4-h6.&amp;nbsp; We are trying to craft a rule to allow an on-prem src to connect to AWS console to run terraform scripts.&lt;BR /&gt;&lt;BR /&gt;We've tried using application type amazon-aws-console with and without the web+ssl dependencies.&amp;nbsp; Also tried restricting it to just http+https with a URL category list including&lt;BR /&gt;sts.amazonaws.com&lt;BR /&gt;*.aws.amazon.com&lt;BR /&gt;*.console.aws.amazon.com&lt;BR /&gt;&lt;BR /&gt;It only works reliably if we simply allow http+https to any destination.&amp;nbsp; Browsing test traffic I would suspect it is all the redirects on the AWS side causing issues.&lt;BR /&gt;&lt;BR /&gt;Can anyone offer guidance or point to a KB that would detail the best way to handle this traffic?&amp;nbsp; Given the search terms I get a flood of results specific to running NGFW in AWS.&lt;BR /&gt;&lt;BR /&gt;Note also we have URL filtering license.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jun 2025 21:16:13 GMT</pubDate>
    <dc:creator>patrick.smith</dc:creator>
    <dc:date>2025-06-06T21:16:13Z</dc:date>
    <item>
      <title>PA outbound security policy - Terraform to AWS console</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-outbound-security-policy-terraform-to-aws-console/m-p/1231238#M5966</link>
      <description>&lt;P&gt;We have an on-prem dev environment with outbound access through a PA-3220 running&amp;nbsp;&lt;SPAN&gt;11.0.4-h6.&amp;nbsp; We are trying to craft a rule to allow an on-prem src to connect to AWS console to run terraform scripts.&lt;BR /&gt;&lt;BR /&gt;We've tried using application type amazon-aws-console with and without the web+ssl dependencies.&amp;nbsp; Also tried restricting it to just http+https with a URL category list including&lt;BR /&gt;sts.amazonaws.com&lt;BR /&gt;*.aws.amazon.com&lt;BR /&gt;*.console.aws.amazon.com&lt;BR /&gt;&lt;BR /&gt;It only works reliably if we simply allow http+https to any destination.&amp;nbsp; Browsing test traffic I would suspect it is all the redirects on the AWS side causing issues.&lt;BR /&gt;&lt;BR /&gt;Can anyone offer guidance or point to a KB that would detail the best way to handle this traffic?&amp;nbsp; Given the search terms I get a flood of results specific to running NGFW in AWS.&lt;BR /&gt;&lt;BR /&gt;Note also we have URL filtering license.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jun 2025 21:16:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-outbound-security-policy-terraform-to-aws-console/m-p/1231238#M5966</guid>
      <dc:creator>patrick.smith</dc:creator>
      <dc:date>2025-06-06T21:16:13Z</dc:date>
    </item>
  </channel>
</rss>

