Focus

Prisma SD-WAN CloudBlades Release Notes

AWS Transit Gateway CloudBlade Version 2.1.0

Table of Contents

updates and upgrade considerations of the AWS Transit Gateway CloudBlade

This topic contains important updates and upgrade considerations of the AWS Transit Gateway CloudBlade Version 2.1.0.

From version 2.1.0 of the AWS Transit Gateway CloudBlade, the marketplace subscription listing has migrated to Palo Alto Networks marketplace from CloudGenix. There is no other change in features or functionality compared to the 2.0.0 version of the CloudBlade.

The new marketplace subscription is mandatory for the 2.1.0 version of the CloudBlade, else the CloudBlade will fail.

To upgrade the AWS Transit Gateway CloudBlade version from version 2.0.0 to version 2.1.0.

Go to Strata Cloud ManagerManagePrisma SD-WANCloudBlades.
Locate the AWS Transit Gateway CloudBlade and click Configure.
Ensure that the Admin State of the CloudBlade remains unchanged, during and after the upgrade process.
Select the version you want to upgrade to from the Version drop-down.
Re-enter the ACCESS KEY ID SECRET in the designated field during the upgrade. Retrieve this information from the AWS portal customer account.
Click Save.
To verify the successful upgrade of the CloudBlade, go to the Prisma SD-WAN CloudBlades web interface and check the Installed Version number in the AWS Transit Gateway CloudBlade tile.

In an upgrade scenario from version 2.0.0 to version 2.1.0 of the AWS Transit Gateway CloudBlade, existing deployments will not be impacted; however, any new deployments require subscribing to the new marketplace.
The upgrade process should not impact the existing vION setup. It's expected to be non-disruptive.
No configuration change is expected on the vION which is already deployed.
Cloud Blades upgrade has no dependency on the vION upgrade and both can be done independently of each other. However, it is recommended not to do both upgrades together.
New vION deployments after the CloudBlade upgrade will use the m5.large instance type instead of m4.large instance type.
The upgraded CloudBlade version will support region-based CIDR deployments.