SA44101 - 2019-04: Out-of-Cycle Advisory: Multiple vulnerabilities resolved in Pulse Connect Secure / Pulse Policy Secure 9.0RX
KB43992 - Unable to upgrade Virtual Appliance (PSA-V) to 9.0Rx and above
KB41030 - Frequently Asked Questions (FAQ) about PSA-V (Virtual Appliance) in 8.3R3/5.4R3 and higher version of PCS/PPS software
KB40996 - How to troubleshoot ESAP related Predefined Antivirus Host Checker policy issues
KB44670 - Pulse Secure Client upgrade from PCS/PPS irrespective of the end user's OS/platform
KB44448 - How do I install or generate a licenses for PSA-V (virtual appliances) and other cloud-based instances (AWS and Azure)?
5751 - Need to restrict the managment of the appliance to a single IP address.
TSB16159 - Hardware End of Life Announcement – SA2500, SA4500, SA6500, IC4500, IC6500 (excluding FIPS platforms)
KB44558 - Network Time Protocol (NTP) issues after upgrading Pulse Connect Secure / Pulse Policy Secure to 9.1R8 Virtual Machines
KB44457 - Frequent VIP flap is observed on Virtual Machines running on VMWare/ESXi in A/P cluster.
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
11/24/2020 6:55 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.
Pulse Engineering is aware of the issue & working on a Long Term Solution. We will keep this article updated as and when we make progress.
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.