<?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 Static Firewall Configuration for Privilege Cloud - Are CloudFront/EC2 IP Ranges Required in Addition to FQDNs? in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/static-firewall-configuration-for-privilege-cloud-are-cloudfront/m-p/1407954#M5784</link>
    <description>&lt;P&gt;We are deploying Privilege Cloud (SaaS) for a customer whose firewall performs SSL inspection and cannot allowlist wildcard domains. We are following the static configuration guide here: &lt;A alt="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the AWS SSL section, we have extracted the specific OCSP Responder, CA Issuer, and CRL FQDNs from our tenant's certificate chain (6 FQDNs total from the *.cyberark.cloud certificate hierarchy). Since these endpoints operate over HTTP (port 80), they do not require SSL inspection bypass - just allowlisting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, the Privilege Cloud section of the same doc also references CloudFront and EC2 IP ranges for us-east-1. When we filter ip-ranges.amazonaws.com/ip-ranges.json for CloudFront + EC2 in us-east-1, we get 500+ IP ranges.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Our questions:&lt;/B&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Are the CloudFront/EC2 IP ranges required in addition to the FQDNs already listed in the static config table, or are they an alternative to the wildcard *.amazonaws.com?&lt;/LI&gt;&lt;LI&gt;Has anyone successfully deployed Privilege Cloud with a static firewall config without opening 500+ IP ranges?&lt;/LI&gt;&lt;LI&gt;Is there a published FQDN list for these Privilege Cloud services rather than IP ranges?&lt;/LI&gt;&lt;LI&gt;For the CloudFront/EC2 IP ranges associated with Privilege Cloud service endpoints (port 443/HTTPS) - do these also need to be on the "do not decrypt" / SSL inspection bypass list on the firewall, in addition to being allowlisted? Or is allowlisting the IPs/FQDNs sufficient without bypassing SSL inspection for those ranges?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any guidance from the community would be greatly appreciated.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jun 2026 17:43:46 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-06-19T17:43:46Z</dc:date>
    <item>
      <title>Static Firewall Configuration for Privilege Cloud - Are CloudFront/EC2 IP Ranges Required in Addition to FQDNs?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/static-firewall-configuration-for-privilege-cloud-are-cloudfront/m-p/1407954#M5784</link>
      <description>&lt;P&gt;We are deploying Privilege Cloud (SaaS) for a customer whose firewall performs SSL inspection and cannot allowlist wildcard domains. We are following the static configuration guide here: &lt;A alt="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the AWS SSL section, we have extracted the specific OCSP Responder, CA Issuer, and CRL FQDNs from our tenant's certificate chain (6 FQDNs total from the *.cyberark.cloud certificate hierarchy). Since these endpoints operate over HTTP (port 80), they do not require SSL inspection bypass - just allowlisting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, the Privilege Cloud section of the same doc also references CloudFront and EC2 IP ranges for us-east-1. When we filter ip-ranges.amazonaws.com/ip-ranges.json for CloudFront + EC2 in us-east-1, we get 500+ IP ranges.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Our questions:&lt;/B&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Are the CloudFront/EC2 IP ranges required in addition to the FQDNs already listed in the static config table, or are they an alternative to the wildcard *.amazonaws.com?&lt;/LI&gt;&lt;LI&gt;Has anyone successfully deployed Privilege Cloud with a static firewall config without opening 500+ IP ranges?&lt;/LI&gt;&lt;LI&gt;Is there a published FQDN list for these Privilege Cloud services rather than IP ranges?&lt;/LI&gt;&lt;LI&gt;For the CloudFront/EC2 IP ranges associated with Privilege Cloud service endpoints (port 443/HTTPS) - do these also need to be on the "do not decrypt" / SSL inspection bypass list on the firewall, in addition to being allowlisted? Or is allowlisting the IPs/FQDNs sufficient without bypassing SSL inspection for those ranges?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any guidance from the community would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2026 17:43:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/static-firewall-configuration-for-privilege-cloud-are-cloudfront/m-p/1407954#M5784</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-06-19T17:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Static Firewall Configuration for Privilege Cloud - Are CloudFront/EC2 IP Ranges Required in Addition to FQDNs?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/static-firewall-configuration-for-privilege-cloud-are-cloudfront/m-p/1407955#M5785</link>
      <description>&lt;P&gt;Hi @Madhav Bhasin​,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like you are going through the hard way for static configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Open a support ticket with Idira asking the static IP list for your tenant.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2026 10:20:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/static-firewall-configuration-for-privilege-cloud-are-cloudfront/m-p/1407955#M5785</guid>
      <dc:creator>Uditha_A</dc:creator>
      <dc:date>2026-06-26T10:20:06Z</dc:date>
    </item>
  </channel>
</rss>

