CloudTrail concepts
This section summarizes basic concepts related to CloudTrail.
Concepts:
CloudTrail events
An event in CloudTrail is the record of an activity in an Amazon account. This activity can be an action taken by an IAM identity, or service that is monitorable by CloudTrail. CloudTrail events provide a history of both API and non-API account activity made through the Amazon Web Services Management Console, Amazon SDKs, command line tools, and other Amazon services.
CloudTrail log files aren't an ordered stack trace of the public API calls, so events don't appear in any specific order.
CloudTrail logs four types of events:
All event types use a CloudTrail JSON log format.
By default, trails and event data stores log management events, but not data or Insights events.
For information about how Amazon Web Services services integrate with CloudTrail, see Amazon service topics for CloudTrail.
Management events
Management events provide information about management operations that are performed on resources in your Amazon account. These are also known as control plane operations.
Example management events include:
-
Configuring security (for example, Amazon Identity and Access Management
AttachRolePolicyAPI operations). -
Registering devices (for example, Amazon EC2
CreateDefaultVpcAPI operations). -
Configuring rules for routing data (for example, Amazon EC2
CreateSubnetAPI operations). -
Setting up logging (for example, Amazon CloudTrail
CreateTrailAPI operations).
Management events can also include non-API events that occur in your account. For
example, when a user signs in to your account, CloudTrail logs the
ConsoleLogin event. For more information, see Non-API events captured by CloudTrail.
By default, CloudTrail trails and CloudTrail Lake event data stores log management events. For more information about logging management events, see Logging management events.
Data events
Data events provide information about the resource operations performed on or in a resource. These are also known as data plane operations. Data events are often high-volume activities.
Example data events include:
-
Amazon S3 object-level API activity (for example,
GetObject,DeleteObject, andPutObjectAPI operations) on objects in S3 buckets. -
Amazon Lambda function execution activity (the
InvokeAPI). -
CloudTrail
PutAuditEventsactivity on a CloudTrail Lake channel that is used to log events from outside Amazon. -
Amazon SNS
PublishandPublishBatchAPI operations on topics.
The following table shows the resource types available for trails. The Resource type (console) column shows the appropriate selection in the console.
The resources.type value column shows the
resources.type value that you would specify to include data
events of that type in your trail using the Amazon CLI or CloudTrail APIs.
For trails, you can use basic or advanced event selectors to log data events for Amazon S3 objects in general purpose buckets, Lambda functions, and DynamoDB tables (shown in the first three rows of the table). You can use only advanced event selectors to log the resource types shown in the remaining rows.
Data events supported by Amazon CloudTrail
| Amazon Web Services service | Description | Resource type (console) | resources.type value |
|---|---|---|---|
Amazon AppConfig |
Amazon AppConfig API activity for configuration operations such as calls to StartConfigurationSession and GetLatestConfiguration. For more information, see Amazon AppConfig. |
Amazon AppConfig |
|
Amazon AppSync |
Amazon AppSync API activity on AppSync GraphQL APIs. For more information, see Amazon AppSync. |
AppSync GraphQL |
|
Amazon Bedrock |
Amazon Bedrock APIKey CredentialProvider API activity. |
Bedrock-AgentCore APIKey CredentialProvider |
|
Amazon Bedrock |
Amazon Bedrock Browser API activity. |
Bedrock-AgentCore Browser |
|
Amazon Bedrock |
Amazon Bedrock Browser-Custom API activity. |
Bedrock-AgentCore Browser-Custom |
|
Bedrock-AgentCore Browser Profile |
API activity on |
Bedrock-AgentCore Browser Profile |
|
Amazon Bedrock |
Amazon Bedrock Code-Interpreter API activity. |
Bedrock-AgentCore Code-Interpreter |
|
Amazon Bedrock |
Amazon Bedrock Code-Interpreter-Custom API activity. |
Bedrock-AgentCore Code-Interpreter-Custom |
|
Amazon Bedrock |
Amazon Bedrock Gateway API activity. |
Bedrock-AgentCore Gateway |
|
Amazon Bedrock |
Amazon Bedrock Oauth2 CredentialProvider API activity. |
Bedrock-AgentCore Oauth2 CredentialProvider |
|
Amazon Bedrock |
Amazon Bedrock Runtime API activity. |
Bedrock-AgentCore Runtime |
|
Amazon Bedrock |
Amazon Bedrock Runtime-Endpoint API activity. |
Bedrock-AgentCore Runtime-Endpoint |
|
Amazon Bedrock |
Amazon Bedrock Token Vault API activity. |
Bedrock-AgentCore Token Vault |
|
Amazon Bedrock |
Amazon Bedrock Workload Identity API activity. |
Bedrock-AgentCore Workload Identity |
|
Amazon Bedrock |
Amazon Bedrock Workload Identity Directory API activity. |
Bedrock-AgentCore Workload Identity Directory |
|
Amazon Keyspaces (for Apache Cassandra) |
Amazon Keyspaces (for Apache Cassandra) API activity on Cassandra CDC streams. |
Cassandra CDC streams |
|
Amazon Keyspaces (for Apache Cassandra) |
Amazon Keyspaces API activity on a table. For more information, see Amazon Keyspaces (for Apache Cassandra). |
Cassandra table |
|
Amazon CloudWatch |
Amazon CloudWatch API activity on metrics. For more information, see Amazon CloudWatch. |
CloudWatch metric |
|
Amazon Cognito |
Amazon Cognito API activity on Amazon Cognito identity pools. For more information, see Amazon Cognito. |
Cognito Identity Pools |
|
Amazon DynamoDB |
Amazon DynamoDB API activity on streams. For more information, see Amazon DynamoDB. |
DynamoDB Streams |
|
Amazon DynamoDB |
Amazon DynamoDB item-level API activity on tables (for example, PutItem, DeleteItem, and UpdateItem API operations). For tables with streams enabled, the resources field in the data event contains both Amazon::DynamoDB::Stream and Amazon::DynamoDB::Table. If you specify Amazon::DynamoDB::Table for the resources.type, it will log both DynamoDB table and DynamoDB streams events by default. To exclude streams events, add a filter on the eventName field. For more information, see Amazon DynamoDB. |
DynamoDB |
|
Amazon Elastic Block Store |
Amazon Elastic Block Store (EBS) direct APIs, such as PutSnapshotBlock, GetSnapshotBlock, and ListChangedBlocks on Amazon EBS snapshots. For more information, see Amazon Elastic Block Store. |
EBS direct APIs |
|
Amazon Elastic Container Service |
Amazon Elastic Container Service API activity on a container instance. |
ECS container instance |
|
Amazon Elastic Kubernetes Service |
Amazon Elastic Kubernetes Service API activity on dashboards. |
EKS dashboard |
|
EventBridge endpoint |
API activity on |
EventBridge endpoint |
|
EventBridge Custom event bus - classic |
API activity on |
EventBridge Custom event bus - classic |
|
EventBridge partner event source |
API activity on |
EventBridge partner event source |
|
EventBridge rule |
API activity on |
EventBridge rule |
|
Amazon FSx |
Amazon FSx API activity on volumes. |
FSx Volume |
|
Amazon IoT Greengrass Version 2 |
Greengrass API activity from a Greengrass core device on a component version. Greengrass doesn't log access denied events. For more information, see Amazon IoT Greengrass Version 2. |
IoT Greengrass component version |
|
Amazon IoT Greengrass Version 2 |
Greengrass API activity from a Greengrass core device on a deployment. Greengrass doesn't log access denied events. For more information, see Amazon IoT Greengrass Version 2. |
IoT Greengrass deployment |
|
Amazon GuardDuty |
GuardDuty API activity on malware scans. |
GuardDuty malware scan |
|
Amazon IoT |
Amazon IoT API activity on certificates. For more information, see Amazon IoT. |
IoT certificate |
|
Amazon IoT |
Amazon IoT API activity on things. For more information, see Amazon IoT. |
IoT thing |
|
Amazon IoT tunnel |
API activity on |
Amazon IoT tunnel |
|
Amazon IoT SiteWise |
IoT SiteWise API activity on assets. For more information, see Amazon IoT SiteWise. |
IoT SiteWise asset |
|
Amazon IoT SiteWise |
IoT SiteWise API activity on time series. For more information, see Amazon IoT SiteWise. |
IoT SiteWise time series |
|
Amazon IoT TwinMaker |
IoT TwinMaker API activity on an entity. For more information, see Amazon IoT TwinMaker. |
IoT TwinMaker entity |
|
Amazon IoT TwinMaker |
IoT TwinMaker API activity on a workspace. For more information, see Amazon IoT TwinMaker. |
IoT TwinMaker workspace |
|
Amazon Kinesis Data Streams |
Kinesis Data Streams API activity on streams. For more information, see Amazon Kinesis Data Streams. |
Kinesis stream |
|
Amazon Kinesis Data Streams |
Kinesis Data Streams API activity on stream consumers. For more information, see Amazon Kinesis Data Streams. |
Kinesis stream consumer |
|
Amazon Data Firehose |
Amazon Data Firehose delivery stream API activity. |
Amazon Data Firehose |
|
Amazon Lambda |
Amazon Lambda function execution activity (the Invoke API). |
Lambda |
|
Amazon Managed Workflows for Apache Airflow |
Amazon MWAA API activity on environments. |
Managed Apache Airflow |
|
Amazon Redshift |
Redshift API activity on clusters. |
Redshift Cluster |
|
Amazon S3 |
Amazon S3 API activity on access points. For more information, see Amazon S3. |
S3 Access Point |
|
Amazon S3 |
Amazon S3 object-level API activity (for example, GetObject, DeleteObject, and PutObject API operations) on objects in general purpose buckets. For more information, see Amazon S3. |
S3 |
|
S3 Express Access Point |
API activity on |
S3 Express Access Point |
|
Amazon S3 |
Amazon S3 object-level API activity (for example, GetObject, DeleteObject, and PutObject API operations) on objects in directory buckets. For more information, see Amazon S3. |
S3 Express |
|
Amazon S3 |
Amazon S3 Object Lambda access points API activity, such as calls to CompleteMultipartUpload and GetObject. For more information, see Amazon S3. |
S3 Object Lambda |
|
Amazon S3 Tables |
Amazon S3 API activity on tables. For more information, see Amazon S3 Tables. |
S3 table |
|
Amazon S3 Tables |
Amazon S3 API activity on table buckets. For more information, see Amazon S3 Tables. |
S3 table bucket |
|
Amazon S3 Vectors |
Amazon S3 API activity on vector indexes. For more information, see Amazon S3 Vectors. |
S3 vector index |
|
Amazon S3 Vectors |
Amazon S3 API activity on vector buckets. For more information, see Amazon S3 Vectors. |
S3 vector bucket |
|
Amazon SageMaker AI |
Amazon SageMaker AI InvokeEndpointWithResponseStream activity on endpoints. For more information, see Amazon SageMaker AI. |
SageMaker endpoint |
|
Amazon SageMaker AI |
Amazon SageMaker AI API activity on feature stores. |
SageMaker Feature Store |
|
Amazon Cloud Map |
Amazon Cloud Map API activity on a namespace. For more information, see Amazon Cloud Map. |
Amazon Cloud Map namespace |
|
Amazon Cloud Map |
Amazon Cloud Map API activity on a service. For more information, see Amazon Cloud Map. |
Amazon Cloud Map service |
|
Amazon SNS |
Amazon SNS Publish API operations on platform endpoints. For more information, see Amazon SNS. |
SNS platform endpoint |
|
Amazon SNS |
Amazon SNS Publish and PublishBatch API operations on topics. For more information, see Amazon SNS. |
SNS topic |
|
Amazon SQS |
Amazon SQS API activity on messages. For more information, see Amazon SQS. |
SQS |
|
Amazon Systems Manager |
Systems Manager API activity on managed nodes. For more information, see Amazon Systems Manager. |
Systems Manager managed node |
|
Amazon Systems Manager |
Systems Manager API activity on control channels. For more information, see Amazon Systems Manager. |
Systems Manager |
|
Amazon Step Functions |
Step Functions API activity on activities. For more information, see Amazon Step Functions. |
Step Functions activity |
|
Amazon Step Functions |
Step Functions API activity on state machines. For more information, see Amazon Step Functions. |
Step Functions state machine |
|
Amazon SWF |
Amazon SWF API activity on domains. For more information, see Amazon SWF. |
SWF domain |
|
Amazon Verified Permissions |
Amazon Verified Permissions API activity on a policy store. |
Amazon Verified Permissions |
|
Amazon X-Ray |
X-Ray API activity on traces. For more information, see Amazon X-Ray. |
X-Ray trace |
|
Data events are not logged by default when you create a trail or event data store. To record CloudTrail data events, you must explicitly add each resource type for which you want to collect activity. For more information about logging data events, see Logging data events.
Additional charges apply for logging data events. For CloudTrail pricing, see Amazon CloudTrail Pricing
Network activity events
CloudTrail network activity events enable VPC endpoint owners to record Amazon API calls made using their VPC endpoints from a private VPC to the Amazon Web Services service. Network activity events provide visibility into the resource operations performed within a VPC.
You can log network activity events for the following services:
Amazon SageMaker
Amazon IoT Secured Tunneling
Amazon SSO
Amazon Step Functions
Amazon Transfer Family
Bedrock Agent Core
DynamoDB
IoT
Relational Database Service (RDS) Core Control Plane
Simple Notification Service (SNS)
Network activity events are not logged by default when you create a trail or event data store. To record CloudTrail network activity events, you must explicitly set the event source for which you want to collect activity. For more information, see Logging network activity events.
Additional charges apply for logging network activity events. For CloudTrail pricing, see Amazon CloudTrail Pricing
Insights events
CloudTrail Insights events capture unusual API call rate or error rate activity in your Amazon account by analyzing CloudTrail management activity. Insights events provide relevant information, such as the associated API, error code, incident time, and statistics, that help you understand and act on unusual activity. Unlike other types of events captured in a CloudTrail trail or event data store, Insights events are logged only when CloudTrail detects changes in your account's API usage or error rate logging that differ significantly from the account's typical usage patterns. For more information, see Working with CloudTrail Insights.
Examples of activity that might generate Insights events include:
-
Your account typically logs no more than 20 Amazon S3
deleteBucketAPI calls per minute, but your account starts to log an average of 100deleteBucketAPI calls per minute. An Insights event is logged at the start of the unusual activity, and another Insights event is logged to mark the end of the unusual activity. -
Your account typically logs 20 calls per minute to the Amazon EC2
AuthorizeSecurityGroupIngressAPI, but your account starts to log zero calls toAuthorizeSecurityGroupIngress. An Insights event is logged at the start of the unusual activity, and ten minutes later, when the unusual activity ends, another Insights event is logged to mark the end of the unusual activity. -
Your account typically logs less than one
AccessDeniedExceptionerror in a seven-day period on the Amazon Identity and Access Management API,DeleteInstanceProfile. Your account starts to log an average of 12AccessDeniedExceptionerrors per minute on theDeleteInstanceProfileAPI call. An Insights event is logged at the start of the unusual error rate activity, and another Insights event is logged to mark the end of the unusual activity.
These examples are provided for illustration purposes only. Your results may vary depending on your use case.
To log CloudTrail Insights events, you must explicitly enable Insights events on a new or existing trail or event data store. For more information about creating a trail, see Creating a trail with the CloudTrail console. For more information about creating an event data store, see Create an event data store for Insights events with the console.
Additional charges apply for Insights events. You will be charged separately if you enable Insights for both trails and event data stores. For more information, see Amazon CloudTrail Pricing
Event history
CloudTrail event history provides a viewable, searchable, downloadable, and immutable record of the past 90 days of CloudTrail management events in an Amazon Web Services Region. You can use this history to gain visibility into actions taken in your Amazon account in the Amazon Web Services Management Console, Amazon SDKs, command line tools, and other Amazon services. You can customize your view of event history in the CloudTrail console by selecting which columns are displayed. For more information, see Working with CloudTrail event history.
Trails
A trail is a configuration that enables delivery of CloudTrail events to an S3 bucket, with optional delivery to CloudWatch Logs and Amazon EventBridge. You can use a trail to choose the CloudTrail events you want delivered, encrypt your CloudTrail event log files with an Amazon KMS key, and set up Amazon SNS notifications for log file delivery. For more information about how to create and manage a trail, see Creating a trail for your Amazon Web Services account.
Multi-Region and single-Region trails
You can create both multi-Region and single-Region trails for your Amazon Web Services account.
- Multi-Region trails
-
When you create a multi-Region trail, CloudTrail records events in all Amazon Web Services Regions that are enabled in your Amazon Web Services account and delivers the CloudTrail event log files to an S3 bucket that you specify. As a best practice, we recommend creating a multi-Region trail because it captures activity in all enabled Regions. All trails created using the CloudTrail console are multi-Region trails. You can convert a single-Region trail to a multi-Region trail by using the Amazon CLI. For more information, see Understanding multi-Region trails and opt-in Regions, Creating a trail with the console, and Converting a single-Region trail to a multi-Region trail.
- Single-Region trails
-
When you create a single-Region trail, CloudTrail records the events in that Region only. It then delivers the CloudTrail event log files to an Amazon S3 bucket that you specify. You can only create a single-Region trail by using the Amazon CLI. If you create additional single trails, you can have those trails deliver CloudTrail event log files to the same S3 bucket or to separate buckets. This is the default option when you create a trail using the Amazon CLI or the CloudTrail API. For more information, see Creating, updating, and managing trails with the Amazon CLI.
Note
For both types of trails, you can specify an Amazon S3 bucket from any Region.
A multi-Region trail has the following advantages:
-
The configuration settings for the trail apply consistently across all enabled Amazon Web Services Regions.
-
You receive CloudTrail events from all enabled Amazon Web Services Regions in a single Amazon S3 bucket and, optionally, in a CloudWatch Logs log group.
-
You manage trail configurations for all enabled Amazon Web Services Regions from one location.
Creating a multi-Region trail, has the following effects:
-
CloudTrail delivers log files for account activity from all enabled Amazon Web Services Regions to the single Amazon S3 bucket that you specify, and, optionally, to a CloudWatch Logs log group.
-
If you configured an Amazon SNS topic for the trail, SNS notifications about log file deliveries in all enabled Amazon Web Services Regions are sent to that single SNS topic.
-
You can see the multi-Region trail in all enabled Amazon Web Services Regions, but you can only modify the trail in the home Region where it was created.
Regardless of whether a trail is multi-Region or single-Region, events sent to Amazon EventBridge are received in each Region's event bus, rather than in one single event bus.
Multiple trails per Region
If you have different but related user groups, such as developers, security personnel, and IT auditors, you can create multiple trails per Region. This allows each group to receive its own copy of the log files.
CloudTrail supports five trails per Region. A multi-Region trail counts as one trail per Region.
The following is an example of a Region with five trails:
-
You create two trails in the US West (N. California) Region that apply to this Region only.
-
You create two more multi-Region trails in US West (N. California) Region.
-
You create another multi-Region trail in the Asia Pacific (Sydney) Region. This trail also exists as a trail in the US West (N. California) Region.
You can view a list of trails in an
Amazon Web Services Region in the Trails page of the CloudTrail console. For
more information, see Updating a trail with the CloudTrail console. For CloudTrail pricing, see
Amazon CloudTrail
Pricing
Organization trails
An organization trail is a configuration that enables delivery of CloudTrail events in the management account and all member accounts in an Amazon Organizations organization to the same Amazon S3 bucket, CloudWatch Logs, and Amazon EventBridge. Creating an organization trail helps you define a uniform event logging strategy for your organization.
All organization trails created using the console are multi-Region organization trails that log events from the enabled Amazon Web Services Regions in each member account in the organization. To log events in all Amazon partitions in your organization, create a multi-Region organization trail in each partition. You can create either a single-Region or multi-Region organization trail by using the Amazon CLI. If you create a single-Region trail, you log activity only in the trail's Amazon Web Services Region (also referred to as the Home Region).
Although most Amazon Web Services Regions are enabled by default for your Amazon Web Services account, you must manually enable certain Regions (also referred to as opt-in Regions). For information about which Regions are enabled by default, see Considerations before enabling and disabling Regions in the Amazon Account Management Reference Guide. For the list of Regions CloudTrail supports, see CloudTrail supported Regions.
When you create an organization trail, a copy of the trail with the name that you give it is created in the member accounts that belongs to your organization.
-
If the organization trail is for a single-Region and the trail's home Region is not an opt-in Region, a copy of the trail is created in the organization trail's home Region in each member account.
-
If the organization trail is for a single-Region and the trail's home Region is an opt-in Region, a copy of the trail is created in the organization trail's home Region in the member accounts that have enabled that Region.
-
If the organization trail is multi-Region and the trail's home Region is not an opt-in Region, a copy of the trail is created in each enabled Amazon Web Services Region in each member account. When a member account enables an opt-in Region, a copy of the multi-Region trail is created in the newly opted in Region for the member account after activation of that Region is complete.
-
If the organization trail is multi-Region and the home Region is an opt-in Region, member accounts will not send activity to the organization trail unless they opt into the Amazon Web Services Region where the multi-Region trail was created. For example, if you create a multi-Region trail and choose the Europe (Spain) Region as the home Region for the trail, only member accounts that enabled the Europe (Spain) Region for their account will send their account activity to the organization trail.
Note
CloudTrail creates organization trails in member accounts even if a resource validation fails. Examples of validation failures include:
-
an incorrect Amazon S3 bucket policy
-
an incorrect Amazon SNS topic policy
-
inability to deliver to a CloudWatch Logs log group
-
insufficient permission to encrypt using a KMS key
A member account with CloudTrail permissions can see any validation failures for an organization trail by viewing the trail's details page on the CloudTrail console, or by running the Amazon CLI get-trail-status command.
Users with CloudTrail permissions in member accounts will be able to see organization trails
(including the trail ARN) when they log into the CloudTrail console from their Amazon
accounts, or when they run Amazon CLI commands such as describe-trails (although
member accounts must use the ARN for the organization trail, and not the name, when
using the Amazon CLI). However, users in member accounts will not have sufficient permissions
to delete organization trails, turn logging on or off, change what types of events are
logged, or otherwise alter organization trails in any way. For more information about
Amazon Organizations, see Organizations
Terminology and Concepts. For more information about creating and working
with organization trails, see Creating a trail for an organization.
CloudTrail Insights
CloudTrail Insights help Amazon users identify and respond to unusual volumes of API calls or
errors logged on API calls by continuously analyzing CloudTrail management events. An Insights
event is a record of unusual levels of write management API activity, or
unusual levels of errors returned on management API activity. By default, trails and
event data stores don't log CloudTrail Insights events. In the console, you can choose to log Insights events
when you create or update a trail or event data store. When you use the CloudTrail API, you
can log Insights events by editing the settings of an existing trail or event data store with the
PutInsightSelectors API. Additional charges apply for
logging CloudTrail Insights events. You will be charged separately if you enable Insights for both
trails and event data stores. For more information, see Working with CloudTrail Insights and Amazon CloudTrail Pricing
Tags
A tag is a customer-defined key and optional value that can be assigned to Amazon resources, such as CloudTrail trails, event data stores, and channels, S3 buckets used to store CloudTrail log files, Amazon Organizations organizations and organizational units, and many more. By adding the same tags to trails and to the S3 buckets you use to store log files for trails, you can make it easier to manage, search for, and filter these resources with Amazon Resource Groups. You can implement tagging strategies to help you consistently, effectively, and easily find and manage your resources. For more information, see Best Practices for Tagging Amazon Resources.
Amazon Security Token Service and CloudTrail
Amazon Security Token Service (Amazon STS) is a service that has a global endpoint and also supports
Region-specific endpoints. An endpoint is a URL that is the entry point for web service
requests. For example, https://cloudtrail.us-west-2.amazonaws.com is the
US West (Oregon) regional entry point for the Amazon CloudTrail service. Regional endpoints
help reduce latency in your applications.
When you use an Amazon STS Region-specific endpoint, the trail in that Region delivers only
the Amazon STS events that occur in that Region. For example, if you are using the endpoint
sts.us-west-2.amazonaws.com, the trail in us-west-2 delivers only the
Amazon STS events that originate from us-west-2. For more information about Amazon STS regional
endpoints, see Activating and Deactivating Amazon STS in an Amazon Region in the
IAM User Guide.
For a complete list of Amazon regional endpoints, see Amazon Regions and Endpoints in the Amazon Web Services General Reference. For details about events from the global Amazon STS endpoint, see Global service events.
Global service events
Important
As of November 22, 2021, Amazon CloudTrail makes Amazon CloudFront events available only in the Region where the event was processed, China (Ningxia) Region, cn-northwest-1.
For trails monitoring global service events, be sure to convert single-Region trails in China (Beijing) Region, cn-north-1, to multi-Region trails, to include events from China (Ningxia) Region, cn-northwest-1. For more information about capturing CloudFront events, see Enabling and disabling global service event logging later in this section.
For most services, events are recorded in the Region where the action occurred. For global services such as Amazon Identity and Access Management (IAM), Amazon STS, and Amazon CloudFront, events are delivered to any trail that includes global services.
For most global services, events are logged as occurring in the China (Beijing) Region, but some global service events are logged as occurring in the China (Ningxia) Region.
To avoid receiving duplicate global service events, remember the following:
-
Global service events are delivered by default to trails that are created using the CloudTrail console. Events are delivered to the bucket for the trail.
-
If you have multiple single Region trails, consider configuring your trails so that global service events are delivered in only one of the trails. For more information, see Enabling and disabling global service event logging.
-
When
IncludeGlobalServiceEventsistrue, CloudTrail delivers global service events only to single-Region trails in China (Beijing) Region. For multi-Region trails,IncludeGlobalServiceEventsmust betrue.For more information about changing global service event logging for a trail, see Enabling and disabling global service event logging.
Example:
-
You create a trail in the CloudTrail console. By default, this trail logs global service events.
-
You have multiple single Region trails.
-
You do not need to include global services for the single Region trails. Global service events are delivered for the first trail. For more information, see Creating, updating, and managing trails with the Amazon CLI.
Note
When you create or update a trail with the Amazon CLI, Amazon SDKs, or CloudTrail API, you can specify whether to include or exclude global service events for trails. You cannot configure global service event logging from the CloudTrail console.