Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt

Use this file to discover all available pages before exploring further.

This guide explains how to manage objects stored in CoreWeave AI Object Storage buckets using S3-compatible tools, including the AWS CLI, s3cmd, Boto3, and s5cmd. For high-performance or bulk transfers, see Migrate data to AI Object Storage for s5cmd (use the CoreWeave fork for AI Object Storage). Alternatively, you can use Cyberduck to manage your buckets and objects in a graphical interface. Currently, the Cloud Console does not support managing objects. To manage versioned buckets with rclone, see Versioned buckets.

Prerequisites

This guide presumes you have the following:
Before running the commands in this guide, make sure your S3 client is configured with:
  • Virtual-hosted addressing enabled (s3.addressing_style = virtual). Path-style addressing is not supported. See Set Endpoints.
  • The correct endpoint URL:
    • http://cwlota.com when running inside a CoreWeave cluster (LOTA, best performance)
    • https://cwobject.com when running outside a CoreWeave cluster

Add objects

Ensure you have the AWS CLI installed and configured.Use the s3 cp command to copy a file into a bucket addressed using the s3:// scheme.
Example command
aws s3 cp [LOCAL-FILE-PATH] s3://[BUCKET-NAME]
Example output
upload: ./my-important-file.txt to s3://my-bucket-name/my-important-file.txt

Verify object integrity

CoreWeave AI Object Storage supports checksum algorithms for verifying object integrity on upload and download. See Checksum algorithms for the full list of supported algorithms.

Exceeding quota limits

If you try to upload an object to a bucket in an Availability Zone where capacity quota limits have been reached, you will receive an error message: <Message>The account is write suspended.</Message> To resolve this, you can request a quota increase.

List buckets and their contents

You can list buckets and their contents using S3-compatible tools such as the AWS CLI, s3cmd, or Boto3. If you’re working with versioned buckets, you can use rclone to list buckets and their contents, including delete markers.
If you want to see all of your available buckets, use the ls command:
aws s3 ls
To list all the objects currently in a bucket, use the ls command to target a bucket path.
aws s3 ls s3://[BUCKET-NAME]
The terminal or command prompt will return a YAML file for your selected bucket, listing all objects within it, their sizes, and their last modified dates.
Example file listing output
2024-10-14 15:35:10 123456 my-first-file.txt
2024-10-14 16:45:22 234567 another-file-of-mine.txt

Delete an object from a bucket

To delete specific objects from a bucket, use the rm command with the AWS CLI.
aws s3 rm s3://[BUCKET-NAME]/[OBJECT-NAME]
When this succeeds, a confirmation message like this one is printed:
Example output
delete: s3://my-bucket-name/my-important-file.txt
For more information about accessing and interacting with the contents of your buckets, see the official Amazon documentation for s3 buckets.

Rename an object

Make sure you have the following to rename an object:
  • s3:PutObject and s3:DeleteObject permissions.
  • A bucket that does not have versioning enabled, either currently or in the past.
  • A request scoped to renaming a single object within the same bucket. The source and destination keys must be in the same bucket.
See Rename Objects for more information.
To rename an object, use the aws s3api rename-object command with the AWS CLI.Replace the following placeholders with the appropriate values for your request:
  • [BUCKET-NAME]: The name of the bucket containing the object.
  • [SOURCE-OBJECT-NAME]: The current name of the object.
  • [DESTINATION-OBJECT-NAME]: The new name for the object.
Rename object
aws s3api rename-object \
  --bucket [BUCKET-NAME] \
  --key [DESTINATION-OBJECT-NAME] \
  --rename-source /[BUCKET-NAME]/[SOURCE-OBJECT-NAME]
When this succeeds, a confirmation message is printed:
Example output
rename: s3://my-bucket-name/my-important-file.txt -> s3://my-bucket-name/my-new-file.txt
Last modified on April 30, 2026