You can upload objects up to 5 GB in size by using the Object Storage Service (OSS) console.
Prerequisites
A bucket is created. For more information, see Create buckets.
Procedure
Log on to the OSS console.
In the left-side navigation pane, click Buckets. On the Buckets page, find and click the desired bucket.
In the left-side navigation tree, choose .
On the Objects page, click Upload Object.
On the upload page, configure the parameters described in the following table.
Parameter
Description
Upload To
The directory to which you want to upload the objects.
Current Directory: The objects are uploaded to the current directory.
Specified Directory: The objects are uploaded to a specified directory. If the specified directory does not exist, OSS automatically creates the directory and uploads the objects to the directory.
Object ACL
The access control list (ACL) of the objects that you want to upload.
Inherited from Bucket: The ACL of the objects is the same as that of the bucket.
Private (recommended): Only the object owner and authorized users can read and write the objects. Other users cannot access the objects.
Public Read: Only the object owner and authorized users can read and write the objects. Other users, including anonymous users, can only read the objects. If you set the File ACL parameter to this value, the objects may be unexpectedly accessed. This may result in unexpectedly high fees. Exercise caution when you set the File ACL parameter to this value.
Public Read/Write: All users, including anonymous users, can read and write the objects.
WarningIf you set the ACL of the objects to Public Read/Write, all users can read and write the objects. This may result in unauthorized access to the data in your bucket, and you may be charged unexpected fees. If a user uploads prohibited data or information, your legitimate interests and rights may be infringed. We recommend that you do not set the File ACL parameter to Public Read/Write unless necessary.
For more information about ACLs, see Object ACLs.
Files to Upload
The objects or directories that you want to upload.
You can click Select Files to select a local file or click Select Folders to select a directory. You can also drag the local file or directory to the Files to Upload section.
If the selected directory contains an object that you do not want to upload, find the object in the file list in the Files to Upload section and click Remove in the Actions column to remove the object.
ImportantIf the object that you want to upload has the same name as an existing object in the bucket, the existing object is overwritten.
If you drag a directory to the Files to Upload section to upload it, the files and subdirectories in this directory are all uploaded to the bucket.
Do not refresh or close the upload page when objects are being uploaded. Otherwise, the upload tasks are interrupted, and the list of upload tasks is cleared.
When you upload objects, you can configure advanced settings such as the user metadata, storage class, and server-side encryption. For more information, see Simple upload.
ImportantIf you want to upload a large number of objects and set the storage classes of the objects to Deep Cold Archive, you are charged high PUT request fees. We recommend that you set the storage classes of the objects to Standard when you upload the objects, and configure lifecycle rules to convert the storage classes of the Standard objects to Deep Cold Archive. This reduces PUT request fees.
Click Upload Object.
You can view the upload progress of the objects on the Upload Tasks tab. After the objects are uploaded, you can view the names, sizes, and storage classes of the uploaded objects in the directory.
What to do next
You can download uploaded objects to the default download path of your browser or to a specified local path. For more information, see Download objects.
You can share the URLs of uploaded objects with third parties for downloads or previews. For more information, see Share objects.
You can map a custom domain name to the bucket to which the objects are uploaded, and use the custom domain name to access the objects. For more information, see Use custom domain names to access OSS resources in the OSS console.