Module aws_sdk_cloudtrail::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS CloudTrail can respond with.

Structs

• AdvancedEventSelector

  Advanced event selectors let you create fine-grained selectors for CloudTrail management and data events. They help you control costs by logging only those events that are important to you. For more information about advanced event selectors, see Logging management events and Logging data events in the CloudTrail User Guide.

• AdvancedFieldSelector

  A single selector statement in an advanced event selector.

• Channel

  Contains information about a returned CloudTrail channel.

• DataResource

  The Amazon S3 buckets, Lambda functions, or Amazon DynamoDB tables that you specify in your event selectors for your trail to log data events. Data events provide information about the resource operations performed on or within a resource itself. These are also known as data plane operations. You can specify up to 250 data resources for a trail.

• Destination

  Contains information about the destination receiving events.

• Event

  Contains information about an event that was returned by a lookup request. The result includes a representation of a CloudTrail event.

• EventDataStore

  A storage lake of event data against which you can run complex SQL-based queries. An event data store can include events that you have logged on your account. To select events for an event data store, use advanced event selectors.

• EventSelector

  Use event selectors to further specify the management and data event settings for your trail. By default, trails created without specific event selectors will be configured to log all read and write management events, and no data events. When an event occurs in your account, CloudTrail evaluates the event selector for all trails. For each trail, if the event matches any event selector, the trail processes and logs the event. If the event doesn't match any event selector, the trail doesn't log the event.

• ImportFailureListItem

  Provides information about an import failure.

• ImportSource

  The import source.

• ImportStatistics

  Provides statistics for the specified ImportID. CloudTrail does not update import statistics in real-time. Returned values for parameters such as EventsCompleted may be lower than the actual value, because CloudTrail updates statistics incrementally over the course of the import.

• ImportsListItem

  Contains information about an import that was returned by a lookup request.

• IngestionStatus

  A table showing information about the most recent successful and failed attempts to ingest events.

• InsightSelector

  A JSON string that contains a list of Insights types that are logged on a trail or event data store.

• LookupAttribute

  Specifies an attribute and value that filter the events returned.

• PublicKey

  Contains information about a returned public key.

• Query

  A SQL string of criteria about events that you want to collect in an event data store.

• QueryStatistics

  Metadata about a query, such as the number of results.

• QueryStatisticsForDescribeQuery

  Gets metadata about a query, including the number of events that were matched, the total number of events scanned, the query run time in milliseconds, and the query's creation time.

• Resource

  Specifies the type and name of a resource referenced by an event.

• ResourceTag

  A resource tag.

• S3ImportSource

  The settings for the source S3 bucket.

• SourceConfig

  Contains configuration information about the channel.

• Tag

  A custom key-value pair associated with a resource such as a CloudTrail trail, event data store, or channel.

• Trail

  The settings for a trail.

• TrailInfo

  Information about a CloudTrail trail, including the trail's name, home Region, and Amazon Resource Name (ARN).

Enums

• BillingMode
  When writing a match expression against BillingMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DeliveryStatus
  When writing a match expression against DeliveryStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DestinationType
  When writing a match expression against DestinationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventCategory
  When writing a match expression against EventCategory, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventDataStoreStatus
  When writing a match expression against EventDataStoreStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• FederationStatus
  When writing a match expression against FederationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ImportFailureStatus
  When writing a match expression against ImportFailureStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ImportStatus
  When writing a match expression against ImportStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InsightType
  When writing a match expression against InsightType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InsightsMetricDataType
  When writing a match expression against InsightsMetricDataType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LookupAttributeKey
  When writing a match expression against LookupAttributeKey, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryStatus
  When writing a match expression against QueryStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ReadWriteType
  When writing a match expression against ReadWriteType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.