Update API model

codegen/sdk-codegen/aws-models/chime-sdk-meetings.json

@@ -64,7 +64,7 @@
  "Capabilities": {
  "target": "com.amazonaws.chimesdkmeetings#AttendeeCapabilities",
  "traits": {
- "smithy.api#documentation": "<p>The capabilities (audio, video, or content) assigned to an attendee.</p>"
+ "smithy.api#documentation": "<p>The capabilities assigned to an attendee: audio, video, or content.</p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>"
  }
  }
  },
@@ -98,7 +98,7 @@
  }
  },
  "traits": {
- "smithy.api#documentation": "<p>The media capabilities of an attendee, including audio, video and content. </p>"
+ "smithy.api#documentation": "<p>The media capabilities of an attendee: audio, video, or content. </p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>"
  }
  },
  "com.amazonaws.chimesdkmeetings#AttendeeIdItem": {
@@ -288,7 +288,7 @@
  }
  ],
  "traits": {
- "smithy.api#documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p>",
+ "smithy.api#documentation": "<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p>\n \n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>",
  "smithy.api#http": {
  "method": "PUT",
  "uri": "/meetings/{MeetingId}/attendees/capabilities?operation=batch-update-except",
@@ -509,7 +509,7 @@
  "Capabilities": {
  "target": "com.amazonaws.chimesdkmeetings#AttendeeCapabilities",
  "traits": {
- "smithy.api#documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on \n all media channels by default.</p>"
+ "smithy.api#documentation": "<p>The capabilities (<code>audio</code>, <code>video</code>, or <code>content</code>) that you want to grant an attendee. If you don't specify capabilities, all users have send and receive capabilities on \n all media channels by default.</p>\n \n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>"
  }
  }
  }
@@ -646,6 +646,12 @@
  "traits": {
  "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>"
  }
+ },
+ "TenantIds": {
+ "target": "com.amazonaws.chimesdkmeetings#TenantIdList",
+ "traits": {
+ "smithy.api#documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>"
+ }
  }
  }
  },
@@ -755,6 +761,12 @@
  "traits": {
  "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to the new meeting.</p>"
  }
+ },
+ "TenantIds": {
+ "target": "com.amazonaws.chimesdkmeetings#TenantIdList",
+ "traits": {
+ "smithy.api#documentation": "<p>A consistent and opaque identifier, created and maintained by the builder to represent a segment of their users.</p>"
+ }
  }
  }
  },
@@ -940,7 +952,7 @@
  "Region": {
  "target": "com.amazonaws.chimesdkmeetings#TranscribeMedicalRegion",
  "traits": {
- "smithy.api#documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region.</p>"
+ "smithy.api#documentation": "<p>The AWS Region passed to Amazon Transcribe Medical. If you don't specify a Region, Amazon Chime uses the meeting's Region. </p>"
  }
  },
  "ContentIdentificationType": {
@@ -1483,6 +1495,12 @@
  "traits": {
  "smithy.api#documentation": "<p>When specified, replicates the media from the primary meeting to this meeting.</p>"
  }
+ },
+ "TenantIds": {
+ "target": "com.amazonaws.chimesdkmeetings#TenantIdList",
+ "traits": {
+ "smithy.api#documentation": "<p>Array of strings.</p>"
+ }
  }
  },
  "traits": {
@@ -1602,7 +1620,7 @@
  }
  },
  "traits": {
- "smithy.api#documentation": "<p>The service is currently unavailable.</p>",
+ "smithy.api#documentation": "<p>The service encountered an unexpected error.</p>",
  "smithy.api#error": "server",
  "smithy.api#httpError": 500
  }
@@ -1767,6 +1785,28 @@
  }
  }
  },
+ "com.amazonaws.chimesdkmeetings#TenantId": {
+ "type": "string",
+ "traits": {
+ "smithy.api#length": {
+ "min": 2,
+ "max": 256
+ },
+ "smithy.api#pattern": "^(?!.*?(.)\\1{3})[-_!@#$a-zA-Z0-9]*$"
+ }
+ },
+ "com.amazonaws.chimesdkmeetings#TenantIdList": {
+ "type": "list",
+ "member": {
+ "target": "com.amazonaws.chimesdkmeetings#TenantId"
+ },
+ "traits": {
+ "smithy.api#length": {
+ "min": 1,
+ "max": 5
+ }
+ }
+ },
  "com.amazonaws.chimesdkmeetings#ThrottlingException": {
  "type": "structure",
  "members": {
@@ -1781,7 +1821,7 @@
  }
  },
  "traits": {
- "smithy.api#documentation": "<p>The number of requests exceeds the limit.</p>",
+ "smithy.api#documentation": "<p>The number of customer requests exceeds the request rate limit.</p>",
  "smithy.api#error": "client",
  "smithy.api#httpError": 429
  }
@@ -2186,7 +2226,7 @@
  }
  ],
  "traits": {
- "smithy.api#documentation": "<p>The capabilties that you want to update.</p>",
+ "smithy.api#documentation": "<p>The capabilties that you want to update.</p>\n <note>\n <p>You use the capabilities with a set of values that control what the capabilities can do, such as <code>SendReceive</code> data. For more information about those values, see \n .</p>\n </note>\n \n <p>When using capabilities, be aware of these corner cases:</p>\n <ul>\n <li>\n <p>You can't set <code>content</code> capabilities to <code>SendReceive</code> or <code>Receive</code> unless you also set <code>video</code> capabilities to <code>SendReceive</code> \n or <code>Receive</code>. If you don't set the <code>video</code> capability to receive, the response will contain an HTTP 400 Bad Request status code. However, you can set your <code>video</code> capability \n to receive and you set your <code>content</code> capability to not receive.</p> \n </li>\n <li>\n <p>When you change an <code>audio</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p>\n </li>\n <li>\n <p>When you change a <code>video</code> or <code>content</code> capability from <code>None</code> or <code>Receive</code> to <code>Send</code> or <code>SendReceive</code> , \n and if the attendee turned on their video or content streams, remote attendess can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p>\n </li>\n </ul>",
  "smithy.api#http": {
  "method": "PUT",
  "uri": "/meetings/{MeetingId}/attendees/{AttendeeId}/capabilities",
@@ -2226,7 +2266,10 @@
  "type": "structure",
  "members": {
  "Attendee": {
- "target": "com.amazonaws.chimesdkmeetings#Attendee"
+ "target": "com.amazonaws.chimesdkmeetings#Attendee",
+ "traits": {
+ "smithy.api#documentation": "<p>The updated attendee data.</p>"
+ }
  }
  }
  }

codegen/sdk-codegen/aws-models/database-migration-service.json

@@ -338,6 +338,9 @@
  },
  {
  "target": "com.amazonaws.databasemigrationservice#TestConnection"
+ },
+ {
+ "target": "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridge"
  }
  ]
  },
@@ -10511,6 +10514,54 @@
  "smithy.api#documentation": "<p></p>"
  }
  },
+ "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridge": {
+ "type": "operation",
+ "input": {
+ "target": "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridgeMessage"
+ },
+ "output": {
+ "target": "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridgeResponse"
+ },
+ "errors": [
+ {
+ "target": "com.amazonaws.databasemigrationservice#AccessDeniedFault"
+ },
+ {
+ "target": "com.amazonaws.databasemigrationservice#InvalidResourceStateFault"
+ }
+ ],
+ "traits": {
+ "smithy.api#documentation": "<p>Migrates 10 active and enabled Amazon SNS subscriptions at a time and converts them to corresponding Amazon EventBridge rules.\n By default, this operation migrates subscriptions only when all your replication instance versions are 3.4.6 or higher.\n If any replication instances are from versions earlier than 3.4.6, the operation raises an error and tells you\n to upgrade these instances to version 3.4.6 or higher. To enable migration regardless of version, set the <code>Force</code>\n option to true. However, if you don't upgrade instances earlier than version 3.4.6, some types of events might not be\n available when you use Amazon EventBridge.</p>\n <p>To call this operation, make sure that you have certain permissions added to your user account.\n For more information, see <a href=\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Events.html#CHAP_Events-migrate-to-eventbridge\">Migrating event subscriptions to Amazon EventBridge</a>\n in the <i>Amazon Web Services Database Migration Service User Guide</i>.</p>"
+ }
+ },
+ "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridgeMessage": {
+ "type": "structure",
+ "members": {
+ "ForceMove": {
+ "target": "com.amazonaws.databasemigrationservice#BooleanOptional",
+ "traits": {
+ "smithy.api#documentation": "<p>When set to true, this operation migrates DMS subscriptions for Amazon SNS\n notifications no matter what your replication instance version is. If not set or set to\n false, this operation runs only when all your replication instances are from DMS\n version 3.4.6 or higher.\n </p>"
+ }
+ }
+ },
+ "traits": {
+ "smithy.api#documentation": "<p></p>"
+ }
+ },
+ "com.amazonaws.databasemigrationservice#UpdateSubscriptionsToEventBridgeResponse": {
+ "type": "structure",
+ "members": {
+ "Result": {
+ "target": "com.amazonaws.databasemigrationservice#String",
+ "traits": {
+ "smithy.api#documentation": "<p>A string that indicates how many event subscriptions were migrated and how many remain to be migrated.</p>"
+ }
+ }
+ },
+ "traits": {
+ "smithy.api#documentation": "<p></p>"
+ }
+ },
  "com.amazonaws.databasemigrationservice#UpgradeDependencyFailureFault": {
  "type": "structure",
  "members": {