put_verification_state_on_violation
async
¶
put_verification_state_on_violation(
violation_id: ViolationId,
verification_state: VerificationState,
*,
config_overrides: Optional[AsyncIoTClientConfig] = None,
verification_state_description: Optional[VerificationStateDescription] = None,
) -> PutVerificationStateOnViolationResponse
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.
Set a verification state and provide a description of that verification state on a violation (detect alarm).
Parameters:
-
violation_id(ViolationId) –The violation ID.
-
verification_state(VerificationState) –The verification state of the violation.
-
verification_state_description(Optional[VerificationStateDescription], default:None) –The description of the verification state of the violation (detect alarm).
Raises:
-
InternalFailureException–An unexpected error has occurred.
-
InvalidRequestException–The request is not valid.
-
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
15487 15488 15489 15490 15491 15492 15493 15494 15495 15496 15497 15498 15499 15500 15501 15502 15503 15504 15505 15506 15507 15508 15509 15510 15511 15512 15513 15514 15515 15516 15517 15518 15519 15520 15521 15522 15523 15524 15525 15526 15527 15528 15529 15530 15531 15532 15533 15534 15535 15536 15537 15538 15539 15540 15541 15542 | |