Object Storage Service:Why have inventory lists not been generated for an extended period of time?

Inventory lists cannot be written to the specified bucket because a DENY policy is configured for the bucket

For example, if the destination bucket that stores inventory lists is configured with a policy that allows only specific IP addresses to access inventory lists, the IP addresses used by the inventory daemon to write inventory lists to the destination bucket are not included in the allowed IP addresses.

Solutions:

• Specify another bucket to store the inventory lists generated for the source bucket. Make sure that the bucket is located in the same region as the source bucket and no DENY policies are configured for the bucket.

• Create a bucket in the same region as the source bucket to store the inventory lists generated for the source bucket.

The specified prefix in the inventory configured for the source bucket is invalid

Solution: Check whether the specified prefix in the inventory configured for the source bucket is valid based on the following rules:

• To scan all objects in the bucket, leave the Object Prefix parameter empty.

• To scan all objects in a directory of the bucket, set the Object Prefix parameter to the full path of the directory that does not include the bucket name.

  For example, to scan all objects in the exampledir1 directory of the examplebucket bucket, set the Object Prefix parameter to exampledir1/. To scan all objects in the exampledir1/exampledir2 directory of the examplebucket bucket, set the Object Prefix parameter to exampledir1/exampledir2/.

The specified prefix in the inventory configured for the source bucket does not match any objects in the bucket

If the specified prefix in the inventory configured for the source bucket does not match any objects in the bucket, no inventory lists are generated.

Solution: Make sure that the specified prefix in the inventory configured for the source bucket matches one or more objects in the bucket.

You view inventory lists in a wrong path

Solution: Check whether you go to a correct path to view inventory lists.

The following structure shows the directories in which generated inventory lists are stored.

dest_bucket
 └──destination-prefix/
     └──src_bucket/
         └──inventory_id/
             ├──YYYY-MM-DDTHH-MMZ/
             │   ├──manifest.json
             │   └──manifest.checksum
             └──data/
                 └──745a29e3-bfaa-490d-9109-47086afcc8f2.csv.gz

You can view the generated inventory lists in the directory specified by the Inventory Path parameter.

• If you do not specify the Inventory Path parameter, view the manifest objects in the src_bucket/inventory_id path and the generated inventory lists in the src_bucket/data path. src_bucket indicates the name of the source bucket and inventory_id indicates the ID of the inventory.

• If you set the Inventory Path parameter to exampledir1, view the manifest objects in the exampledir1/src_bucket/inventory_id path of the bucket in which the inventory lists are stored and the generated inventory lists in the exampledir1/src_bucket/data path.

• If you set the Inventory Path parameter to exampledir1/exampledir2, view the manifest objects in the exampledir1/exampledir2/src_bucket/inventory_id path of the bucket in which the inventory lists are stored and the generated inventory lists in the exampledir1/exampledir2/src_bucket/data path.

The RAM role does not have the permissions to export inventory lists

If you modify the permissions of the RAM role that is associated with an inventory, inventory lists may fail to be exported due to insufficient permissions of the RAM role.

Solution: Grant the required permissions to the RAM role. For more information, see Required permissions.