Updated API models and rebuilt service gems.

apis/accessanalyzer/2019-11-01/api-2.json

@@ -983,7 +983,9 @@
         "s3Bucket":{"shape":"S3BucketConfiguration"},
         "snsTopic":{"shape":"SnsTopicConfiguration"},
         "sqsQueue":{"shape":"SqsQueueConfiguration"},
-        "s3ExpressDirectoryBucket":{"shape":"S3ExpressDirectoryBucketConfiguration"}
+        "s3ExpressDirectoryBucket":{"shape":"S3ExpressDirectoryBucketConfiguration"},
+        "dynamodbStream":{"shape":"DynamodbStreamConfiguration"},
+        "dynamodbTable":{"shape":"DynamodbTableConfiguration"}
       },
       "union":true
     },
@@ -1129,6 +1131,20 @@
         }
       }
     },
+    "DynamodbStreamConfiguration":{
+      "type":"structure",
+      "members":{
+        "streamPolicy":{"shape":"DynamodbStreamPolicy"}
+      }
+    },
+    "DynamodbStreamPolicy":{"type":"string"},
+    "DynamodbTableConfiguration":{
+      "type":"structure",
+      "members":{
+        "tablePolicy":{"shape":"DynamodbTablePolicy"}
+      }
+    },
+    "DynamodbTablePolicy":{"type":"string"},
     "EbsGroup":{"type":"string"},
     "EbsGroupList":{
       "type":"list",
@@ -2219,7 +2235,9 @@
         "AWS::RDS::DBSnapshot",
         "AWS::RDS::DBClusterSnapshot",
         "AWS::SNS::Topic",
-        "AWS::S3Express::DirectoryBucket"
+        "AWS::S3Express::DirectoryBucket",
+        "AWS::DynamoDB::Table",
+        "AWS::DynamoDB::Stream"
       ]
     },
     "RetiringPrincipal":{"type":"string"},
@@ -2673,7 +2691,8 @@
         "AWS::S3::AccessPoint",
         "AWS::S3::MultiRegionAccessPoint",
         "AWS::S3ObjectLambda::AccessPoint",
-        "AWS::IAM::AssumeRolePolicyDocument"
+        "AWS::IAM::AssumeRolePolicyDocument",
+        "AWS::DynamoDB::Table"
       ]
     },
     "ValidatePolicyResponse":{

apis/accessanalyzer/2019-11-01/docs-2.json

@@ -429,6 +429,30 @@
       "refs": {
       }
     },
+    "DynamodbStreamConfiguration": {
+      "base": "<p>The proposed access control configuration for a DynamoDB stream. You can propose a configuration for a new DynamoDB stream or an existing DynamoDB stream that you own by specifying the policy for the DynamoDB stream. For more information, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html\">PutResourcePolicy</a>.</p> <ul> <li> <p>If the configuration is for an existing DynamoDB stream and you do not specify the DynamoDB policy, then the access preview uses the existing DynamoDB policy for the stream.</p> </li> <li> <p>If the access preview is for a new resource and you do not specify the policy, then the access preview assumes a DynamoDB stream without a policy.</p> </li> <li> <p>To propose deletion of an existing DynamoDB stream policy, you can specify an empty string for the DynamoDB policy.</p> </li> </ul>",
+      "refs": {
+        "Configuration$dynamodbStream": "<p>The access control configuration is for a DynamoDB stream.</p>"
+      }
+    },
+    "DynamodbStreamPolicy": {
+      "base": null,
+      "refs": {
+        "DynamodbStreamConfiguration$streamPolicy": "<p>The proposed resource policy defining who can access or manage the DynamoDB stream.</p>"
+      }
+    },
+    "DynamodbTableConfiguration": {
+      "base": "<p>The proposed access control configuration for a DynamoDB table or index. You can propose a configuration for a new DynamoDB table or index or an existing DynamoDB table or index that you own by specifying the policy for the DynamoDB table or index. For more information, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html\">PutResourcePolicy</a>.</p> <ul> <li> <p>If the configuration is for an existing DynamoDB table or index and you do not specify the DynamoDB policy, then the access preview uses the existing DynamoDB policy for the table or index.</p> </li> <li> <p>If the access preview is for a new resource and you do not specify the policy, then the access preview assumes a DynamoDB table without a policy.</p> </li> <li> <p>To propose deletion of an existing DynamoDB table or index policy, you can specify an empty string for the DynamoDB policy.</p> </li> </ul>",
+      "refs": {
+        "Configuration$dynamodbTable": "<p>The access control configuration is for a DynamoDB table or index.</p>"
+      }
+    },
+    "DynamodbTablePolicy": {
+      "base": null,
+      "refs": {
+        "DynamodbTableConfiguration$tablePolicy": "<p>The proposed resource policy defining who can access or manage the DynamoDB table.</p>"
+      }
+    },
     "EbsGroup": {
       "base": null,
       "refs": {

apis/codebuild/2016-10-06/docs-2.json

@@ -2035,7 +2035,7 @@
     "WebhookFilterType": {
       "base": null,
       "refs": {
-        "WebhookFilter$type": "<p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR_ACCOUNT_ID</code>, <code>HEAD_REF</code>, <code>BASE_REF</code>, <code>FILE_PATH</code>, and <code>COMMIT_MESSAGE</code>. </p> <ul> <li> <p> EVENT </p> <ul> <li> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of six event types: <code>PUSH</code>, <code>PULL_REQUEST_CREATED</code>, <code>PULL_REQUEST_UPDATED</code>, <code>PULL_REQUEST_CLOSED</code>, <code>PULL_REQUEST_REOPENED</code>, and <code>PULL_REQUEST_MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL_REQUEST_CREATED, PULL_REQUEST_UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL_REQUEST_REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </li> </ul> </li> <li> <p>ACTOR_ACCOUNT_ID</p> <ul> <li> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </li> </ul> </li> <li> <p>HEAD_REF</p> <ul> <li> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </li> </ul> </li> <li> <p>BASE_REF</p> <ul> <li> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </li> </ul> </li> <li> <p>FILE_PATH</p> <ul> <li> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </li> </ul> </li> <li> <p>COMMIT_MESSAGE</p> <ul> <li> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </li> </ul> </li> </ul>"
+        "WebhookFilter$type": "<p> The type of webhook filter. There are eight webhook filter types: <code>EVENT</code>, <code>ACTOR_ACCOUNT_ID</code>, <code>HEAD_REF</code>, <code>BASE_REF</code>, <code>FILE_PATH</code>, <code>COMMIT_MESSAGE</code>, <code>TAG_NAME</code>, and <code>RELEASE_NAME</code>. </p> <ul> <li> <p> EVENT </p> <ul> <li> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of eight event types: <code>PUSH</code>, <code>PULL_REQUEST_CREATED</code>, <code>PULL_REQUEST_UPDATED</code>, <code>PULL_REQUEST_CLOSED</code>, <code>PULL_REQUEST_REOPENED</code>, <code>PULL_REQUEST_MERGED</code>, <code>RELEASED</code>, and <code>PRERELEASED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL_REQUEST_CREATED, PULL_REQUEST_UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL_REQUEST_REOPENED</code> works with GitHub and GitHub Enterprise only. The <code>RELEASED</code> and <code>PRERELEASED</code> work with GitHub only.</p> </note> </li> </ul> </li> <li> <p>ACTOR_ACCOUNT_ID</p> <ul> <li> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </li> </ul> </li> <li> <p>HEAD_REF</p> <ul> <li> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <note> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events.</p> </note> </li> </ul> </li> <li> <p>BASE_REF</p> <ul> <li> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </li> </ul> </li> <li> <p>FILE_PATH</p> <ul> <li> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </li> </ul> </li> <li> <p>COMMIT_MESSAGE</p> <ul> <li> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </li> </ul> </li> <li> <p>TAG_NAME</p> <ul> <li> <p>A webhook triggers a build when the tag name of the release matches the regular expression <code>pattern</code>.</p> <note> <p> Works with <code>RELEASED</code> and <code>PRERELEASED</code> events only. </p> </note> </li> </ul> </li> <li> <p>RELEASE_NAME</p> <ul> <li> <p>A webhook triggers a build when the release name matches the regular expression <code>pattern</code>.</p> <note> <p> Works with <code>RELEASED</code> and <code>PRERELEASED</code> events only. </p> </note> </li> </ul> </li> </ul>"
       }
     },
     "WrapperBoolean": {

apis/connect/2017-08-08/api-2.json

@@ -9022,7 +9022,9 @@
         "REAL_TIME_CONTACT_ANALYSIS_SEGMENTS",
         "ATTACHMENTS",
         "CONTACT_EVALUATIONS",
-        "SCREEN_RECORDINGS"
+        "SCREEN_RECORDINGS",
+        "REAL_TIME_CONTACT_ANALYSIS_CHAT_SEGMENTS",
+        "REAL_TIME_CONTACT_ANALYSIS_VOICE_SEGMENTS"
       ]
     },
     "InstanceSummary":{

apis/connect/2017-08-08/docs-2.json

@@ -3873,7 +3873,7 @@
     "InstanceStorageResourceType": {
       "base": null,
       "refs": {
-        "AssociateInstanceStorageConfigRequest$ResourceType": "<p>A valid resource type.</p>",
+        "AssociateInstanceStorageConfigRequest$ResourceType": "<p>A valid resource type. To <a href=\"https://docs.aws.amazon.com/connect/latest/adminguide/enable-contact-analysis-segment-streams.html\">enable streaming for real-time analysis of contacts</a>, use the following types:</p> <ul> <li> <p>For chat contacts, use <code>REAL_TIME_CONTACT_ANALYSIS_CHAT_SEGMENTS</code>.</p> </li> <li> <p>For voice contacts, use <code>REAL_TIME_CONTACT_ANALYSIS_VOICE_SEGMENTS</code>.</p> </li> </ul> <note> <p> <code>REAL_TIME_CONTACT_ANALYSIS_SEGMENTS</code> is deprecated, but it is still supported and will apply only to VOICE channel contacts. Use <code>REAL_TIME_CONTACT_ANALYSIS_VOICE_SEGMENTS</code> for voice contacts moving forward.</p> <p>If you have previously associated a stream with <code>REAL_TIME_CONTACT_ANALYSIS_SEGMENTS</code>, no action is needed to update the stream to <code>REAL_TIME_CONTACT_ANALYSIS_VOICE_SEGMENTS</code>.</p> </note>",
         "DescribeInstanceStorageConfigRequest$ResourceType": "<p>A valid resource type.</p>",
         "DisassociateInstanceStorageConfigRequest$ResourceType": "<p>A valid resource type.</p>",
         "ListInstanceStorageConfigsRequest$ResourceType": "<p>A valid resource type.</p>",