Package-level declarations
Types
The severity level that is assigned to the association.
The mode for generating association compliance. You can specify AUTO or MANUAL . In AUTO mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association is COMPLIANT . If the association execution doesn't run successfully, the association is NON-COMPLIANT . In MANUAL mode, you must specify the AssociationId as a parameter for the PutComplianceItems API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to the PutComplianceItems API action. By default, all associations use AUTO mode.
The key of a key-value pair that identifies the location of an attachment to a document.
Specify the document format for the request. The document format can be either JSON or YAML. JSON is the default format.
The type of document to create.
Update method - when set to 'Replace', the update will replace the existing document; when set to 'NewVersion', the update will create a new version.
The data type of the parameter, such as `text` or `aws:ec2:image`. The default is `text`.
The parameter tier.
The type of parameter.
Defines the compliance level for approved patches. This means that if an approved patch is reported as missing, this is the severity of the compliance violation. The default value is UNSPECIFIED.
Defines the operating system the patch baseline applies to. The Default value is WINDOWS.
The key for the filter. For information about valid keys, see PatchFilter in the AWS Systems Manager API Reference .
The action for Patch Manager to take on patches included in the RejectedPackages list.
A compliance severity level for all approved patches in a patch baseline. Valid compliance severity levels include the following: UNSPECIFIED , CRITICAL , HIGH , MEDIUM , LOW , and INFORMATIONAL .