Modify Autoscaling on an Existing Non-Mesh Firewall Deployment
Focus
Focus
Prisma AIRS

Modify Autoscaling on an Existing Non-Mesh Firewall Deployment

Table of Contents

Modify Autoscaling on an Existing Non-Mesh Firewall Deployment

Update autoscaling parameters — including instance bounds, metric thresholds, and Update Interval — on an existing Auto-Deploy non-mesh Prisma AIRS firewall on AWS, Azure, or GCP.
Where Can I Use This?What Do I Need?
  • Prisma AIRS
  • AWS
  • Azure
  • GCP
  • An existing non-mesh AIRS firewall deployed with dynamic autoscaling enabled
  • Access to Strata Cloud Manager
Use this procedure to update autoscaling parameters on an already-deployed Auto-Deploy non-mesh AIRS firewall. You can adjust Min/Max instance bounds, change the metric Update Interval, add new scaling metrics, edit thresholds on existing metrics, and remove metrics. The scaling mode (Static or Dynamic) cannot be changed after initial deployment.
  • If you have disconnected firewalls in your deployment folder in the Strata Cloud Manager Device Management page, you will see a failure at the folder push step. Ensure all firewalls in the folder are connected before proceeding.
  • If firewalls are connected to Strata Cloud Manager but have not yet completed bootstrapping, wait for bootstrapping to complete before triggering a brownfield update. Starting the update before bootstrapping completes will cause the folder push to fail.
  1. In Strata Cloud Manager, go to InsightsDiscover & Assess.
  2. On the Select Firewall Placement page, select the Existing option and choose your auto-deployed firewall from the list.
  3. Select Auto-Execute Workflow.
  4. In the autoscaling section, make your changes: adjust Min/Max bounds, change the Update Interval, or add, edit, or remove scaling metrics.
  5. Proceed to the review page and verify the updated payload reflects all your changes.
  6. Click Save & Auto-Execute.
An Update Firewall Configuration task is triggered. Monitor progress in Cloud Task Logs.