<?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: Prisma Access location and Compute location in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-location-and-compute-location/m-p/563563#M609</link>
    <description>&lt;P&gt;1. Compute location is the actual point of egress for traffic whereas location can be referred to as edge location to route the traffic quickly to the compute for processing .&lt;BR /&gt;2. Well the whole purpose of having an edge location is to reduce latency and ensure traffic reaches the computer faster.&lt;/P&gt;
&lt;P&gt;3. Your IP will be sourced from the actual location you have onboarded.&lt;/P&gt;
&lt;P&gt;4. AWS and GCP have similar architecture, I believe you can reference the same to have some insights into this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Oct 2023 16:53:49 GMT</pubDate>
    <dc:creator>znazir</dc:creator>
    <dc:date>2023-10-30T16:53:49Z</dc:date>
    <item>
      <title>Prisma Access location and Compute location</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-location-and-compute-location/m-p/562488#M604</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have some questions about Prisma Access locations (RN-SPN vs MU-SPN), but I was unable to discover the answers in the documents that were provided. It would be wonderful if you could clarify something for me:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Difference between Prisma Access location vs compute location&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.&amp;nbsp; How it will affect my overall traffic flow if Access location are just entry point and traffic getting egress from somewhere else&lt;/P&gt;
&lt;P&gt;3. If my access location is in a country A and my compute location in country B,&amp;nbsp; then&amp;nbsp; how can ensure that my traffic is not crossing my boundary for certain apps where i has location specific restriction&lt;/P&gt;
&lt;P&gt;4. Any reference architecture or study material will be helpful.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 21:24:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-location-and-compute-location/m-p/562488#M604</guid>
      <dc:creator>Vishal_Mandliya</dc:creator>
      <dc:date>2023-10-19T21:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: Prisma Access location and Compute location</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-location-and-compute-location/m-p/563563#M609</link>
      <description>&lt;P&gt;1. Compute location is the actual point of egress for traffic whereas location can be referred to as edge location to route the traffic quickly to the compute for processing .&lt;BR /&gt;2. Well the whole purpose of having an edge location is to reduce latency and ensure traffic reaches the computer faster.&lt;/P&gt;
&lt;P&gt;3. Your IP will be sourced from the actual location you have onboarded.&lt;/P&gt;
&lt;P&gt;4. AWS and GCP have similar architecture, I believe you can reference the same to have some insights into this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2023 16:53:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/prisma-access-location-and-compute-location/m-p/563563#M609</guid>
      <dc:creator>znazir</dc:creator>
      <dc:date>2023-10-30T16:53:49Z</dc:date>
    </item>
  </channel>
</rss>

