Install Panorama on AWS
Table of Contents
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on Alibaba Cloud
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on Alibaba Cloud
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase the CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
- Install the Device Certificate for a Dedicated Log Collector
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
- Configure Tracking of Administrator Activity
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Device Group Push to a Multi-VSYS Firewall
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Schedule a Configuration Push to Managed Firewalls
- Redistribute Data to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Configure a Managed Collector
- Configure Log Forwarding to Panorama
- Configure Syslog Forwarding to External Destinations
- Forward Logs to Strata Logging Service
- Verify Log Forwarding to Panorama
- Modify Log Forwarding and Buffering Defaults
- Configure Log Forwarding from Panorama to External Destinations
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
-
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- View Log Query Jobs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- View Task Success or Failure Status
- Generate a Stats Dump File for a Managed Firewall
- Recover Managed Device Connectivity to Panorama
- Restore an Expired Device Certificate
Install Panorama on AWS
How to deploy a Panorama™ virtual appliance and a virtual
Dedicated Log Collector on Amazon Web Services.
You can now deploy Panorama™ and a Dedicated
Log Collector on Amazon Web Services (AWS). Panorama deployed on
AWS is Bring Your Own License (BYOL), supports all deployment modes
(Panorama, Log Collector, and Management Only), and shares the same
processes and functionality as the M-Series hardware appliances.
For more information on Panorama modes, see Panorama
Models.
- Log in to AWS Web Service console and select the EC2 Dashboard.Set up the virtual private cloud (VPC) for your network needs.Whether you launch the Panorama virtual appliance in an existing VPC or you create a new VPC, the Panorama virtual appliance must be able to receive traffic from other instances in the VPC and perform inbound and outbound communication between the VPC and the internet as needed.Refer to the AWS VPC documentation for instructions on creating a VPC and setting it up for access.
- Create a new VPC or use an existing VPC. Refer to the AWS Getting Started documentationVerify that the network and security components are appropriately defined.
- Create an internet gateway to enable internet access to the subnet of your Panorama virtual appliance. Internet access is required to install software and content updates, activate licenses, and leverage Palo Alto Networks cloud services. Otherwise, you must manually install updates and activate licenses.
- Create subnets. Subnets are segments of the IP address range assigned to the VPC in which you can launch AWS instances. It is recommended that the Panorama virtual appliance belong to the management subnet so that you can configure it to access the internet if needed.
- Add routes to the route table for a private subnet to ensure traffic can be routed across subnets in the VPC and from the internet if applicable.Ensure you create routes between subnets to allow communication between:
- Panorama, managed firewalls, and Log Collectors.
- (Optional) Panorama and the internet.
- Ensure that the following inbound security rules are allowed for the VPC to manage VPC traffic. The ingress traffic source for each rule is unique to your deployment topology.See Ports Used for Panorama for more information.
- Allow SSH (port 22) traffic to enable access to the Panorama CLI.
- Allow HTTPS (port 443) traffic to enable access to the Panorama web interface.
- Allow traffic on port 3978 to enable communication between Panorama, manage firewalls, and managed Log Collectors. This port is also used by Log Collectors to forward logs to Panorama.
- Allow traffic on port 28443 to enable managed firewalls to get software and content updates from Panorama.
Deploy Panorama on Amazon Web Services.- Select ServicesEC2Instances and Launch Instance.Select AWS Marketplace, search for Palo Alto Networks Panorama, and Select the Panorama AMI and Continue.Choose the EC2 instance type for allocating the resources required for the Panorama virtual appliance, and click Next: Configure Instance Details. Review the Setup Prerequisites for the Panorama Virtual Appliance for resource requirements.If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you configure the appliance with the required resources during initial deployment. The Panorama virtual appliance does not remain in Log Collector mode if you resize the virtual machine after you deploy it, and this results in a loss of log data.Configure the instance details.
- Select Next: Configure Instance Details.
- For the Network, select the VPC.
- Select the Subnet.
- To Auto-assign Public IP select Enable.This IP must be accessible by the firewalls you plan to manage using Panorama. This allows you to obtain a publicly accessible IP address for the management interface of the Panorama virtual appliance. You can later attach an Elastic IP address to the management interface. Unlike the public IP address that is disassociated from the virtual appliance when the instance is terminated, the Elastic IP address provides persistence and you can the IP address to a new (or replacement) instance of the Panorama virtual appliance without the need to reconfigure the IP address whenever the Panorama virtual appliance instance is powered off.
- Configure any additional instance details as needed.
(Optional) Configure the Panorama virtual appliance storage.- Select Next: Add Storage.
- Add New Volume to add additional log storage.(SD-WAN only) If you plan on managing your SD-WAN deployment in Management Only mode, you must add a 2TB logging disk.If you intend to use the Panorama virtual appliance in Panorama mode or as a Dedicated Log Collector, add the virtual logging disks during the initial deployment. By default, the Panorama virtual appliance is in Panorama mode for the initial deployment when you meet the Panorama mode resource requirements and have added at least one virtual logging disk. Otherwise, the Panorama virtual appliance defaults to Management Only mode. Change the Panorama virtual appliance to Management Only mode if you just want to manage devices and Dedicated Log Collectors, and to not collect logs locally.The Panorama virtual appliance on AWS only supports 2TB logging disks, and in total supports up to 24TB of log storage. You are unable to add a logging disk smaller than 2TB, or a logging disk with a size not divisible by the 2TB logging disk requirement. The Panorama virtual appliance partitions logging disks larger than 2TB into 2TB partitions.
(Optional) Select Next: Add Tags and add one or more tags as metadata to help you identify and group the Panorama virtual appliance. For example, add a Name tag with a Value that helps you identify which firewalls the Panorama virtual appliance manages.Configure the instance security group.- Select Next: Configure Security Group.
- Select an existing security group to assign a security group for the Panorama virtual appliance instance.
- Select the security group you previously created.You can select the default security group to allow all inbound and outbound traffic types.
Review and Launch the Panorama virtual appliance instance to verify that your selections are accurate before you Launch.Select an existing key pair or create a new one and acknowledge the disclaimer.If you created a new key from AWS, download and save the key to a safe location. The file extension is .pem. You must load the public key into PuTTYgen and save it in .ppk format. You cannot regenerate this key if lost.It takes about 30 minutes to finish deploying the Panorama virtual appliance after you launch it on AWS. Deploying the Panorama virtual appliance may take longer depending on the number and size of the disks attached to the instance. View the Launch Time by selecting the Panorama virtual appliance instance (Instances).If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you provision the appliance with the required resources. The Panorama virtual appliance does not remain in Log Collector mode if you resize the virtual machine after you deploy it and this results in a loss of log data.Shut down the Panorama virtual appliance.- On the EC2 Dashboard, select Instances.Select the Panorama virtual appliance and click Instance StateStop Instance.Create or assign an Elastic IP (EIP) address to the management interface.
- Select ServicesEC2Elastic IPs and Allocate Elastic IP address.Select a Network Border Group to specify the logical group of zones from where the public IP4v address is advertised.For the Public IPv4 address pool, select Amazon’s pool of IPv4 addresses.Allocate the EIP.Click the IPv4 address in the Allocated IPv4 address column and Associate Elastic IP address.Select the Panorama virtual appliance Instance.Select the Panorama virtual appliance Private IP address to with which to associate the EIP.Power on the Panorama virtual appliance.
- On the EC2 Dashboard, select Instance.From the list, select the Panorama virtual appliance and click ActionsInstance StateStart.Configure a new administrative password for the Panorama virtual appliance.You must configure a unique administrative password before you can access the web interface of the Panorama virtual appliance. To access the CLI, the private key used to launch the Panorama virtual appliance is required.The new password must be a minimum of eight characters and include a minimum of one lowercase character, one uppercase character, and one number or special character.
- If you have an SSH service installed on your computer:
- Enter the following command to log into the Panorama virtual appliance:
ssh -i <private_key.ppk> admin@<public-ip_address>
Configure a new password using the following commands and follow the on screen prompts:admin> configure admin# set mgt-config users admin password
If you need to activate a BYOL, set the DNS server IP address so that the Panorama virtual appliance can access the Palo Alto Networks licensing server. Enter the following command to set the DNS server IP address:admin# set deviceconfig system dns-setting servers primary <ip_address>
Commit your changes with the command:admin# commit
Terminate the SSH session.- If you are using PuTTY to SSH into the Panorama virtual appliance:
- If you are using an existing key pair and have the .ppk file available, continue to the Step 7.3. If you created a new key pair or have only the .pem file of the existing key pair, open PuTTYgen and Load the .pem file.Save the private key to a local accessible destination.Open PuTTY and select SSHAuth and then Browse to the .ppk file you saved in the previous step.Select Sessions and enter the public IP address of the Panorama virtual appliance. Click Open and click Yes when the security prompt appears.Log in as admin when prompted.Configure a new password using the following commands and follow the onscreen prompts:
admin> configure admin# set mgt-config users admin password
Set the DNS server IP address so that the Panorama virtual appliance can access the Palo Alto Networks licensing server. Enter the following command to set the DNS server IP address:admin# set deviceconfig system dns-setting servers primary <ip_address>
Commit your changes with the command:admin# commit
Terminate the SSH session.Register the Panorama virtual appliance and activate the device management license and support licenses.- (VM Flex Licensing Only) Provisioning the Panorama Virtual Appliance Serial Number.When leveraging VM Flex licensing, this step is required to generate the Panorama virtual appliance serial number needed to register the Panorama virtual appliance with the Palo Alto Networks Customer Support Portal (CSP).Register Panorama.You must register the Panorama virtual appliance using the serial number provided by Palo Alto Networks in the order fulfillment email.This step is not required when leveraging VM Flex licensing as the serial number is automatically registered with the CSP when generated.Activate the firewall management license.Activate a Panorama Support License.Complete configuring the Panorama virtual appliance for your deployment needs.
- For Panorama in Log Collector Mode.
- Add a Virtual Disk to Panorama on AWS as needed.Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Log Collector mode.
- Begin at Step 6 to switch to Log Collector mode.Enter the Public IP address of the Dedicated Log Collector when you add the Log Collector as a managed collector to the Panorama management server. You cannot specify the IP Address, Netmask, or Gateway.
- For Panorama in Panorama mode.
- Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Panorama mode.
- For Panorama in Management Only mode.
- Configure a Managed Collector to add a Dedicated Log Collector to the Panorama virtual appliance.Management Only mode does not support local log collection, and requires a Dedicated Log Collector to store managed device logs.