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.
Adequate permissions to manage objects in CoreWeave AI Object Storage (for example, s3:PutObject and s3:DeleteObject). See Object Storage S3 Permissions for more information.
Alternatively, configure your CoreWeave credentials to work with the AWS CLI.Using a separate profile for CoreWeave AI Object Storage is recommended to avoid conflicts with your other AWS profiles and S3-compatible services; if you do not set up this configuration, you may encounter errors when using AI Object Storage.
Configure CoreWeave credentials
Create a new credentials file and profile in your CoreWeave configuration directory.
Set the default endpoint URL to the appropriate endpoint for your use case:
The primary endpoint, https://cwobject.com, for use when running outside of a CoreWeave cluster.
The LOTA endpoint, http://cwlota.com, for use when running inside a CoreWeave cluster. The LOTA endpoint routes to the LOTA path for best performance.
Set the primary endpoint for local development
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set endpoint_url https://cwobject.com --profile cw
Set the S3 addressing_style to virtual:
Set virtual addressing style
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set s3.addressing_style virtual --profile cw
Use the following Python script to upload a file to your S3 bucket. Replace the following placeholders with the appropriate values for your request:
[BUCKET-NAME]: The name of the bucket to upload the file to.
[LOCAL-FILE-PATH]: The path to the local file to upload.
[OBJECT-NAME]: The name of the object to upload. This is optional. If you don’t set a value, it will use the same string as your [LOCAL-FILE-PATH].
Upload a file to a bucket
import osimport boto3from botocore.client import Configboto_config = Config( region_name='US-EAST-04A', s3={'addressing_style': 'virtual'})# Create the S3 clients3 = boto3.client( 's3', endpoint_url='https://cwobject.com', aws_access_key_id=os.environ['ACCESS_KEY_ID'], aws_secret_access_key=os.environ['SECRET_ACCESS_KEY'], config=boto_config)# Define your bucket name and the file pathbucket_name = '[BUCKET-NAME]'file_name = '[LOCAL-FILE-PATH]'object_name = '[OBJECT-NAME]' # This is optional. If you don't set a value, it will use the same string as your file_name.# Upload files3.upload_file(file_name, bucket_name, object_name)print(f'File {file_name} uploaded to {bucket_name}/{object_name}')
If this succeeds, a confirmation message is printed.
Example output
File /path/to/my-file uploaded to my-bucket-name/my-important-file
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.
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.
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.
AWS CLI
s3cmd
Boto3
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.
Alternatively, configure your CoreWeave credentials to work with the AWS CLI.Using a separate profile for CoreWeave AI Object Storage is recommended to avoid conflicts with your other AWS profiles and S3-compatible services; if you do not set up this configuration, you may encounter errors when using AI Object Storage.
Configure CoreWeave credentials
Create a new credentials file and profile in your CoreWeave configuration directory.
Alternatively, configure your CoreWeave credentials to work with the AWS CLI.Using a separate profile for CoreWeave AI Object Storage is recommended to avoid conflicts with your other AWS profiles and S3-compatible services; if you do not set up this configuration, you may encounter errors when using AI Object Storage.
Configure CoreWeave credentials
Create a new credentials file and profile in your CoreWeave configuration directory.
Set the default endpoint URL to the appropriate endpoint for your use case:
The primary endpoint, https://cwobject.com, for use when running outside of a CoreWeave cluster.
The LOTA endpoint, http://cwlota.com, for use when running inside a CoreWeave cluster. The LOTA endpoint routes to the LOTA path for best performance.
Set the primary endpoint for local development
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set endpoint_url https://cwobject.com --profile cw
Set the S3 addressing_style to virtual:
Set virtual addressing style
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set s3.addressing_style virtual --profile cw
Use the following script to delete an object from a bucket. Replace [BUCKET-NAME] with the name of the bucket and [OBJECT-NAME] with the key of the object to delete.
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.
To rename an object, use the mv command with s3cmd.
Copy and delete operationThe s3cmd mv command performs a copy and delete operation instead of an atomic rename operation. For atomic rename operations, use the AWS CLI or Boto3 with the RenameObject API.
To prevent accidental overwrites when uploading objects, use the If-None-Match: * header with PutObject. See Conditional writes for details.
Replace the following placeholders with the appropriate values for your request:
[BUCKET-NAME]: The name of the bucket containing the source object.
[SOURCE-OBJECT-NAME]: The name of the source object to rename.
[DESTINATION-OBJECT-NAME]: The new name for the object.
Alternatively, configure your CoreWeave credentials to work with the AWS CLI.Using a separate profile for CoreWeave AI Object Storage is recommended to avoid conflicts with your other AWS profiles and S3-compatible services; if you do not set up this configuration, you may encounter errors when using AI Object Storage.
Configure CoreWeave credentials
Create a new credentials file and profile in your CoreWeave configuration directory.
Set the default endpoint URL to the appropriate endpoint for your use case:
The primary endpoint, https://cwobject.com, for use when running outside of a CoreWeave cluster.
The LOTA endpoint, http://cwlota.com, for use when running inside a CoreWeave cluster. The LOTA endpoint routes to the LOTA path for best performance.
Set the primary endpoint for local development
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set endpoint_url https://cwobject.com --profile cw
Set the S3 addressing_style to virtual:
Set virtual addressing style
AWS_CONFIG_FILE=~/.coreweave/cw.config aws configure set s3.addressing_style virtual --profile cw
Use the rename_object method to rename an object. Replace [BUCKET-NAME], [SOURCE-OBJECT-NAME], and [DESTINATION-OBJECT-NAME] with the appropriate values for your request.