DreamObjects buckets cannot be renamed once created. However, you are able to use the panel's migration tool to copy a bucket to a new bucket. In this way, you can rename the bucket by creating a new one with the same content.

1. Navigate to the DreamObjects page in your DreamHost panel.

2. Click the Migrations Tab.

3. Click the + Create Migration button.

4. Enter your DreamHost bucket credentials:
   • Type — Set to S3
   • Host — objects-us-east-1.dream.io
   • Access Key and Secret Key — These are your DreamObject's keys

5. Click the Choose Destination & Buckets button.

6. Enter a name for your migration. The name is for your use only.
7. If you have more than one DreamObjects user, choose the one you'd like to create the new bucket under.
8. By default, all of the buckets are highlighted and selected. Click a bucket to un-select it. Make sure the only bucket selected is the one you want to copy.
9. Click the Start Migration button.
   

   

   Since you're migrating to a new DreamObjects bucket, an error displays notifying you that the bucket name already exists.

   Name this bucket anything you like. This will be the renamed bucket once the migration completes.

10. Click Resolve Conflicts to begin the migration. The main page of the Migrations tab opens and your active migration displays in the Active Migrations section:

After running the migration tool, your storage will be temporarily increased for that month. This is because the data is copied between buckets, not moved.

If the naming conventions used for your S3 buckets are not compatible with the naming conventions for DreamObjects, a 'Bucket Name Conflicts' screen appears. 

Click the View Details button to view information about the migration. For example, you can view the current status, how long it's been processing, and its current state.

Migrated and migrating Buckets reflect one of the following five states:

• Queued — the Bucket and all of its objects have been successfully copied to DreamObjects.
• In Progress — the Bucket is in the process of being copied to DreamObjects and has not yet completed the action.
• Stopped — the migration process for the Bucket has either failed, or was manually stopped by the user requesting the migration.
• Partial — some Buckets and their contents have been migrated, and some have not. This may have been caused by a failure during Object Synchronization. Such failures can be caused by deleting your S3 Buckets, or by revoking your S3 credentials before the migration is complete.
• Complete — the Bucket and all of its objects have been successfully copied to DreamObjects.

Did this article answer your questions?