Copying an Object to Another Bucket in Object Storage

Copy an object to another bucket in Object Storage.

Caution

Object copy doesn't work if you don't authorize the Object Storage service to copy objects on your behalf. See Service Permissions for more information.

Copy Object Overwrite Rules

Use overwrite rules to control the copying of objects based on their entity tag (ETag) values.

Overwrite destination object: Use this option when you don't want to limit a copy operation by an ETag value. This option is the default. This option can be used for any copy operation, regardless of whether it involves overwriting an existing object.
Do not overwrite any destination object: Use this option to prevent the overwriting an existing copy of an object in the destination location, regardless of the destination object's ETag value.
Overwrite destination object only if it matches the specified ETag: Use this option to prevent the accidental overwriting of an object in the destination location that doesn't have the specified ETag. When you use this option, the copy operation only succeeds if the ETag you supply when starting the copy request matches the ETag of the destination object.
Copy object only if the source matches the specified ETag: Use this option if you want the copy operation successful only if the ETag you supply when starting the copy request matches the ETag of the source object. For objects that are intentionally updated and overwritten as part of data management activity, this option ensures that only the specified version of the object (as indicated by the ETag) is allowed to be copied. If the object's ETag value changes after the copy work request is created, but before the copy operation is run, the copy operation doesn't complete.

Caution

If you overwrite an object, the operation can't be undone.

Scope and Constraints

Objects can't be copied directly from Archive Storage. To copy objects that are in Archive Storage, you must first restore the object to the Standard Object Storage tier. Objects can be copied directly to Archive tier buckets from the Standard or Infrequent Access tiers. When you copy objects into an Archive Storage bucket, the copy of the object is immediately archived.
Specify an existing target bucket for the copy request. The copy operation doesn't automatically create buckets.
When an object is copied, the destination object receives a new ETag value.
If you rename, overwrite, or delete a source object during a copy operation, the copy operation fails and the destination object is not created or overwritten.
Bulk copying isn't supported. Identify a single object in the copy request.

Service Permissions

Because Object Storage is a regional service, you must authorize the Object Storage service for each region carrying out copy operations on your behalf. For example, you might authorize the Object Storage service in region US East (Ashburn) to manage objects on your behalf. After you authorize the Object Storage service, you can copy an object stored in a US East (Ashburn) bucket to a bucket in another region.

To determine the region identifier value of an Oracle Cloud Infrastructure region, see Regions and Availability Domains.

For administrators:

To enable object copy, you must authorize the service to manage objects on your behalf:

You can create a policy that authorizes the service in the specified region to manage Object Storage namespaces, buckets, and their associated objects in all compartments in the tenancy:
```
Allow service objectstorage-<region_identifier> to manage object-family in tenancy
```

Instead of using the policy verb manage, you can create a policy that reduces the scope of access by instead using one of the following statements:

Allow service objectstorage-<region_identifier> to manage object-family in tenancy where any {request.permission='OBJECT_READ', request.permission='OBJECT_INSPECT', request.permission='OBJECT_CREATE', request.permission='OBJECT_OVERWRITE', request.permission='OBJECT_DELETE'}

Allow service objectstorage-<region_identifier> to manage object-family in compartment <compartment_name> where any {request.permission='OBJECT_READ', request.permission='OBJECT_INSPECT', request.permission='OBJECT_CREATE', request.permission='OBJECT_OVERWRITE', request.permission='OBJECT_DELETE'}