Update models for release

.changes/3.110.3

@@ -0,0 +1,17 @@
+[
+    {
+        "type": "bugfix",
+        "category": "",
+        "description": "Fixes EventParsingIterator example"
+    },
+    {
+        "type": "api-change",
+        "category": "SecurityHub",
+        "description": "This release resolves an issue with the DescribeHub action, changes the MasterId and InvitationId parameters for AcceptInvitation to Required, and changes the AccountIds parameter for DeleteInvitations and DeclineInvitations to Required."
+    },
+    {
+        "type": "api-change",
+        "category": "SSM",
+        "description": "This feature adds \"default tier\" to the AWS Systems Manager Parameter Store for parameter creation and update. AWS customers can now set the \"default tier\" to one of the following values: Standard (default), Advanced or Intelligent-Tiering. This allows customers to create advanced parameters or parameters in corresponding tiers with one setting rather than code change to specify parameter tiers."
+    }
+]

CHANGELOG.md

@@ -1,5 +1,11 @@
 # CHANGELOG
 
+## next release
+
+* `Aws\` - Fixes EventParsingIterator example
+* `Aws\SSM` - This feature adds "default tier" to the AWS Systems Manager Parameter Store for parameter creation and update. AWS customers can now set the "default tier" to one of the following values: Standard (default), Advanced or Intelligent-Tiering. This allows customers to create advanced parameters or parameters in corresponding tiers with one setting rather than code change to specify parameter tiers.
+* `Aws\SecurityHub` - This release resolves an issue with the DescribeHub action, changes the MasterId and InvitationId parameters for AcceptInvitation to Required, and changes the AccountIds parameter for DeleteInvitations and DeclineInvitations to Required.
+
 ## 3.110.2 - 2019-08-23
 
 * `Aws\EC2` - This release of EC2 VM Import Export adds support for exporting Amazon Machine Image(AMI)s to a VM file

src/data/securityhub/2018-10-26/api-2.json

@@ -603,6 +603,10 @@
   "shapes":{
     "AcceptInvitationRequest":{
       "type":"structure",
+      "required":[
+        "MasterId",
+        "InvitationId"
+      ],
       "members":{
         "MasterId":{"shape":"NonEmptyString"},
         "InvitationId":{"shape":"NonEmptyString"}
@@ -987,6 +991,7 @@
     },
     "DeclineInvitationsRequest":{
       "type":"structure",
+      "required":["AccountIds"],
       "members":{
         "AccountIds":{"shape":"AccountIdList"}
       }
@@ -1035,6 +1040,7 @@
     },
     "DeleteInvitationsRequest":{
       "type":"structure",
+      "required":["AccountIds"],
       "members":{
         "AccountIds":{"shape":"AccountIdList"}
       }
@@ -1076,7 +1082,11 @@
     "DescribeHubRequest":{
       "type":"structure",
       "members":{
-        "HubArn":{"shape":"NonEmptyString"}
+        "HubArn":{
+          "shape":"NonEmptyString",
+          "location":"querystring",
+          "locationName":"HubArn"
+        }
       }
     },
     "DescribeHubResponse":{

src/data/ssm/2014-11-06/api-2.json

@@ -7015,7 +7015,8 @@
       "type":"string",
       "enum":[
         "Standard",
-        "Advanced"
+        "Advanced",
+        "Intelligent-Tiering"
       ]
     },
     "ParameterType":{
@@ -7396,7 +7397,7 @@
     },
     "PatchSourceConfiguration":{
       "type":"string",
-      "max":512,
+      "max":1024,
       "min":1,
       "sensitive":true
     },

src/data/ssm/2014-11-06/docs-2.json

@@ -2189,7 +2189,7 @@
         "SendCommandRequest$DocumentVersion": "<p>The SSM document version to use in the request. You can specify $DEFAULT, $LATEST, or a specific version number. If you run commands by using the AWS CLI, then you must escape the first two options by using a backslash. If you specify a version number, then you don't need to use the backslash. For example:</p> <p>--document-version \"\\$DEFAULT\"</p> <p>--document-version \"\\$LATEST\"</p> <p>--document-version \"3\"</p>",
         "StartAutomationExecutionRequest$DocumentVersion": "<p>The version of the Automation document to use for this execution.</p>",
         "UpdateAssociationRequest$DocumentVersion": "<p>The document version you want update for the association. </p>",
-        "UpdateDocumentRequest$DocumentVersion": "<p>The version of the document that you want to update.</p>"
+        "UpdateDocumentRequest$DocumentVersion": "<p>(Required) The version of the document that you want to update. </p>"
       }
     },
     "DocumentVersionInfo": {
@@ -2681,7 +2681,7 @@
         "AssociationDescription$InstanceId": "<p>The ID of the instance.</p>",
         "CommandInvocation$InstanceId": "<p>The instance ID in which this invocation was requested.</p>",
         "CreateAssociationBatchRequestEntry$InstanceId": "<p>The ID of the instance. </p>",
-        "CreateAssociationRequest$InstanceId": "<p>The instance ID.</p>",
+        "CreateAssociationRequest$InstanceId": "<p>The instance ID.</p> <note> <p> <code>InstanceId</code> has been deprecated. To specify an instance ID for an association, use the <code>Targets</code> parameter. If you use the parameter <code>InstanceId</code>, you cannot use the parameters <code>AssociationName</code>, <code>DocumentVersion</code>, <code>MaxErrors</code>, <code>MaxConcurrency</code>, <code>OutputLocation</code>, or <code>ScheduleExpression</code>. To use these parameters, you must use the <code>Targets</code> parameter.</p> </note>",
         "DeleteAssociationRequest$InstanceId": "<p>The ID of the instance.</p>",
         "DescribeAssociationRequest$InstanceId": "<p>The instance ID.</p>",
         "DescribeEffectiveInstanceAssociationsRequest$InstanceId": "<p>The instance ID for which you want to view all associations.</p>",
@@ -4961,7 +4961,7 @@
       "refs": {
         "ParameterHistory$Tier": "<p>The parameter tier.</p>",
         "ParameterMetadata$Tier": "<p>The parameter tier.</p>",
-        "PutParameterRequest$Tier": "<p>Parameter Store offers a standard tier and an advanced tier for parameters. Standard parameters have a value limit of 4 KB and can't be configured to use parameter policies. You can create a maximum of 10,000 standard parameters per account and per Region. Standard parameters are offered at no additional cost.</p> <p>Advanced parameters have a value limit of 8 KB and can be configured to use parameter policies. You can create a maximum of 100,000 advanced parameters per account and per Region. Advanced parameters incur a charge.</p> <p>If you don't specify a parameter tier when you create a new parameter, the parameter defaults to using the standard tier. You can change a standard parameter to an advanced parameter at any time. But you can't revert an advanced parameter to a standard parameter. Reverting an advanced parameter to a standard parameter would result in data loss because the system would truncate the size of the parameter from 8 KB to 4 KB. Reverting would also remove any policies attached to the parameter. Lastly, advanced parameters use a different form of encryption than standard parameters.</p> <p>If you no longer need an advanced parameter, or if you no longer want to incur charges for an advanced parameter, you must delete it and recreate it as a new standard parameter. For more information, see <a href=\"http://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-advanced-parameters.html\">About Advanced Parameters</a> in the <i>AWS Systems Manager User Guide</i>.</p>"
+        "PutParameterRequest$Tier": "<p>The parameter tier to assign to a parameter.</p> <p>Parameter Store offers a standard tier and an advanced tier for parameters. Standard parameters have a content size limit of 4 KB and can't be configured to use parameter policies. You can create a maximum of 10,000 standard parameters for each Region in an AWS account. Standard parameters are offered at no additional cost. </p> <p>Advanced parameters have a content size limit of 8 KB and can be configured to use parameter policies. You can create a maximum of 100,000 advanced parameters for each Region in an AWS account. Advanced parameters incur a charge. For more information, see <a href=\"http://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-advanced-parameters.html\">About Advanced Parameters</a> in the <i>AWS Systems Manager User Guide</i>.</p> <p>You can change a standard parameter to an advanced parameter any time. But you can't revert an advanced parameter to a standard parameter. Reverting an advanced parameter to a standard parameter would result in data loss because the system would truncate the size of the parameter from 8 KB to 4 KB. Reverting would also remove any policies attached to the parameter. Lastly, advanced parameters use a different form of encryption than standard parameters. </p> <p>If you no longer need an advanced parameter, or if you no longer want to incur charges for an advanced parameter, you must delete it and recreate it as a new standard parameter. </p> <p> <b>Using the Default Tier Configuration</b> </p> <p>In <code>PutParameter</code> requests, you can specify the tier to create the parameter in. Whenever you specify a tier in the request, Parameter Store creates or updates the parameter according to that request. However, if you do not specify a tier in a request, Parameter Store assigns the tier based on the current Parameter Store default tier configuration.</p> <p>The default tier when you begin using Parameter Store is the standard-parameter tier. If you use the advanced-parameter tier, you can specify one of the following as the default:</p> <ul> <li> <p> <b>Advanced</b>: With this option, Parameter Store evaluates all requests as advanced parameters. </p> </li> <li> <p> <b>Intelligent-Tiering</b>: With this option, Parameter Store evaluates each request to determine if the parameter is standard or advanced. </p> <p>If the request doesn't include any options that require an advanced parameter, the parameter is created in the standard-parameter tier. If one or more options requiring an advanced parameter are included in the request, Parameter Store create a parameter in the advanced-parameter tier.</p> <p>This approach helps control your parameter-related costs by always creating standard parameters unless an advanced parameter is necessary. </p> </li> </ul> <p>Options that require an advanced parameter include the following:</p> <ul> <li> <p>The content size of the parameter is more than 4 KB.</p> </li> <li> <p>The parameter uses a parameter policy.</p> </li> <li> <p>More than 10,000 parameters already exist in your AWS account in the current Region.</p> </li> </ul> <p>For more information about configuring the default tier option, see <a href=\"http://docs.aws.amazon.com/systems-manager/latest/userguide/ps-default-tier.html\">Specifying a Default Parameter Tier</a> in the AWS Systems Manager User Guide.</p>"
       }
     },
     "ParameterType": {
@@ -5322,7 +5322,7 @@
       "base": null,
       "refs": {
         "DescribeAvailablePatchesRequest$Filters": "<p>Filters used to scope down the returned patches.</p>",
-        "DescribeInstancePatchesRequest$Filters": "<p>Each entry in the array is a structure containing:</p> <p>Key (string, between 1 and 128 characters)</p> <p>Values (array of strings, each string between 1 and 256 characters)</p>",
+        "DescribeInstancePatchesRequest$Filters": "<p>An array of structures. Each entry in the array is a structure containing a Key, Value combination. Valid values for Key are <code>Classification</code> | <code>KBId</code> | <code>Severity</code> | <code>State</code>.</p>",
         "DescribeMaintenanceWindowScheduleRequest$Filters": "<p>Filters used to limit the range of results. For example, you can limit maintenance window executions to only those scheduled before or after a certain date and time.</p>",
         "DescribePatchBaselinesRequest$Filters": "<p>Each element in the array is a structure containing: </p> <p>Key: (string, \"NAME_PREFIX\" or \"OWNER\")</p> <p>Value: (array of strings, exactly 1 entry, between 1 and 255 characters)</p>",
         "DescribePatchGroupsRequest$Filters": "<p>One or more filters. Use a filter to return a more specific list of results.</p>"
@@ -6573,7 +6573,7 @@
         "AutomationExecutionMetadata$Targets": "<p>The targets defined by the user when starting the Automation.</p>",
         "Command$Targets": "<p>An array of search criteria that targets instances using a Key,Value combination that you specify. Targets is required if you don't provide one or more instance IDs in the call.</p>",
         "CreateAssociationBatchRequestEntry$Targets": "<p>The instances targeted by the request.</p>",
-        "CreateAssociationRequest$Targets": "<p>The targets (either instances or tags) for the association.</p>",
+        "CreateAssociationRequest$Targets": "<p>The targets (either instances or tags) for the association. You must specify a value for <code>Targets</code> if you don't specify a value for <code>InstanceId</code>.</p>",
         "DescribeMaintenanceWindowScheduleRequest$Targets": "<p>The instance ID or key/value pair to retrieve information about.</p>",
         "DescribeMaintenanceWindowsForTargetRequest$Targets": "<p>The instance ID or key/value pair to retrieve information about.</p>",
         "GetMaintenanceWindowTaskResult$Targets": "<p>The targets where the task should run.</p>",