<?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: About Service Connection with AWS in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000214#M1042</link>
    <description>&lt;P&gt;thanks for reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but aws tunnel is only change in 169.254.0.0/16. this subnet is using strata cloud too.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jan 2025 04:38:47 GMT</pubDate>
    <dc:creator>sujichoi</dc:creator>
    <dc:date>2025-01-07T04:38:47Z</dc:date>
    <item>
      <title>About Service Connection with AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000210#M1040</link>
      <description>&lt;P&gt;hello&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I am using AWS by connecting to service connection. (using prisma cloud)&lt;/P&gt;
&lt;P&gt;Is there anyone who runs both primary and secondary tunnel connecting AWS?&lt;/P&gt;
&lt;P&gt;In my case, bgp neighbor setup was not possible due to the 169.254.0.0/16 band.&lt;/P&gt;
&lt;P&gt;It was running statically, but the secondary tunnel was not live, so even if I ran a tunnel monitor, the 169.254.0.0/16 band overlapped, so tunnel monitoring did not turn on, making communication impossible.&lt;/P&gt;
&lt;P&gt;Are you also only using one primary tunnel when connecting to AWS?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 01:41:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000210#M1040</guid>
      <dc:creator>sujichoi</dc:creator>
      <dc:date>2025-01-07T01:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: About Service Connection with AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000212#M1041</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/270775"&gt;@sujichoi&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;hello&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I am using AWS by connecting to service connection. (using prisma cloud)&lt;/P&gt;
&lt;P&gt;Is there anyone who runs both primary and secondary tunnel connecting AWS?&lt;/P&gt;
&lt;P&gt;In my case, bgp neighbor setup was not possible due to the 169.254.0.0/16 band.&lt;/P&gt;
&lt;P&gt;It was running statically, but the secondary tunnel was not live, so even if I ran a tunnel monitor, the 169.254.0.0/16 band overlapped, so tunnel monitoring did not turn on, making communication impossible.&lt;/P&gt;
&lt;P&gt;Are you also only using one primary tunnel when connecting to AWS?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/270775"&gt;@sujichoi&lt;/a&gt;&amp;nbsp;, check these two links out, I think it may address your questions:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Tunnel options for your AWS Site-to-Site VPN connection:&amp;nbsp;&lt;A href="https://docs.aws.amazon.com/vpn/latest/s2svpn/VPNTunnels.html" target="_blank"&gt;https://docs.aws.amazon.com/vpn/latest/s2svpn/VPNTunnels.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Onboard an AWS Virtual Private Cloud:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/prisma-access/integration/secure-public-cloud-deployment-with-prisma-access/onboard-an-aws-virtual-private-cloud" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma-access/integration/secure-public-cloud-deployment-with-prisma-access/onboard-an-aws-virtual-private-cloud&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Vickynet&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 03:16:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000212#M1041</guid>
      <dc:creator>Vickynet</dc:creator>
      <dc:date>2025-01-07T03:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: About Service Connection with AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000214#M1042</link>
      <description>&lt;P&gt;thanks for reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but aws tunnel is only change in 169.254.0.0/16. this subnet is using strata cloud too.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 04:38:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/about-service-connection-with-aws/m-p/1000214#M1042</guid>
      <dc:creator>sujichoi</dc:creator>
      <dc:date>2025-01-07T04:38:47Z</dc:date>
    </item>
  </channel>
</rss>

