Configuring Amazon S3 Inventory

Amazon S3 Inventory provides a flat file list of your objects and metadata, on a schedule that you define. You can use S3 Inventory as a scheduled alternative to the Amazon S3 synchronous List API operation. S3 Inventory provides comma-separated values (CSV), Apache optimized row columnar (ORC), or Apache Parquet (Parquet) output files that list your objects and their corresponding metadata. You can configure S3 Inventory to create inventory lists on a daily or weekly basis for an S3 bucket or for objects that share a prefix (objects that have names that begin with the same string). For more information, see Amazon S3 Inventory.

This section describes how to configure an inventory, including details about the inventory source and destination buckets.

Overview

Amazon S3 Inventory helps you manage your storage by creating lists of the objects in an S3 bucket on a defined schedule. You can configure multiple inventory lists for a bucket. The inventory lists are published to CSV, ORC, or Parquet files in a destination bucket.

The easiest way to set up an inventory is by using the AWS Management Console, but you can also use the REST API, AWS Command Line Interface (AWS CLI), or AWS SDKs. The console performs the first step of the following procedure for you: adding a bucket policy to the destination bucket.

To set up Amazon S3 Inventory for an S3 bucket

1. Add a bucket policy for the destination bucket.

   You must create a bucket policy on the destination bucket to grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see Grant permissions for S3 Inventory and S3 analytics.

2. Configure an inventory to list the objects in a source bucket and publish the list to a destination bucket.

   When you configure an inventory list for a source bucket, you specify the destination bucket where you want the list to be stored, and whether you want to generate the list daily or weekly. You can also configure what object metadata to include and whether to list all object versions or only current versions.

   You can specify that the inventory list file be encrypted by using server-side encryption with Amazon S3 managed keys (SSE-S3) or with AWS Key Management Service (AWS KMS) customer managed keys (SSE-KMS).

   Note

   The AWS managed key (aws/s3) is not supported for SSE-KMS encryption with S3 Inventory.

   For more information about SSE-S3 and SSE-KMS, see Protecting data using server-side encryption. If you plan to use SSE-KMS encryption, see Step 3.

   • For information about how to use the console to configure an inventory list, see Configuring Amazon S3 Inventory.

   • To use the Amazon S3 API to configure an inventory list, use the PUT Bucket inventory configuration REST API or the equivalent from the AWS CLI or AWS SDKs.

3. To encrypt the inventory list file with SSE-KMS, grant Amazon S3 permission to use the customer managed key.

   You can configure encryption for the inventory list file by using the AWS Management Console, REST API, AWS CLI, or AWS SDKs. Whichever way you choose, you must grant Amazon S3 permission to use the customer managed key to encrypt the inventory file. You grant Amazon S3 permission by modifying the key policy for the customer managed key that you want to use to encrypt the inventory file. For more information, see the next section, Granting Amazon S3 permission to use your customer managed key for encryption.

4. To configure inventory, see Configuring inventory by using the S3 console.

   If you use encryption for cross-account operations of Amazon S3 inventory configuration in the destination bucket, you should use fully qualified KMS key ARN. For more information, see Using SSE-KMS encryption for cross-account operations and ServerSideEncryptionByDefault.

Creating a destination bucket policy

If you create the inventory configuration through the S3 console, Amazon S3 automatically creates a bucket policy on the destination bucket that grants Amazon S3 write permission. If you create the inventory configuration through the AWS CLI, SDKs, or the REST API, you must manually add a bucket policy on the destination bucket. For more information, see Grant permissions for S3 Inventory and S3 analytics. The Amazon S3 Inventory destination bucket policy allows Amazon S3 to write data for the inventory reports to the bucket.

If an error occurs when you try to create the bucket policy, you are given instructions on how to fix it. For example, if you choose a destination bucket in another AWS account and don't have permissions to read and write to the bucket policy, you see an error message.

In this case, the destination bucket owner must add the displayed bucket policy to the destination bucket. If the policy is not added to the destination bucket, you won't get an inventory report because Amazon S3 doesn't have permission to write to the destination bucket. If the source bucket is owned by a different account than that of the current user, the correct account ID of the source bucket owner must be substituted in the policy.

Granting Amazon S3 permission to use your customer managed key for encryption

To grant Amazon S3 permission to use your AWS Key Management Service (AWS KMS) customer managed key for server-side encryption, you must use a key policy. To update your key policy so that you can use your customer managed key, use the following procedure.

To grant permissions to encrypt using your customer managed key

1. Using the AWS account that owns the customer managed key, sign into the AWS Management Console.

2. Open the AWS KMS console at https://console.aws.amazon.com/kms.

3. To change the AWS Region, use the Region selector in the upper-right corner of the page.

4. In the left navigation pane, choose Customer managed keys.

5. Under Customer managed keys, choose the customer managed key that you want to use to encrypt your inventory files.

6. Under Key policy, choose Switch to policy view.

7. To update the key policy, choose Edit.

8. Under Edit key policy, add the following key policy to the existing key policy.

   {
       "Sid": "Allow Amazon S3 use of the customer managed key",
       "Effect": "Allow",
       "Principal": {
           "Service": "s3.amazonaws.com"
       },
       "Action": [
           "kms:GenerateDataKey"
       ],
       "Resource": "*",
       "Condition":{
         "StringEquals":{
            "aws:SourceAccount":"source-account-id"
        },
         "ArnLike":{
           "aws:SourceARN": "arn:aws:s3:::source-bucket-name"
        }
      }
   }

9. Choose Save changes.

For more information about creating customer managed keys and using key policies, see the following links in the AWS Key Management Service Developer Guide:

• Getting Started

• Using Key Policies in AWS KMS

Configuring inventory by using the S3 console

Use these instructions to configure inventory by using the S3 console.

Note

It might take up to 48 hours to deliver the first report.

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

2. In the left navigation pane, choose Buckets.

3. In the Buckets list, choose the name of the bucket for which you want to configure Amazon S3 Inventory.

4. Choose Management.

5. Under Inventory configurations, choose Create inventory configuration.

6. For Inventory configuration name, enter a name.

7. Set the Inventory scope:

   • Enter an optional prefix.

   • Choose object versions: Current versions only or Include all versions.

8. Under Report details, choose the location of the AWS account that you want to save the reports to: This account or A different account.

9. Under Destination, choose the destination bucket where you want reports to be saved.

   The destination bucket must be in the same AWS Region as the bucket for which you are setting up the inventory. The destination bucket can be in a different AWS account. Under the Destination bucket field, you see the Destination bucket permission that is added to the destination bucket policy to allow Amazon S3 to place data in that bucket. For more information, see Creating a destination bucket policy.

10. Under Frequency, choose how often the report will be generated: Daily or Weekly.

11. Choose the Output format for the report:

    • CSV

    • Apache ORC

    • Apache Parquet

12. Under Status, choose Enable or Disable.

13. To configure server-side encryption, under Inventory report encryption, follow these steps:

    1. Under Server-side encryption, choose Do not specify an encryption key or Specify an encryption key to encrypt data.

       • To keep the bucket settings for default server-side encryption of objects when storing them in Amazon S3, choose Do not specify an encryption key. As long as the bucket destination has S3 Bucket Keys enabled, the copy operation applies an S3 Bucket Key at the destination bucket.

         Note

         If the bucket policy for the specified destination requires objects to be encrypted before storing them in Amazon S3, you must specify an encryption key. Otherwise, copying objects to the destination will fail.

       • To encrypt objects before storing them in Amazon S3, choose Specify an encryption key.

    2. If you chose Specify an encryption key, under Encryption key type, you need to choose Amazon S3 managed key (SSE-S3) or AWS Key Management Service key (SSE-KMS).

       SSE-S3 uses one of the strongest block ciphers—256-bit Advanced Encryption Standard (AES-256) to encrypt each object. SSE-KMS provides you with more control over your key. For more information about SSE-S3, see Protecting data using server-side encryption with Amazon S3 managed encryption keys (SSE-S3). For more information about SSE-KMS, see Protecting data using server-side encryption with AWS Key Management Service keys (SSE-KMS).

       Note

       To encrypt the inventory list file with SSE-KMS, you must grant Amazon S3 permission to use the customer managed key. For instructions, see Grant Amazon S3 Permission to Encrypt Using Your KMS Keys.

    3. If you chose AWS Key Management Service key (SSE-KMS), under AWS KMS key, you can specify your AWS KMS key through one of the following options.

       • To choose from a list of available KMS keys, choose Choose from your AWS KMS keys, and choose a symmetric encryption KMS key in the same Region as your bucket from the list of available keys.

         Note

         Both the AWS managed key (aws/s3) and your customer managed keys appear in the list. However, the AWS managed key (aws/s3) is not supported for SSE-KMS encryption with S3 Inventory.

       • To enter the KMS key ARN, choose Enter AWS KMS key ARN, and enter your KMS key ARN in the filed that appears.

       • To create a new customer managed key in the AWS KMS console, choose Create a KMS key.

14. For Additional fields, select one or more of the following to add to the inventory report:

    • Size – The object size in bytes, not including the size of incomplete multipart uploads, object metadata, and delete markers.

    • Last modified date – The object creation date or the last modified date, whichever is the latest.

    • Storage class – The storage class used for storing the object.

    • ETag – The entity tag (ETag) is a hash of the object. The ETag reflects changes only to the contents of an object, and not its metadata. The ETag might or might not be an MD5 digest of the object data. Whether it is depends on how the object was created and how it is encrypted. For more information, see Object in the Amazon Simple Storage Service API Reference.

    • Multipart upload – Specifies that the object was uploaded as a multipart upload. For more information, see Uploading and copying objects using multipart upload.

    • Replication status – The replication status of the object. For more information, see Using the S3 console.

    • Encryption status – The server-side encryption used to encrypt the object. For more information, see Protecting data using server-side encryption.

    • S3 Object Lock configurations – The Object Lock status of the object, including the following settings:

      • Retention mode – The level of protection applied to the object, either Governance or Compliance.

      • Retain until date – The date until which the locked object cannot be deleted.

      • Legal hold status – The legal hold status of the locked object.

      For information about S3 Object Lock, see How S3 Object Lock works.

    • Intelligent-Tiering access tier – Indicates the access tier of the object if it was stored in S3 Intelligent-Tiering. For more information, see Storage class for automatically optimizing data with changing or unknown access patterns.

    • S3 Bucket Key status – Indicates whether a bucket-level key generated by AWS KMS applies to the object. For more information, see Reducing the cost of SSE-KMS with Amazon S3 Bucket Keys.

    • Checksum algorithm – Indicates the algorithm that is used to create the checksum for the object.

    For more information about the contents of an inventory report, see Amazon S3 Inventory list.

15. Choose Create.

When an inventory list is published, you can query the inventory list file with Amazon S3 Select. For more information about how to locate your inventory list and query the inventory list file with Amazon S3 Select, see Locating your inventory list.