AWS awscloudtrail documentation change
Summary
Replaced Presto references with Trino in CloudTrail Lake query documentation
Security assessment
Consistency update for SQL engine branding. No security implications identified in query engine change documentation.
Diff
diff --git a/awscloudtrail/latest/userguide/cloudtrail-lake.md b/awscloudtrail/latest/userguide/cloudtrail-lake.md index 9c3635441..fc2d0f081 100644 --- a//awscloudtrail/latest/userguide/cloudtrail-lake.md +++ b//awscloudtrail/latest/userguide/cloudtrail-lake.md @@ -35 +35 @@ CloudTrail typically delivers events within an average of about 5 minutes of an -CloudTrail Lake queries offer a deeper and more customizable view of events than simple key and value lookups in **Event history** , or running `LookupEvents`. An **Event history** search is limited to a single AWS account, only returns events from a single AWS Region, and cannot query multiple attributes. In contrast, CloudTrail Lake users can run complex SQL queries across multiple event fields. CloudTrail Lake supports all valid Presto `SELECT` statements and functions. For more information about the supported SQL functions and operators, see [Functions and Operators](https://prestodb.io/docs/current/functions.html) on the Presto documentation website. +CloudTrail Lake queries offer a deeper and more customizable view of events than simple key and value lookups in **Event history** , or running `LookupEvents`. An **Event history** search is limited to a single AWS account, only returns events from a single AWS Region, and cannot query multiple attributes. In contrast, CloudTrail Lake users can run complex SQL queries across multiple event fields. CloudTrail Lake supports all valid Trino `SELECT` statements and functions. For more information about the supported SQL functions and operators, see [Functions and Operators](https://trino.io/docs/current/functions.html) on the Trino documentation website.