Defender Deployment And Upgrade From Prisma Cloud Console

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
L3 Networker
100% helpful (1/1)

 

By RD Singh, Senior Customer Success Engineer

 

Demo Agenda:  Prisma Cloud Compute Defender Automation

 

Prerequisites:

 

  • Access to Live Community Article:

        Runtime Security: Auto-deploy DaemonSet Defender using Kubernetes Service Account

  • Admin access to AWS and Prisma Cloud console
  • EKS Cluster

 

Steps

 

  • Create service account
  • Generate kubeconfig to authenticate with EKS Cluster
  • Configure authentication credentials in the Prisma Cloud console
  • Deploy /upgrade the defender

 

About the Presenter:

 

RD Singh is a senior customer success engineer specializing in Prisma Cloud, Next-Generation Firewall, AWS, Azure, GCP, containers and Kubernetes. RD uses collaborative approaches to break down complex problems into solutions for global enterprise customers and leverage his multi industry knowledge to inspire success.

Rate this article:
(1)
Comments
L1 Bithead

Getting below error. 

 

Error fetching Daemonset: Get "https://EKS-Control-Plane-URL/apis/apps/v1/daemonsets?fieldselector=metadata.name%3Dtwistlock-defend...": dial tcp IPaddress:443:i/o timeout.

L1 Bithead

Seems like a connectivity issue. Console is not able to reach the cluster. Is there any firewall rule blocking the console IP to communicate to cluster api server?

  • 1209 Views
  • 2 comments
  • 2 Likes
Register or Sign-in
Contributors
Article Dashboard
Version history
Last Updated:
‎05-01-2024 09:48 AM
Updated by: