|
165 | 165 | "base": null, |
166 | 166 | "refs": { |
167 | 167 | "DescribeDocumentPermissionResponse$AccountIds": "<p>The account IDs that have permission to use this document. The ID can be either an Amazon Web Services account or <i>All</i>.</p>", |
168 | | - "ModifyDocumentPermissionRequest$AccountIdsToAdd": "<p>The Amazon Web Services users that should have access to the document. The account IDs can either be a group of account IDs or <i>All</i>. </p>", |
169 | | - "ModifyDocumentPermissionRequest$AccountIdsToRemove": "<p>The Amazon Web Services users that should no longer have access to the document. The Amazon Web Services user can either be a group of account IDs or <i>All</i>. This action has a higher priority than <code>AccountIdsToAdd</code>. If you specify an ID to add and the same ID to remove, the system removes access to the document. </p>" |
| 168 | + "ModifyDocumentPermissionRequest$AccountIdsToAdd": "<p>The Amazon Web Services users that should have access to the document. The account IDs can either be a group of account IDs or <i>All</i>. You must specify a value for this parameter or the <code>AccountIdsToRemove</code> parameter.</p>", |
| 169 | + "ModifyDocumentPermissionRequest$AccountIdsToRemove": "<p>The Amazon Web Services users that should no longer have access to the document. The Amazon Web Services user can either be a group of account IDs or <i>All</i>. This action has a higher priority than <code>AccountIdsToAdd</code>. If you specify an ID to add and the same ID to remove, the system removes access to the document. You must specify a value for this parameter or the <code>AccountIdsToAdd</code> parameter.</p>" |
170 | 170 | } |
171 | 171 | }, |
172 | 172 | "AccountSharingInfo": { |
|
3576 | 3576 | "DescribePatchGroupStateResult$InstancesWithFailedPatches": "<p>The number of managed nodes with patches from the patch baseline that failed to install.</p>", |
3577 | 3577 | "DescribePatchGroupStateResult$InstancesWithNotApplicablePatches": "<p>The number of managed nodes with patches that aren't applicable.</p>", |
3578 | 3578 | "DescribePatchGroupStateResult$InstancesWithUnreportedNotApplicablePatches": "<p>The number of managed nodes with <code>NotApplicable</code> patches beyond the supported limit, which aren't reported by name to Inventory. Inventory is a tool in Amazon Web Services Systems Manager.</p>", |
| 3579 | + "DescribePatchGroupStateResult$InstancesWithAvailableSecurityUpdates": "<p>The number of managed nodes for which security-related patches are available but not approved because because they didn't meet the patch baseline requirements. For example, an updated version of a patch might have been released before the specified auto-approval period was over.</p> <p>Applies to Windows Server managed nodes only.</p>", |
3579 | 3580 | "OpsItemLimitExceededException$Limit": null, |
3580 | 3581 | "ParentStepDetails$Iteration": "<p>The current repetition of the loop represented by an integer.</p>", |
3581 | 3582 | "ProgressCounters$TotalSteps": "<p>The total number of steps run in all specified Amazon Web Services Regions and Amazon Web Services accounts for the current Automation execution.</p>", |
|
6138 | 6139 | "ParameterHistory$Name": "<p>The name of the parameter.</p>", |
6139 | 6140 | "ParameterMetadata$Name": "<p>The parameter name.</p>", |
6140 | 6141 | "ParameterNameList$member": null, |
6141 | | - "PutParameterRequest$Name": "<p>The fully qualified name of the parameter that you want to create or update.</p> <note> <p>You can't enter the Amazon Resource Name (ARN) for a parameter, only the parameter name itself.</p> </note> <p>The fully qualified name includes the complete hierarchy of the parameter path and name. For parameters in a hierarchy, you must include a leading forward slash character (/) when you create or reference a parameter. For example: <code>/Dev/DBServer/MySQL/db-string13</code> </p> <p>Naming Constraints:</p> <ul> <li> <p>Parameter names are case sensitive.</p> </li> <li> <p>A parameter name must be unique within an Amazon Web Services Region</p> </li> <li> <p>A parameter name can't be prefixed with \"<code>aws</code>\" or \"<code>ssm</code>\" (case-insensitive).</p> </li> <li> <p>Parameter names can include only the following symbols and letters: <code>a-zA-Z0-9_.-</code> </p> <p>In addition, the slash character ( / ) is used to delineate hierarchies in parameter names. For example: <code>/Dev/Production/East/Project-ABC/MyParameter</code> </p> </li> <li> <p>A parameter name can't include spaces.</p> </li> <li> <p>Parameter hierarchies are limited to a maximum depth of fifteen levels.</p> </li> </ul> <p>For additional information about valid values for parameter names, see <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-su-create.html\">Creating Systems Manager parameters</a> in the <i>Amazon Web Services Systems Manager User Guide</i>.</p> <note> <p>The maximum length constraint of 2048 characters listed below includes 1037 characters reserved for internal use by Systems Manager. The maximum length for a parameter name that you create is 1011 characters. This includes the characters in the ARN that precede the name you specify, such as <code>arn:aws:ssm:us-east-2:111122223333:parameter/</code>.</p> </note>", |
| 6142 | + "PutParameterRequest$Name": "<p>The fully qualified name of the parameter that you want to create or update.</p> <note> <p>You can't enter the Amazon Resource Name (ARN) for a parameter, only the parameter name itself.</p> </note> <p>The fully qualified name includes the complete hierarchy of the parameter path and name. For parameters in a hierarchy, you must include a leading forward slash character (/) when you create or reference a parameter. For example: <code>/Dev/DBServer/MySQL/db-string13</code> </p> <p>Naming Constraints:</p> <ul> <li> <p>Parameter names are case sensitive.</p> </li> <li> <p>A parameter name must be unique within an Amazon Web Services Region</p> </li> <li> <p>A parameter name can't be prefixed with \"<code>aws</code>\" or \"<code>ssm</code>\" (case-insensitive).</p> </li> <li> <p>Parameter names can include only the following symbols and letters: <code>a-zA-Z0-9_.-</code> </p> <p>In addition, the slash character ( / ) is used to delineate hierarchies in parameter names. For example: <code>/Dev/Production/East/Project-ABC/MyParameter</code> </p> </li> <li> <p>A parameter name can't include spaces.</p> </li> <li> <p>Parameter hierarchies are limited to a maximum depth of fifteen levels.</p> </li> </ul> <p>For additional information about valid values for parameter names, see <a href=\"https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-su-create.html\">Creating Systems Manager parameters</a> in the <i>Amazon Web Services Systems Manager User Guide</i>.</p> <note> <p>The reported maximum length of 2048 characters for a parameter name includes 1037 characters that are reserved for internal use by Systems Manager. The maximum length for a parameter name that you specify is 1011 characters.</p> <p>This count of 1011 characters includes the characters in the ARN that precede the name you specify. This ARN length will vary depending on your partition and Region. For example, the following 45 characters count toward the 1011 character maximum for a parameter created in the US East (Ohio) Region: <code>arn:aws:ssm:us-east-2:111122223333:parameter/</code>.</p> </note>", |
6142 | 6143 | "UnlabelParameterVersionRequest$Name": "<p>The name of the parameter from which you want to delete one or more labels.</p> <note> <p>You can't enter the Amazon Resource Name (ARN) for a parameter, only the parameter name itself.</p> </note>" |
6143 | 6144 | } |
6144 | 6145 | }, |
|
6470 | 6471 | "Patch$Arch": "<p>The architecture of the patch. For example, in <code>example-pkg-0.710.10-2.7.abcd.x86_64</code>, the architecture is indicated by <code>x86_64</code>. Applies to Linux-based managed nodes only.</p>" |
6471 | 6472 | } |
6472 | 6473 | }, |
| 6474 | + "PatchAvailableSecurityUpdateCount": { |
| 6475 | + "base": null, |
| 6476 | + "refs": { |
| 6477 | + "InstancePatchState$AvailableSecurityUpdateCount": "<p>The number of security-related patches that are available but not approved because they didn't meet the patch baseline requirements. For example, an updated version of a patch might have been released before the specified auto-approval period was over.</p> <p>Applies to Windows Server managed nodes only.</p>" |
| 6478 | + } |
| 6479 | + }, |
6473 | 6480 | "PatchBaselineIdentity": { |
6474 | 6481 | "base": "<p>Defines the basic information about a patch baseline.</p>", |
6475 | 6482 | "refs": { |
|
6567 | 6574 | "DescribeInstancePatchesRequest$MaxResults": "<p>The maximum number of patches to return (per page).</p>" |
6568 | 6575 | } |
6569 | 6576 | }, |
| 6577 | + "PatchComplianceStatus": { |
| 6578 | + "base": null, |
| 6579 | + "refs": { |
| 6580 | + "BaselineOverride$AvailableSecurityUpdatesComplianceStatus": "<p>Indicates whether managed nodes for which there are available security-related patches that have not been approved by the baseline are being defined as <code>COMPLIANT</code> or <code>NON_COMPLIANT</code>. This option is specified when the <code>CreatePatchBaseline</code> or <code>UpdatePatchBaseline</code> commands are run.</p> <p>Applies to Windows Server managed nodes only.</p>", |
| 6581 | + "CreatePatchBaselineRequest$AvailableSecurityUpdatesComplianceStatus": "<p>Indicates the status you want to assign to security patches that are available but not approved because they don't meet the installation criteria specified in the patch baseline.</p> <p>Example scenario: Security patches that you might want installed can be skipped if you have specified a long period to wait after a patch is released before installation. If an update to the patch is released during your specified waiting period, the waiting period for installing the patch starts over. If the waiting period is too long, multiple versions of the patch could be released but never installed.</p> <p>Supported for Windows Server managed nodes only.</p>", |
| 6582 | + "GetPatchBaselineResult$AvailableSecurityUpdatesComplianceStatus": "<p>Indicates the compliance status of managed nodes for which security-related patches are available but were not approved. This preference is specified when the <code>CreatePatchBaseline</code> or <code>UpdatePatchBaseline</code> commands are run.</p> <p>Applies to Windows Server managed nodes only.</p>", |
| 6583 | + "UpdatePatchBaselineRequest$AvailableSecurityUpdatesComplianceStatus": "<p>Indicates the status to be assigned to security patches that are available but not approved because they don't meet the installation criteria specified in the patch baseline.</p> <p>Example scenario: Security patches that you might want installed can be skipped if you have specified a long period to wait after a patch is released before installation. If an update to the patch is released during your specified waiting period, the waiting period for installing the patch starts over. If the waiting period is too long, multiple versions of the patch could be released but never installed.</p> <p>Supported for Windows Server managed nodes only.</p>", |
| 6584 | + "UpdatePatchBaselineResult$AvailableSecurityUpdatesComplianceStatus": "<p>Indicates the compliance status of managed nodes for which security-related patches are available but were not approved. This preference is specified when the <code>CreatePatchBaseline</code> or <code>UpdatePatchBaseline</code> commands are run.</p> <p>Applies to Windows Server managed nodes only.</p>" |
| 6585 | + } |
| 6586 | + }, |
6570 | 6587 | "PatchContentUrl": { |
6571 | 6588 | "base": null, |
6572 | 6589 | "refs": { |
|
0 commit comments