Given an existing ECS Cluster, which option shows the steps required to install the Console in Amazon ECS?

The correct steps to install the Prisma Cloud Compute Console in an Amazon ECS cluster involve ensuring data persistence and availability. The Console requires a shared, persistent file system so that if the Console task is rescheduled to a different EC2 instance, it can access its existing data. Amazon EFS (Elastic File System) provides this capability. Therefore, the correct procedure is to download the release, create and mount a shared EFS file system to the cluster nodes, create the ECS task definition referencing the EFS volume, and then deploy the task.

A. The Console can be deployed natively in an ECS cluster; a onebox deployment is typically for non-production or small-scale environments.
B. Using local storage on each node is incorrect because the Console data would be lost or inaccessible if the task moves to a different node.
C. "Download task from AWS" is not a standard step; an administrator creates a task definition based on the vendor's specifications, not downloads it from AWS.

1. Palo Alto Networks, "Prisma Cloud Administrator’s Guide (Compute)", Version Self-Hosted 32.01, Chapter: "Install Console on an ECS Cluster". This section explicitly states the prerequisite: "Create a shared file system, such as AWS EFS, and mount it on all the EC2 instances in your ECS cluster. The Console needs a persistent storage solution."

2. Palo Alto Networks, "Prisma Cloud Administrator’s Guide (Compute)", Version Self-Hosted 32.01, Chapter: "Install Console on an ECS Cluster", Section: "Create the Console task definition". This part of the guide details creating the task definition, which includes configuring the volume mount for the shared EFS file system.