|
46 | 46 | {"shape":"UnauthorizedException"},
|
47 | 47 | {"shape":"NotFoundException"},
|
48 | 48 | {"shape":"ForbiddenException"},
|
49 |
| - {"shape":"ServiceUnavailableException"} |
| 49 | + {"shape":"ServiceUnavailableException"}, |
| 50 | + {"shape":"ServiceFailureException"}, |
| 51 | + {"shape":"ThrottlingException"} |
50 | 52 | ],
|
51 | 53 | "documentation":"<p>Updates <code>AttendeeCapabilities</code> except the capabilities listed in an <code>ExcludedAttendeeIds</code> table.</p> <note> <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 .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <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> 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 to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <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> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <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> , and if the attendee turned on their video or content streams, remote attendees can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
|
52 | 54 | },
|
|
81 | 83 | "output":{"shape":"CreateMeetingResponse"},
|
82 | 84 | "errors":[
|
83 | 85 | {"shape":"BadRequestException"},
|
| 86 | + {"shape":"ConflictException"}, |
84 | 87 | {"shape":"ForbiddenException"},
|
85 | 88 | {"shape":"UnauthorizedException"},
|
86 | 89 | {"shape":"ThrottlingException"},
|
|
100 | 103 | "output":{"shape":"CreateMeetingWithAttendeesResponse"},
|
101 | 104 | "errors":[
|
102 | 105 | {"shape":"BadRequestException"},
|
| 106 | + {"shape":"ConflictException"}, |
103 | 107 | {"shape":"ForbiddenException"},
|
104 | 108 | {"shape":"UnauthorizedException"},
|
105 | 109 | {"shape":"ThrottlingException"},
|
|
215 | 219 | "input":{"shape":"ListTagsForResourceRequest"},
|
216 | 220 | "output":{"shape":"ListTagsForResourceResponse"},
|
217 | 221 | "errors":[
|
| 222 | + {"shape":"BadRequestException"}, |
| 223 | + {"shape":"ForbiddenException"}, |
| 224 | + {"shape":"UnauthorizedException"}, |
| 225 | + {"shape":"LimitExceededException"}, |
| 226 | + {"shape":"ServiceUnavailableException"}, |
| 227 | + {"shape":"ServiceFailureException"}, |
| 228 | + {"shape":"ThrottlingException"}, |
218 | 229 | {"shape":"ResourceNotFoundException"}
|
219 | 230 | ],
|
220 | 231 | "documentation":"<p>Returns a list of the tags available for the specified resource.</p>"
|
|
271 | 282 | "output":{"shape":"TagResourceResponse"},
|
272 | 283 | "errors":[
|
273 | 284 | {"shape":"BadRequestException"},
|
| 285 | + {"shape":"ForbiddenException"}, |
| 286 | + {"shape":"UnauthorizedException"}, |
| 287 | + {"shape":"LimitExceededException"}, |
| 288 | + {"shape":"ServiceUnavailableException"}, |
| 289 | + {"shape":"ServiceFailureException"}, |
| 290 | + {"shape":"ThrottlingException"}, |
274 | 291 | {"shape":"ResourceNotFoundException"},
|
275 | 292 | {"shape":"TooManyTagsException"}
|
276 | 293 | ],
|
|
287 | 304 | "output":{"shape":"UntagResourceResponse"},
|
288 | 305 | "errors":[
|
289 | 306 | {"shape":"BadRequestException"},
|
| 307 | + {"shape":"ForbiddenException"}, |
| 308 | + {"shape":"UnauthorizedException"}, |
| 309 | + {"shape":"LimitExceededException"}, |
| 310 | + {"shape":"ServiceUnavailableException"}, |
| 311 | + {"shape":"ServiceFailureException"}, |
| 312 | + {"shape":"ThrottlingException"}, |
290 | 313 | {"shape":"ResourceNotFoundException"}
|
291 | 314 | ],
|
292 | 315 | "documentation":"<p>Removes the specified tags from the specified resources. When you specify a tag key, the action removes both that key and its associated value. The operation succeeds even if you attempt to remove tags from a resource that were already removed. Note the following:</p> <ul> <li> <p>To remove tags from a resource, you need the necessary permissions for the service that the resource belongs to as well as permissions for removing tags. For more information, see the documentation for the service whose resource you want to untag.</p> </li> <li> <p>You can only tag resources that are located in the specified AWS Region for the calling AWS account.</p> </li> </ul> <p> <b>Minimum permissions</b> </p> <p>In addition to the <code>tag:UntagResources</code> permission required by this operation, you must also have the remove tags permission defined by the service that created the resource. For example, to remove the tags from an Amazon EC2 instance using the <code>UntagResources</code> operation, you must have both of the following permissions:</p> <p> <code>tag:UntagResource</code> </p> <p> <code>ChimeSDKMeetings:DeleteTags</code> </p>"
|
|
305 | 328 | {"shape":"UnauthorizedException"},
|
306 | 329 | {"shape":"NotFoundException"},
|
307 | 330 | {"shape":"ForbiddenException"},
|
308 |
| - {"shape":"ServiceUnavailableException"} |
| 331 | + {"shape":"ServiceUnavailableException"}, |
| 332 | + {"shape":"ServiceFailureException"}, |
| 333 | + {"shape":"ThrottlingException"} |
309 | 334 | ],
|
310 | 335 | "documentation":"<p>The capabilities that you want to update.</p> <note> <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 .</p> </note> <p>When using capabilities, be aware of these corner cases:</p> <ul> <li> <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> 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 to receive and you set your <code>content</code> capability to not receive.</p> </li> <li> <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> , and if the attendee left their microphone unmuted, audio will flow from the attendee to the other meeting participants.</p> </li> <li> <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> , and if the attendee turned on their video or content streams, remote attendees can receive those streams, but only after media renegotiation between the client and the Amazon Chime back-end server.</p> </li> </ul>"
|
311 | 336 | }
|
|
0 commit comments