|
4592 | 4592 | },
|
4593 | 4593 | "Tags":{
|
4594 | 4594 | "shape":"TagList",
|
4595 |
| - "documentation":"<p>Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag an association to identify the type of resource to which it applies, the environment, or the purpose of the association.</p>", |
| 4595 | + "documentation":"<p>Adds or overwrites one or more tags for a State Manager association. <i>Tags</i> are metadata that you can assign to your Amazon Web Services resources. Tags enable you to categorize your resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value, both of which you define. </p>", |
4596 | 4596 | "box":true
|
4597 | 4597 | },
|
4598 | 4598 | "AlarmConfiguration":{"shape":"AlarmConfiguration"}
|
|
6876 | 6876 | "members":{
|
6877 | 6877 | "Message":{"shape":"String"}
|
6878 | 6878 | },
|
6879 |
| - "documentation":"<p>The document can't be shared with more Amazon Web Services user accounts. You can share a document with a maximum of 20 accounts. You can publicly share up to five documents. If you need to increase this limit, contact Amazon Web Services Support.</p>", |
| 6879 | + "documentation":"<p>The document can't be shared with more Amazon Web Services user accounts. You can specify a maximum of 20 accounts per API operation to share a private document.</p> <p>By default, you can share a private document with a maximum of 1,000 accounts and publicly share up to five documents.</p> <p>If you need to increase the quota for privately or publicly shared Systems Manager documents, contact Amazon Web Services Support.</p>", |
6880 | 6880 | "exception":true
|
6881 | 6881 | },
|
6882 | 6882 | "DocumentPermissionMaxResults":{
|
|
8707 | 8707 | "members":{
|
8708 | 8708 | "Key":{
|
8709 | 8709 | "shape":"InstanceInformationStringFilterKey",
|
8710 |
| - "documentation":"<p>The filter key name to describe your managed nodes. For example:</p> <p>\"InstanceIds\" | \"AgentVersion\" | \"PingStatus\" | \"PlatformTypes\" | \"ActivationIds\" | \"IamRole\" | \"ResourceType\" | \"AssociationStatus\" | \"tag-key\" | \"tag:<code>{keyname}</code> </p> <important> <p> <code>Tag Key</code> isn't a valid filter. You must specify either <code>tag-key</code> or <code>tag:{keyname}</code> and a string. Here are some valid examples: <code>tag-key</code>, <code>tag:123</code>, <code>tag:al!</code>, <code>tag:Windows</code>. Here are some <i>invalid</i> examples: <code>tag-keys</code>, <code>Tag Key</code>, <code>tag:</code>, <code>tagKey</code>, <code>abc:keyname</code>.</p> </important>" |
| 8710 | + "documentation":"<p>The filter key name to describe your managed nodes.</p> <p>Valid filter key values: ActivationIds | AgentVersion | AssociationStatus | IamRole | InstanceIds | PingStatus | PlatformTypes | ResourceType | SourceIds | SourceTypes | \"tag-key\" | \"tag:<code>{keyname}</code> </p> <ul> <li> <p>Valid values for the <code>AssociationStatus</code> filter key: Success | Pending | Failed</p> </li> <li> <p>Valid values for the <code>PingStatus</code> filter key: Online | ConnectionLost | Inactive (deprecated)</p> </li> <li> <p>Valid values for the <code>PlatformType</code> filter key: Windows | Linux | MacOS</p> </li> <li> <p>Valid values for the <code>ResourceType</code> filter key: EC2Instance | ManagedInstance</p> </li> <li> <p>Valid values for the <code>SourceType</code> filter key: AWS::EC2::Instance | AWS::SSM::ManagedInstance | AWS::IoT::Thing</p> </li> <li> <p>Valid tag examples: <code>Key=tag-key,Values=Purpose</code> | <code>Key=tag:Purpose,Values=Test</code>.</p> </li> </ul>" |
8711 | 8711 | },
|
8712 | 8712 | "Values":{
|
8713 | 8713 | "shape":"InstanceInformationFilterValueSet",
|
|
8817 | 8817 | },
|
8818 | 8818 | "CriticalNonCompliantCount":{
|
8819 | 8819 | "shape":"PatchCriticalNonCompliantCount",
|
8820 |
| - "documentation":"<p>The number of managed nodes where patches that are specified as <code>Critical</code> for compliance reporting in the patch baseline aren't installed. These patches might be missing, have failed installation, were rejected, or were installed but awaiting a required managed node reboot. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
| 8820 | + "documentation":"<p>The number of patches per node that are specified as <code>Critical</code> for compliance reporting in the patch baseline aren't installed. These patches might be missing, have failed installation, were rejected, or were installed but awaiting a required managed node reboot. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
8821 | 8821 | "box":true
|
8822 | 8822 | },
|
8823 | 8823 | "SecurityNonCompliantCount":{
|
8824 | 8824 | "shape":"PatchSecurityNonCompliantCount",
|
8825 |
| - "documentation":"<p>The number of managed nodes where patches that are specified as <code>Security</code> in a patch advisory aren't installed. These patches might be missing, have failed installation, were rejected, or were installed but awaiting a required managed node reboot. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
| 8825 | + "documentation":"<p>The number of patches per node that are specified as <code>Security</code> in a patch advisory aren't installed. These patches might be missing, have failed installation, were rejected, or were installed but awaiting a required managed node reboot. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
8826 | 8826 | "box":true
|
8827 | 8827 | },
|
8828 | 8828 | "OtherNonCompliantCount":{
|
8829 | 8829 | "shape":"PatchOtherNonCompliantCount",
|
8830 |
| - "documentation":"<p>The number of managed nodes with patches installed that are specified as other than <code>Critical</code> or <code>Security</code> but aren't compliant with the patch baseline. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
| 8830 | + "documentation":"<p>The number of patches per node that are specified as other than <code>Critical</code> or <code>Security</code> but aren't compliant with the patch baseline. The status of these managed nodes is <code>NON_COMPLIANT</code>.</p>", |
8831 | 8831 | "box":true
|
8832 | 8832 | }
|
8833 | 8833 | },
|
|
9271 | 9271 | "members":{
|
9272 | 9272 | "Message":{"shape":"String"}
|
9273 | 9273 | },
|
9274 |
| - "documentation":"<p>The tag key or value isn't valid.</p>", |
| 9274 | + "documentation":"<p>The specified tag key or value isn't valid.</p>", |
9275 | 9275 | "exception":true
|
9276 | 9276 | },
|
9277 | 9277 | "InvalidTarget":{
|
|
10386 | 10386 | "members":{
|
10387 | 10387 | "S3BucketName":{
|
10388 | 10388 | "shape":"S3BucketName",
|
10389 |
| - "documentation":"<p>The name of an S3 bucket where execution logs are stored .</p>" |
| 10389 | + "documentation":"<p>The name of an S3 bucket where execution logs are stored.</p>" |
10390 | 10390 | },
|
10391 | 10391 | "S3KeyPrefix":{
|
10392 | 10392 | "shape":"S3KeyPrefix",
|
|
11262 | 11262 | "WINDOWS",
|
11263 | 11263 | "AMAZON_LINUX",
|
11264 | 11264 | "AMAZON_LINUX_2",
|
| 11265 | + "AMAZON_LINUX_2022", |
11265 | 11266 | "UBUNTU",
|
11266 | 11267 | "REDHAT_ENTERPRISE_LINUX",
|
11267 | 11268 | "SUSE",
|
|
0 commit comments