IoT.Client.
start_detect_mitigation_actions_task
(**kwargs)¶Starts a Device Defender ML Detect mitigation actions task.
Requires permission to access the StartDetectMitigationActionsTask action.
See also: AWS API Documentation
Request Syntax
response = client.start_detect_mitigation_actions_task(
taskId='string',
target={
'violationIds': [
'string',
],
'securityProfileName': 'string',
'behaviorName': 'string'
},
actions=[
'string',
],
violationEventOccurrenceRange={
'startTime': datetime(2015, 1, 1),
'endTime': datetime(2015, 1, 1)
},
includeOnlyActiveViolations=True|False,
includeSuppressedAlerts=True|False,
clientRequestToken='string'
)
[REQUIRED]
The unique identifier of the task.
[REQUIRED]
Specifies the ML Detect findings to which the mitigation actions are applied.
The unique identifiers of the violations.
The name of the security profile.
The name of the behavior.
[REQUIRED]
The actions to be performed when a device has unexpected behavior.
Specifies the time period of which violation events occurred between.
The start date and time of a time period in which violation events occurred.
The end date and time of a time period in which violation events occurred.
[REQUIRED]
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.
This field is autopopulated if not provided.
dict
Response Syntax
{
'taskId': 'string'
}
Response Structure
(dict) --
taskId (string) --
The unique identifier of the task.
Exceptions
IoT.Client.exceptions.InvalidRequestException
IoT.Client.exceptions.TaskAlreadyExistsException
IoT.Client.exceptions.LimitExceededException
IoT.Client.exceptions.ThrottlingException
IoT.Client.exceptions.InternalFailureException