AWS Documentation » AWS Systems Manager » User Guide » AWS Systems Manager Instances & Nodes » AWS Systems Manager Patch Manager » How Patch Manager Operations Work » Key Differences Between Linux and Windows Patching

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Key Differences Between Linux and Windows Patching

The following table describes important differences between Linux and Windows patching.

Note

To patch Linux instances, your instances must be running SSM Agent version 2.0.834.0 or later.

An updated version of SSM Agent is released whenever new capabilities are added to Systems Manager or updates are made to existing capabilities. If an older version of the agent is running on an instance, some SSM Agent processes can fail. For that reason, we recommend that you automate the process of keeping SSM Agent up-to-date on your instances. For information, see Automate Updates to SSM Agent. To be notified about SSM Agent updates, subscribe to the SSM Agent Release Notes page on GitHub.

Difference	Details
Patch evaluation	Linux For Linux patching, Systems Manager evaluates patch baseline rules and the list of approved and rejected patches on each managed instance. Systems Manager must evaluate patching on each instance because the service retrieves the list of known patches and updates from the repositories that are configured on the instance. Windows Patch Manager uses different processes on Windows managed instances and Linux managed instances in order to evaluate which patches should be present. For Windows patching, Systems Manager evaluates patch baseline rules and the list of approved and rejected patches directly in the service. It can do this because Windows patches are pulled from a single repository (Windows Update).
Not Applicable patches	Due to the large number of available packages for Linux operating systems, Systems Manager does not report details about patches in the Not Applicable state. A Not Not Applicable patch is, for example, a patch for Apache software when the instance does not have Apache installed. Systems Manager does report the number of Not Applicable patches in the summary, but if you call the DescribeInstancePatches API for an instance, the returned data does not include patches with a state of Not Applicable. This behavior is different from Windows.
SSM document support	The AWS-ApplyPatchBaseline SSM document doesn't support Linux instances. For applying patch baselines to both Windows and Linux instances, the recommended SSM document is AWS-RunPatchBaseline. For more information, see About SSM Documents for Patching Instances and About the SSM Document AWS-RunPatchBaseline.
Application patches	Patch Manager's primary focus is applying patches to operating systems. However, you can also use Patch Manager to apply patches to some applications on your instances. Linux On Linux operating systems, Patch Manager uses the configured repositories for updates, and does not differentiate between operating systems and application patches. You can use Patch Manager to define which repositories to fetch updates from. For more information, see How to Specify an Alternative Patch Source Repository (Linux). Windows On Windows Server instances, you can apply approval rules, as well as Approved and Rejected patch exceptions, for applications released by Microsoft, such as Microsoft Word 2011 and Microsoft Exchange Server 2016. For more information, see Create a Custom Patch Baseline.