Skip to main content
Inventory Reporting provides a scheduled, point-in-time listing of all objects in a bucket so you can audit, analyze, and manage bucket contents at scale without enumerating objects yourself. The output includes lists of objects with metadata for each object. You specify the source bucket whose objects to inventory and a destination bucket for the output. You can schedule the inventory listing to run daily or weekly, and you can configure the output to meet your analytics needs. Inventory Reporting supports storage, data platform, security, and compliance teams that need object-level inventory for governance, analytics, lifecycle, and cost optimization. This page describes the available configuration options, the structure of the resulting reports, and the limitations to consider before you enable Inventory Reporting on a bucket.

Configuration options

For your inventory reporting configuration, you can specify the following options:
  • Schedule: How often you want the inventory report to run, either daily or weekly.
  • Source bucket: Choose the bucket that you want to inventory. You can choose to list all of the objects in the bucket or only objects with a specified prefix. If you don’t specify a prefix, the report inventories all objects.
  • Destination bucket: Choose the bucket where you want to write the inventory reports, and optionally specify a prefix (subdirectory) to organize the reports.
  • Output formats:
  • Optional fields: Choose the optional fields that you want to include in the inventory report. See the detailed field reference for all available configuration options.
To configure and enable inventory reports, see Configure Inventory Reporting for CoreWeave AI Object Storage.

Output fields

When you configure your inventory report, you can choose whether to include or exclude certain fields from the output. The report always includes some fields, and includes optional fields only if you specify them in the OptionalFields configuration. The following fields are available:
Field nameDescriptionWhen included in report
BucketNameName of the bucket that contains the objectAlways
ObjectKeyUnique key (path/name) that identifies the object within the bucketAlways
VersionIDVersion identifier for the object, if versioning is enabledAlways included if IncludedObjectVersions is set to All
IsLatestIndicates whether this is the latest version of the objectAlways included if IncludedObjectVersions is set to All
IsDeleteMarkerShows whether this entry is a delete markerAlways included if IncludedObjectVersions is set to All
SizeSize of the object in bytesOptional
LastModifiedDateDate and time when the object was last modifiedOptional
IsMultipartUploadedIndicates whether the object was uploaded as a multipart uploadOptional
EncryptionStatusEncryption status or method used on the objectOptional
StorageClassStorage class assigned to the object (see Usage-Based Billing)Optional
ChecksumAlgorithmAlgorithm used to compute the checksum of the objectOptional
LastAccessedDateTimestamp of the last access (read) of the object, in RFC 3339 format, expressed in UTC. Example: 2026-05-20T12:00:00ZOptional
ETagETag of the object. You can use ETags with conditional writes to perform atomic updates.Optional

Notes and limitations

Before you enable Inventory Reporting, review the following considerations:
  • No notifications: You don’t receive notifications when the inventory listing completes, so you must check the destination bucket to see whether the inventory reports have been written.
  • Pricing: Inventory Reporting incurs charges for storage of the inventory reports in your destination bucket. Use LastAccessedDate to derive the access tier (Hot, Warm, or Cold) of the objects.
  • Consistency: Inventory reports provide eventual consistency. A specific report might not reflect object changes during the scan, but changes converge across successive runs. Reports aren’t transactional snapshots.
  • Not for billing: Inventory reports are for governance and analytics, not billing reconciliation. Inventory reports don’t match the audit logs or the billing data exactly.
  • Configuration limit: You can set up to 1,000 inventory configurations per bucket.
  • Encryption: SSE-C for report files is not supported.

Inventory report contents

After an inventory run completes, the destination bucket contains the following report artifacts:
  • A manifest file (manifest.json) that describes the report and lists all inventory data files.
  • One or more inventory data files that contain the object listings.

Manifest file

The manifest file (manifest.json) describes the inventory report, and it’s written to the root of the subdirectory specified in the inventory configuration. The manifest file is a JSON object with the following fields:
FieldDescription
fileSchemaSpecifies which fields are included in the report
sourceBucketName of the source bucket
destinationBucketName of the destination bucket
versionVersion of the inventory report
creationTimestampCreation date (start of inventory report generation)
filesList of the inventory files
files.keyKey that identifies the file path, always included in the report
files.sizeSize of the inventory file in bytes
files.md5checksumMD5 checksum of the inventory file
The manifest file looks similar to this:
manifest.json
{
  "sourceBucket": "my-bucket",
  "destinationBucket": "arn:aws:s3:::my-destination-bucket",
  "version": "2016-11-30",
  "creationTimestamp": "1761777847000",
  "fileFormat": "JSON",
  "fileSchema": "Bucket,Key,VersionId,IsLatest,IsDeleteMarker,Size,StorageClass,LastAccessedDate",
  "files": [
    {
      "key": "inventory-reports/my-bucket/my-inventory-config/data/2025-10-29_2ead449d-ef16-5bb2-beb9-f3421d5c8af1.json.gz",
      "size": 183,
      "md5checksum": "6f7cbc70f083910058ac7d57615a304b"
    }
    ...
  ]
}

Support

If you need help with Inventory Reporting, contact CoreWeave support or email support@coreweave.com.
Last modified on June 10, 2026