AWS awscloudtrail documentation change
Summary
Updated terminology capitalization and formatting changes (e.g., 'event history' to 'Event history' with bold formatting), minor wording adjustments for consistency, and CLI command formatting updates
Security assessment
Changes are editorial/formatting improvements (capitalization, bold emphasis, console preposition changes) without introducing new security content or addressing vulnerabilities. CloudTrail event history is security-relevant by nature, but these changes only enhance existing documentation clarity.
Diff
diff --git a/awscloudtrail/latest/userguide/view-cloudtrail-events.md b/awscloudtrail/latest/userguide/view-cloudtrail-events.md index 172a1a662..0f1ce5694 100644 --- a/awscloudtrail/latest/userguide/view-cloudtrail-events.md +++ b/awscloudtrail/latest/userguide/view-cloudtrail-events.md @@ -7 +7 @@ Limitations of Event history -# Working with CloudTrail event history +# Working with CloudTrail Event history @@ -9 +9 @@ Limitations of Event history -CloudTrail is enabled by default for your AWS account and you automatically have access to the CloudTrail event history. The event history provides a viewable, searchable, downloadable, and immutable record of the past 90 days of management events in an AWS Region. These events capture activity made through the AWS Management Console, AWS Command Line Interface, and AWS SDKs and APIs. The event history records events in the AWS Region where the event happened. There are no CloudTrail charges for viewing the event history. +CloudTrail is enabled by default for your AWS account and you automatically have access to the CloudTrail **Event history**. The **Event history** provides a viewable, searchable, downloadable, and immutable record of the past 90 days of management events in an AWS Region. These events capture activity made through the AWS Management Console, AWS Command Line Interface, and AWS SDKs and APIs. The **Event history** records events in the AWS Region where the event happened. There are no CloudTrail charges for viewing the **Event history**. @@ -11 +11 @@ CloudTrail is enabled by default for your AWS account and you automatically have -You can look up events related to the creation, modification, or deletion of resources (such as IAM users or Amazon EC2 instances) in your AWS account on a by-Region basis on the CloudTrail console by viewing the **Event history** page. You can also look up these events by running the [`aws cloudtrail lookup-events`](https://docs.aws.amazon.com/cli/latest/reference/cloudtrail/lookup-events.html) command or by using the [`LookupEvents`](https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_LookupEvents.html) API. +You can look up events related to the creation, modification, or deletion of resources (such as IAM users or Amazon EC2 instances) in your AWS account on a by-Region basis in the CloudTrail console by viewing the **Event history** page. You can also look up these events by running the [**aws cloudtrail lookup-events**](https://docs.aws.amazon.com/cli/latest/reference/cloudtrail/lookup-events.html) command or by using the [`LookupEvents`](https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_LookupEvents.html) API. @@ -13 +13 @@ You can look up events related to the creation, modification, or deletion of res -You can use the **Event history** page on the CloudTrail console to view, search, download, archive, analyze, and respond to account activity across your AWS infrastructure. You can [customize the view](./view-cloudtrail-events-console.html#displaying-cloudtrail-events) of the **Event history** page on the console by selecting how many events to display on each page and which columns to display or hide. You can also compare the details of events in event history side-by-side. You can programmatically [look up events](./view-cloudtrail-events-cli.html) by using the AWS SDKs or AWS Command Line Interface. +You can use the **Event history** page in the CloudTrail console to view, search, download, archive, analyze, and respond to account activity across your AWS infrastructure. You can [customize the view](./view-cloudtrail-events-console.html#displaying-cloudtrail-events) of the **Event history** in the console by selecting how many events to display on each page and which columns to display or hide. You can also compare the details of events in **Event history** side-by-side. You can programmatically [look up events](./view-cloudtrail-events-cli.html) by using the AWS SDKs or AWS Command Line Interface. @@ -17 +17 @@ You can use the **Event history** page on the CloudTrail console to view, search -Over time, AWS services might add additional events. CloudTrail records these events in event history, but a full 90-day record of activity that includes added events won't be available until 90 days after it adds the events. +Over time, AWS services might add additional events. CloudTrail records these events in **Event history** , but a full 90-day record of activity that includes added events won't be available until 90 days after it adds the events. @@ -19 +19 @@ Over time, AWS services might add additional events. CloudTrail records these ev -The event history is separate from any trails or event data stores that you create for your account. Changes you make to your event data stores or trails do not affect the event history. +The **Event history** is separate from any trails or event data stores that you create for your account. Changes you make to your event data stores or trails do not affect the **Event history**. @@ -36 +36 @@ The sections which follow describe how to look up recent management events by us -The following limitations apply to the event history. +The following limitations apply to the **Event history**. @@ -40 +40 @@ The following limitations apply to the event history. - * The event history is limited to the past 90 days of events. For an ongoing record of events in your AWS account, create an [event data store](./query-event-data-store-cloudtrail.html) or a [trail](./cloudtrail-create-a-trail-using-the-console-first-time.html). + * The **Event history** is limited to the past 90 days of events. For an ongoing record of events in your AWS account, create an [event data store](./query-event-data-store-cloudtrail.html) or a [trail](./cloudtrail-create-a-trail-using-the-console-first-time.html). @@ -44 +44 @@ The following limitations apply to the event history. - * The event history doesn't provide organization level event aggregation. To record events across your organization, create an organization event data store or trail. + * The **Event history** doesn't provide organization level event aggregation. To record events across your organization, create an organization event data store or trail. @@ -46 +46 @@ The following limitations apply to the event history. - * An event history search is limited to a single AWS account, only returns events from a single AWS Region, and cannot query multiple attributes. You can only apply one attribute filter and a time range filter. + * An **Event history** search is limited to a single AWS account, only returns events from a single AWS Region, and cannot query multiple attributes. You can only apply one attribute filter and a time range filter. @@ -48 +48 @@ The following limitations apply to the event history. -You can create a CloudTrail Lake event data store to query across multiple attributes and AWS Regions. You can also query across multiple AWS accounts in an AWS Organizations organization. In CloudTrail Lake, you can query multiple event types, including management events, data events, Insights events, AWS Config configuration items, Audit Manager evidence, and non-AWS events. CloudTrail Lake queries offer a deeper and more customizable view of events than simple key and value lookups on the **Event history** page, or by running `LookupEvents`. For more information, see [Working with AWS CloudTrail Lake](./cloudtrail-lake.html) and [Create an event data store for CloudTrail events with the console](./query-event-data-store-cloudtrail.html). +You can create a CloudTrail Lake event data store to query across multiple attributes and AWS Regions. You can also query across multiple AWS accounts in an AWS Organizations organization. In CloudTrail Lake, you can query multiple event types, including management events, data events, Insights events, AWS Config configuration items, Audit Manager evidence, and non-AWS events. CloudTrail Lake queries offer a deeper and more customizable view of events than simple key and value lookups in **Event history** , or running `LookupEvents`. For more information, see [Working with AWS CloudTrail Lake](./cloudtrail-lake.html) and [Create an event data store for CloudTrail events with the console](./query-event-data-store-cloudtrail.html). @@ -50 +50 @@ You can create a CloudTrail Lake event data store to query across multiple attri - * You cannot exclude AWS KMS or Amazon RDS Data API events from event history; settings that you apply to a trail or event data store do not apply to event history. + * You cannot exclude AWS KMS or Amazon RDS Data API events from **Event history** ; settings that you apply to a trail or event data store do not apply to **Event history**.