Cloudaware offers a low-friction, high-value continuous patching. Cloudaware’s approach is to ensure a customer’s compute instances are patched in a timely manner without causing harm and interference to production applications.
Clouduaware patch management process supports capabilities such as automatically generated release notes, full and partial rollback, and deployment of emergency patches for critical security vulnerabilities.
Transparency
Consistency
Rollback
Rollback script is located on every patched instance in the following location: /opt/breeze-agent/os_updater/YYYYMMDDhhmmss.sh
In the event rollback is requested, Cloudaware Breeze agent will set repo to the previous GUID, execute the rollback script and verify rollback using yum update against preview repo GUID. After the script execution is complete, the yum update should not introduce any changes to the packages on the host.
Emergency Security Release
If a critical security vulnerability is identified, Cloudaware will create an emergency release. The emergency release will contain security patches and potentially other updates that have accumulated since the last release.
Patch Information in CMDB
Cloudaware provides patch monitoring and patch eligibility information in CMDB. Along with OS level data, the information on patches becomes available in Cloudaware CMDB once Breeze agent is installed on a machine.
Cloudaware shows what patches are outstanding, equally well for Windows and Linux. If a patch is security-related, meaning that there is a security vulnerability that has been identified with that version of the package, the checkbox 'Security' is going to be checked requiring your attention.
Once a package is applied, the column 'Installed Date' is populated. The column 'Package Age' gives the idea of how well your security team is doing with patching.