From a4ca58189150bec53dc81e1d178bf20373853a39 Mon Sep 17 00:00:00 2001 From: solalraveh Date: Fri, 19 Jun 2020 10:46:40 +0300 Subject: [PATCH 1/2] Update install_swarm.adoc modified to distinguish saas and self-hosted --- admin_guide/install/install_swarm.adoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/admin_guide/install/install_swarm.adoc b/admin_guide/install/install_swarm.adoc index 085c84b3..563ccfaa 100644 --- a/admin_guide/install/install_swarm.adoc +++ b/admin_guide/install/install_swarm.adoc @@ -316,9 +316,9 @@ Console provides a GUI to configure all the options required to deploy Defender [.procedure] . Open Console. +ifdef::compute_edition[] . Go to *Manage > Defenders > Names*. -ifdef::compute_edition[] . Click *Add SAN*, and add the DNS name of your load balancer. . Go to *Manage > Defenders > Deploy > Swarm*. @@ -358,7 +358,12 @@ You need sudo privileges to run this command. . Validate that the Defender global service is running. + +ifdef::prisma_cloud[] +Open Console, then go to *Compute > Manage > Defenders > Manage*. +endif::prisma_cloud[] +ifdef::compute_edition[] Open Console, then go to *Manage > Defenders > Manage*. +endif::compute_edition[] The table lists all Defenders deployed to your environment (one per node). From 83e60f92eb9730ce8cada106bd672f47619f2102 Mon Sep 17 00:00:00 2001 From: solalraveh Date: Fri, 19 Jun 2020 11:07:15 +0300 Subject: [PATCH 2/2] updates to port 443 on saas updated openshift install and connectivity flow to call out 443. diagram png file needs to be modified --- admin_guide/install/install_openshift.adoc | 2 +- ref_arch/platform_components/connectivity_flows.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/admin_guide/install/install_openshift.adoc b/admin_guide/install/install_openshift.adoc index a69194af..dc698b13 100644 --- a/admin_guide/install/install_openshift.adoc +++ b/admin_guide/install/install_openshift.adoc @@ -76,7 +76,7 @@ ifdef::prisma_cloud[] [.section] ==== Network connectivity -Validate that outbound connections can be made on port 8084. +Validate that outbound connections to your Console can be made on port 443. endif::prisma_cloud[] diff --git a/ref_arch/platform_components/connectivity_flows.adoc b/ref_arch/platform_components/connectivity_flows.adoc index 8ed19c33..e1d2acab 100644 --- a/ref_arch/platform_components/connectivity_flows.adoc +++ b/ref_arch/platform_components/connectivity_flows.adoc @@ -18,7 +18,7 @@ interoperate with firewalls wherever necessary, provided the required TCP ports are open. When using Prisma Cloud Compute Saas Console customers will need to provide connectivity -from their deployed Defenders to the SaaS Console through the firewalls. +from their deployed Defenders to the SaaS Console through the firewalls on port 443. === Istio