start_detect_mitigation_actions_task
¶
start_detect_mitigation_actions_task(
task_id: MitigationActionsTaskId,
target: DetectMitigationActionsTaskTarget,
actions: DetectMitigationActionsToExecuteList,
client_request_token: ClientRequestToken,
*,
config_overrides: Optional[IoTClientConfig] = 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/io_t.py
16202 16203 16204 16205 16206 16207 16208 16209 16210 16211 16212 16213 16214 16215 16216 16217 16218 16219 16220 16221 16222 16223 16224 16225 16226 16227 16228 16229 16230 16231 16232 16233 16234 16235 16236 16237 16238 16239 16240 16241 16242 16243 16244 16245 16246 16247 16248 16249 16250 16251 16252 16253 16254 16255 16256 16257 16258 16259 16260 16261 16262 16263 16264 16265 16266 16267 16268 16269 16270 16271 16272 16273 16274 16275 16276 16277 16278 | |