Create an event data store - AWS CloudTrail

Create an event data store

To get started with CloudTrail Lake, create an event data store. You can keep the event data in an event data store for up to seven years, or 2555 days. By default, event data is retained for 2555 days, and termination protection is enabled for an event data store.

  1. Choose Lake in the left navigation pane of the CloudTrail console.

  2. On the Lake page, open the Event data stores tab.

  3. Choose Create event data store.

  4. On the Configure event data store page, in General details, enter a name for the event data store. A name is required.

  5. Specify a retention period for the event data store in days. Valid values are integers from 7 to 2555 (seven years). The event data store retains event data for the specified number of days.

  6. CloudTrail stores the event data store resource in the region in which you create it, but by default, the events collected in the data store are from all regions in your account. Optionally, you can select Include only the current region in my event data store to include only events that are logged in the current region. If you do not choose this option, your event data store includes events from all regions. Choose Next.

  7. To have your event data store collect events from all accounts in an AWS Organizations organization, select Enable for all accounts in my organization. You must be signed in to the management account for the organization to create an event data store that collects events for an organization.

  8. (Optional) In the Tags area, you can add up to 50 tag key and value pairs to help you identify, sort, and control access to your event data store. For more information about how to use IAM policies to authorize access to an event data store based on tags, see Examples: Denying access to create or delete event data stores based on tags. For more information about how you can use tags in AWS, see Tagging AWS resources in the AWS General Reference.

  9. On the Choose events page, choose at least one event type. By default, Management events is selected. You can add both management and data events to your event data store. For more information about management events, see Logging management events for trails. For more information about data events, see Logging data events for trails.

  10. (Optional) Choose Copy trail events if you want to copy events from an existing trail to run queries on past events. For more information about considerations for copying trail events, see Considerations.

    1. Choose the trail that you want to copy. If the source S3 bucket for the trail uses a KMS key for data encryption, verify that the KMS key policy grants CloudTrail access to decrypt the data. If your source S3 bucket uses multiple KMS keys, you must update each key's policy to grant CloudTrail access. For more information about updating the KMS key policy, see KMS key policy for decrypting data in the source S3 bucket.

    2. (Optional) Choose a time range for copying the events. You can choose a Relative range or an Absolute range. To avoid duplicating events between the source trail and destination event data store, choose a time range that is earlier than the creation of the event data store.

      • If you choose Relative range, you can choose to copy events logged in the last 5 minutes, 30 minutes, 1 hour, 6 hours, or a custom range. CloudTrail copies the events logged within the chosen time period.

      • If you choose Absolute range, you can choose a specific start and end date. CloudTrail copies the events that occurred between the chosen start and end dates.

    3. For Permissions, choose from the following IAM role options. If you choose an existing IAM role, verify that the IAM role policy provides the necessary permissions. For more information about updating the IAM role permissions, see IAM permissions for copying trail events.

      • Choose Create a new role (recommended) to create a new IAM role. For Enter IAM role name, enter a name for the role. CloudTrail automatically creates the necessary permissions for this new role.

      • Choose Use a custom IAM role to use a custom IAM role that is not listed. For Enter IAM role ARN, enter the IAM ARN.

      • Choose Use an existing role to choose an existing IAM role from the drop-down list.

  11. If your event data store includes management events, choose Read, Write, or both. At least one is required. For more information about Read and Write management events, see Logging management events for trails.

  12. You can choose to exclude AWS Key Management Service or Amazon RDS Data API events from your event data store. For more information about these options, see Logging management events for trails.

  13. To include data events in your event data store, do the following.

    1. Choose a data event type. This is the AWS service and resource on which data events are logged.

    2. In Log selector template, choose a template. You can choose to log all data events, readOnly events, writeOnly events, or Custom to build a custom log selector.

    3. If you choose Custom, optionally enter a name for your custom log selector template.

    4. In Advanced event selectors, build expressions by choosing values for Field, Operator, and Value. Advanced event selectors for an event data store work the same as advanced event selectors that you apply to a trail. For more information about how to build advanced event selectors, see Logging data events with advanced event selectors.

      The following example uses a Custom log selector template to choose only event names from S3 objects that start with Put, such as PutObject. Because the advanced event selector does not include or exclude any other event types or resource ARNs, all S3 data events, both read and write, that are logged to the US East (N. Virginia) Region, and that have event names starting with Put, are stored in the event data store.

                                Lake data events, advanced event selectors

      To exclude or include data events with advanced event selectors by using an S3 bucket ARN, always use the Starts with operator.

    5. Optionally, expand JSON view to see your advanced event selectors as a JSON block. Choose Next.

  14. On the Review and create page, review your choices. Choose Edit to make changes to a section. When you're ready to create the event data store, choose Create event data store.

  15. The new event data store is visible in the Event data stores table on the Lake page.

    From this point forward, the event data store captures events that match its advanced event selectors. Events that occurred before you created the event data store are not in the event data store unless you chose to copy existing trail events.