Skip to content

CloudTrail  >  Operations  >  stop_event_data_store_ingestion

stop_event_data_store_ingestion

Operation

stop_event_data_store_ingestion async 

stop_event_data_store_ingestion(input: StopEventDataStoreIngestionInput, plugins: list[Plugin] | None = None) -> StopEventDataStoreIngestionOutput
Warning

CloudTrail Lake will no longer be open to new customers starting May 31, 2026. If you would like to use CloudTrail Lake, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see CloudTrail Lake availability change.

Stops the ingestion of live events on an event data store specified as either an ARN or the ID portion of the ARN. To stop ingestion, the event data store Status must be ENABLED and the eventCategory must be Management, Data, NetworkActivity, or ConfigurationItem.

Parameters:

Name Type Description Default
input StopEventDataStoreIngestionInput

An instance of StopEventDataStoreIngestionInput.

 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
StopEventDataStoreIngestionOutput

An instance of StopEventDataStoreIngestionOutput.

Input

StopEventDataStoreIngestionInput dataclass

Dataclass for StopEventDataStoreIngestionInput structure.

Attributes

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

The ARN (or ID suffix of the ARN) of the event data store for which you want to stop ingestion.

Output

StopEventDataStoreIngestionOutput dataclass

Dataclass for StopEventDataStoreIngestionOutput 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.