KB44670 - Pulse Secure Client upgrade from PCS/PPS irrespective of the end user's OS/platform
KB41030 - Frequently Asked Questions (FAQ) about PSA-V (Virtual Appliance) in 8.3R3/5.4R3 and higher version of PCS/PPS software
KB44747 - Features getting deprecated in PCS/PPS after 9.1R13 Release
KB44617 - Pulse Desktop Client On MacOS Takes A Delayed Time To Load
KB44874 - Virtual appliances (On-prem/cloud) fail to reboot after upgrade to PCS/PPS version 9.1R11.4/R11.5/R12 or later
KB43617 - [VA-SPE] Upgrading the VMware Hardware Version for a PCS/PPS Virtual Appliance
KB24619 - How to restrict user login to a specific time period on a PCS/PPS device
KB44448 - How do I install or generate a licenses for PSA-V (virtual appliances) and other cloud-based instances (AWS and Azure)?
KB44646 - Implications of Enabling Host Header Validation in PCS/PPS 9.1R10
KB40067 - PCS/PPS automatic subscription license checks and renewal
What would you like to know?
< Back to search results
KB44638 - AWS upgrades of PCS/PPS takes a very long time compared to Azure/KVM/VMWare/Hyper-V platforms
Last Modified Date
2/3/2022 9:14 PM
AWS upgrades of PCS/PPS takes a very long time compared to Azure/KVM/VMWare/Hyper-V platforms
This article describes the delay observed in AWS Upgrades of PCS/PPS appliances.
Problem or Goal
AWS Upgrades of PCS/PPS Virtual Appliances take a considerable amount of time to upgrade when compared to other platforms such as Azure/KVM/VMWare/Hyper-V.
This is seen due to the Disk I/O operations.
Upgrades from base Deployments that use GP3 EBS Volumes take considerably less amount of time.
Therefore, please deploy base images using GP3 EBS Volumes via AMI templates or deploy Base PCS 9.1R13 or later images from marketplace as we have incorporated GP3 EBS volumes.
Freshly Deploy an AWS Image of the target version.
Export Binary System/User configurations from the current appliance.
Import the exported Binary System/User Configurations on to the Freshly Deployed AWS instance.
Perform some basic/functionality testing.
Shutdown the existing/old PSA-V instance and make a note of the Auth code previously used.
Use the Auth code to generate new licenses and apply them.
Assign the Elastic (Public IP Address) to the new instance.
Decommission the old instance once the new appliance is fully functional.
If the target PCS image is not available, you would need to perform an upgrade the usual way.
AWS Marketplace is not qualified for the China Region.
Was this article helpful?
Please tell us how we can make this article more useful.