Skip to content

GuardDuty  >  Operations  >  unarchive_findings

unarchive_findings

Operation

unarchive_findings async 

unarchive_findings(input: UnarchiveFindingsInput, plugins: list[Plugin] | None = None) -> UnarchiveFindingsOutput

Unarchives GuardDuty findings specified by the findingIds.

Parameters:

Name Type Description Default
input UnarchiveFindingsInput

An instance of UnarchiveFindingsInput.

 required
plugins list[Plugin] | None

A list of callables that modify the configuration dynamically. Changes made by these plugins only apply for the duration of the operation execution and will not affect any other operation invocations.

 None

Returns:

Type Description
UnarchiveFindingsOutput

An instance of UnarchiveFindingsOutput.

Input

UnarchiveFindingsInput dataclass

Dataclass for UnarchiveFindingsInput structure.

Attributes

detector_id class-attribute instance-attribute 
detector_id: str | None = None

The ID of the detector associated with the findings to unarchive.

To find the detectorId in the current Region, see the Settings page in the GuardDuty console, or run the ListDetectors API.

finding_ids class-attribute instance-attribute 
finding_ids: list[str] | None = None

The IDs of the findings to unarchive.

Output

UnarchiveFindingsOutput dataclass

Dataclass for UnarchiveFindingsOutput structure.

Attributes

response_metadata class-attribute instance-attribute 
response_metadata: ResponseMetadata = field(default=EMPTY_RESPONSE_METADATA, repr=False, compare=False)

Metadata about the response that produced this output. Use this to recover the request identifiers a service's support team needs in order to investigate a call. Members of the metadata are individually optional.