start_detect_mitigation_actions_task
async
¶
start_detect_mitigation_actions_task(
task_id: MitigationActionsTaskId,
target: DetectMitigationActionsTaskTarget,
actions: DetectMitigationActionsToExecuteList,
client_request_token: ClientRequestToken,
*,
config_overrides: Optional[AsyncIoTClientConfig] = None,
violation_event_occurrence_range: Optional[ViolationEventOccurrenceRange] = None,
include_only_active_violations: Optional[NullableBoolean] = None,
include_suppressed_alerts: Optional[NullableBoolean] = None,
) -> StartDetectMitigationActionsTaskResponse
The IoT Device Defender detect feature will no longer be available to new customers starting August 31, 2026. If you would like to use the detect feature, sign up prior to August 31, 2026. To learn about alternatives to IoT Device Defender detect, see IoT Device Defender detect feature availability change in the IoT Device Defender Developer Guide. There is no change to IoT Device Defender audit availability.
Starts a Device Defender ML Detect mitigation actions task.
Requires permission to access the StartDetectMitigationActionsTask action.
Parameters:
-
task_id(MitigationActionsTaskId) –The unique identifier of the task.
-
target(DetectMitigationActionsTaskTarget) –Specifies the ML Detect findings to which the mitigation actions are applied.
-
actions(DetectMitigationActionsToExecuteList) –The actions to be performed when a device has unexpected behavior.
-
violation_event_occurrence_range(Optional[ViolationEventOccurrenceRange], default:None) –Specifies the time period of which violation events occurred between.
-
include_only_active_violations(Optional[NullableBoolean], default:None) –Specifies to list only active violations.
-
include_suppressed_alerts(Optional[NullableBoolean], default:None) –Specifies to include suppressed alerts.
-
client_request_token(ClientRequestToken) –Each mitigation action task must have a unique client request token. If you try to create a new task with the same token as a task that already exists, an exception occurs. If you omit this value, Amazon Web Services SDKs will automatically generate a unique client request.
Raises:
-
InternalFailureException–An unexpected error has occurred.
-
InvalidRequestException–The request is not valid.
-
LimitExceededException–A limit has been exceeded.
-
TaskAlreadyExistsException–This exception occurs if you attempt to start a task with the same task-id as an existing task but with a different clientRequestToken.
-
ThrottlingException–The rate exceeds the limit.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iot/_services/async_io_t.py
16445 16446 16447 16448 16449 16450 16451 16452 16453 16454 16455 16456 16457 16458 16459 16460 16461 16462 16463 16464 16465 16466 16467 16468 16469 16470 16471 16472 16473 16474 16475 16476 16477 16478 16479 16480 16481 16482 16483 16484 16485 16486 16487 16488 16489 16490 16491 16492 16493 16494 16495 16496 16497 16498 16499 16500 16501 16502 16503 16504 16505 16506 16507 16508 16509 16510 16511 16512 16513 16514 16515 16516 16517 16518 16519 16520 16521 16522 | |