Unlock the Power of AI

1 million free tokens

88% Price Reduction

Activate Now

Activate EOS and manage EOS resources

Updated at: 2025-01-22 02:14
important

This topic contains important information on necessary precautions. We recommend that you read this topic carefully before proceeding.

You can perform basic operations by using the Edge Object Storage (EOS) console, such as creating buckets, uploading objects, and downloading objects.

Activate EOS

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. Click Activate Now and follow the on-screen instructions to activate EOS.

Bucket management

Create a bucket

Note
  • By default, the maximum number of buckets that can be created by an Alibaba Cloud account in ENS is 20. If you want to increase the quota, contact the Alibaba Cloud business manager.

  • You are not charged for creating a bucket. You are charged only for the storage of objects in the bucket and the traffic generated when the objects are accessed.

  • After you create a bucket, you cannot change the name of the bucket or the region to which the bucket belongs.

  • The capacity of a bucket is scalable. You do not need to purchase capacity before you use a bucket.

  • After you create a bucket, the domain name resolution of the bucket takes a period of time to refresh. We recommend that you perform operations on the bucket after 5 minutes. Otherwise, the operations may fail.

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. Click Create Bucket.

  4. On the Create Bucket page, configure the following parameters and click OK.

    Parameter

    Description

    Bucket Name

    The name of the bucket. The name of a bucket cannot be changed after the bucket is created.

    The name must meet the following requirements:

    • A bucket name must be globally unique.

    • The name can contain lowercase letters, digits, and hyphens (-).

    • The name cannot start or end with a hyphen (-).

    • The name must be 3 to 50 characters in length.

    Scheduling Policy

    • Specify Nodes

    • Global Scheduling

    Note

    If you select Global Scheduling, EOS selects one or more nodes for data storage based on the scheduling policy. Data is distributed and stored on the edge cloud, not on specific nodes. If you want to store data in a specific location, select Specific Nodes.

    Node (if you set Scheduling Policy to Specific Nodes)

    The node to which the bucket belongs.

    You can select a node from the drop-down list. After you create a bucket, the node cannot be changed.

    Scheduling Scope (if you set Scheduling Policy to Global Scheduling)

    • Chinese Mainland

    • Outside Chinese Mainland

    Note

    Select a scheduling scope based on your business requirements. After you create a bucket, the scheduling scope cannot be changed.

    Endpoint

    EOS uses the same global endpoint: EOS.aliyuncs.com.

    Access Control List

    You can configure the access control list (ACL) of a bucket based on your business requirements and modify the ACL of the bucket after you create the bucket. You can configure only one ACL for a bucket. Valid values:

    • Private: Only the owner or authorized users of this bucket can read and write objects in the bucket. Other users cannot access the objects in the bucket without authorization.

    • Public Read (Not Recommended): Only the owner or authorized users of this bucket can write objects in the bucket. Other users, including anonymous users, can only read objects in the bucket.

      Warning

      This may result in unexpected access to the data in the bucket and unexpectedly high fees. Exercise caution when you set the bucket ACL to Public Read.

    • Public Read/Write (Not Recommend): All users, including anonymous users, can perform read and write operations on the objects in the bucket.

      Warning

      If you set the ACL of a bucket to Public Read/Write, all users can access the objects in the bucket and write data to the bucket over the Internet. This may result in unexpected access to the data in the bucket and unexpectedly high 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 bucket ACL to public-read-write unless necessary.

    Remarks

    The value must be 1 to 128 characters in length.

Delete a bucket

If you no longer use a bucket, you can delete the bucket to prevent unnecessary charges.

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket that you want to delete and click Delete in the Actions column.

  4. In the message that appears, click OK.

    Note

    Note: Make sure that the objects in the bucket are deleted before you delete the bucket. Otherwise, the bucket cannot be deleted. A bucket cannot be restored after being deleted.

Object management

Upload an object

  1. Log on to the ENS console

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket where the object is stored and click Manage in the Actions column.

  4. On the Objects page, click Upload Object.

  5. On the Upload Object page, configure the following parameters.

    Parameter

    Description

    Upload To

    Set the directory to which you want to upload the objects.

    • Current Directory: The object is uploaded to the current directory.

    Note

    Set the value to Current Directory.

    Access Control List

    Select the 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.

    Note

    Set the value to Inherited from Bucket.

    Upload Object

    Select the object that you want to upload.

    You can click Scan Files to select a local file, or drag a file to the Upload Object section.

    File naming conventions:

    • The object name must be encoded in UTF-8.

    • The object name is case-sensitive.

    • The object name cannot start with a slash (/) or backslash (\).

    • The name must be 1 to 1,023 bytes in length.

  6. Click Upload. You can view the upload progress on the Upload Tasks tab.

Download an object

After you upload objects to a bucket, you can download the objects to the default download path of your browser or a specific local path.

  1. Log on to the ENS console

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket where the object is stored and click Manage in the Actions column.

  4. On the Objects page, find the object that you want to download and click Download in the Actions column.

Delete an object

  1. Log on to the ENS console

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket that you want to manage and click Manage in the Actions column.

  4. On the Buckets page, find the object that you want to delete and click Delete in the Actions column.

    Note

    Note: Objects cannot be restored after being deleted. Proceed with caution.

Search for objects

If your bucket contains a large number of objects, you can search for and retrieve objects by prefix to improve search efficiency.

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket that you want to manage and click Manage in the Actions column.

  4. On the Objects page, enter a prefix in the search box to query objects.

Lifecycle

Based on your business requirements, you may need to retain some infrequently accessed data in your bucket for a long period of time for compliance or archiving requirements, or delete data that is no longer needed in batches. You can configure lifecycle rules based on the last modified time to delete objects to reduce storage costs. Lifecycle rules are suitable for scenarios where objects that are accessed in specific or predictable patterns.

Create a lifecycle rule

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket and click Manage in the Actions column.

  4. On the Lifecycle page, click Create Rule.

  5. Configure the following parameters and click OK.

    Parameter

    Description

    Parameter

    Description

    Status

    Specify the status of the lifecycle rule. You can select Enabled or Disabled.

    • After you enable a lifecycle rule, objects are deleted based on the configured lifecycle rule.

    • After you disable a lifecycle rule, lifecycle tasks of the lifecycle rule are interrupted.

    Applied To

    Specify the objects on which you want the lifecycle rule to take effect. You can select Objects with Specified Prefix or Whole Bucket.

    Allow Overlapped Prefixes

    Specify whether to allow prefixes that overlap. By default, OSS checks whether the prefix of each lifecycle rule overlaps with that of another lifecycle rule. For example, if the bucket has an existing lifecycle rule (Rule 1) and you want to configure another lifecycle rule (Rule 2) that contains an overlapping prefix:

    • Rule 1: All objects whose names contain the dir1/ prefix in the bucket are deleted 180 days after the objects are last modified.

    • Rule 2: All objects whose names contain the dir1/dir2/ prefix in the bucket are deleted 30 days after the objects are last modified.

    If you do not allow prefix overlapping in the lifecycle configuration, EOS detects that objects in the dir1/dir2/ directory match two deletion rules. Therefore, the two lifecycle rules do not take effect.

    If you allow prefix overlapping in the lifecycle configuration, the objects in the dir1/dir2/ directory are deleted after 30 days. Other objects in the dir1/ directory are deleted after 180 days.

    Prefix

    Specify the prefix in the names of objects on which you want the lifecycle rule to take effect.

    • If you set the prefix to test, all objects whose names contain the test prefix, such as testObj.png and test/testObj.jpg match the lifecycle rule.

    • If you set the prefix to test/, all objects whose names contain the test/ prefix, such as test/example.jpg and test/test.jpg, match the lifecycle rule.

    Object Lifecycle

    Configure rules for objects to specify when the objects expire. Valid values: Days Overdue and Expired At.

    Lifecycle-based Rules

    Configure lifecycle rules to delete expired objects.

    For example, you select Modified Time, set Expired At to June 30, 2023, and specify that objects that are last modified before this date are automatically deleted. In this case, objects that are last modified before June 30, 2023 are automatically deleted. The deleted objects cannot be restored.

CORS

Browsers reject cross-origin requests based on the same-origin policy to keep website content secure. For example, if the JavaScript code on one website makes a request for a resource hosted on another website that has a different origin, the browser denies the request. Two URLs have the same origin if they have the same protocol, domain name or IP address, and port number (if specified). The following table provides examples of origin comparison with http://www.aliyun.com/org/test.html.

URL

Successful access

Cause

URL

Successful access

Cause

http://www.aliyun.com/org/other.html

Yes

Same protocol, domain name, and port number.

http://www.aliyun.com/org/internal/page.html

Yes

Same protocol, domain name, and port number.

https://www.aliyun.com/page.html

No

Different protocols (HTTPS and HTTP).

http://www.aliyun.com:22/dir/page.html

No

Different port numbers (22 and no port number).

http://help.aliyun.com/dir/other.html

No

Different domain names.

The preceding table shows that the browser rejects requests from a URL to another URL that has a different origin. If you want to allow cross-origin requests, you must configure CORS rules.

Note
  • You can create up to 10 CORS rules for a bucket.

  • When EOS receives a cross-origin request or an OPTIONS request that is destined for a bucket, OSS reads the CORS rules that are configured for the bucket and attempts to match the rules one after another. If EOS finds the first match, EOS returns corresponding headers. If the request fails to match the CORS rules, the CORS-related header fields are not returned in the response.

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket that you want to manage and click Manage in the Actions column.

  4. On the CORS Settings page, click Create CORS Rules.

  5. On the Create CORS Rules dialog box, configure the following parameters.

    Parameter

    Required

    Description

    Parameter

    Required

    Description

    Request Source

    Yes

    The origins from which cross-origin requests are allowed. When you configure this parameter, take note of the following items:

    • You can specify multiple allowed origins. Separate origins with line feeds.

    • An origin URL must include the protocol, such as HTTP or HTTPS.

    • You can use an asterisk (*) as the wildcard character. Each source can contain only one asterisk (*).

    • If an origin URL does not use the default port number, specify the actual port number. Example: https://www.example.com:8080.

    The following examples show how to configure domain names:

    • To allow requests from a specific origin, specify the origin URL. Example: https://www.example.com.

    • To match second-level domain names, use an asterisk (*) as the wildcard character in the domain name. Example: https://*.example.com.

    • To match all domain names, enter only an asterisk (*) as the wildcard character.

    Allowed Methods

    Yes

    The methods that cross-origin requests are allowed to use.

    Allowed Headers

    No

    The allowed headers in cross-origin requests. When you configure the headers, take note of the following items:

    • This parameter is in the key:value format and case-insensitive. Example: content-type:text/plain.

    • You can configure multiple headers. Separate multiple headers with line feeds.

    • You can use an asterisk (*) as the wildcard character. Each source can contain only one asterisk (*). Set this parameter to an asterisk (*) wildcard character if you do not have special requirements.

    Exposed Headers

    No

    The response headers available to requests from applications, such as an XMLHttpRequest object in JavaScript. Exposed headers cannot contain asterisks (*).

    Cache Timeout (Seconds)

    No

    The time the browser can cache the response to a preflight (OPTIONS) request to a specific resource. Unit: seconds.

    Vary: Origin

    No

    Selects whether to return the Vary: Origin header.

    If both CORS and non-CORS requests are sent to OSS, or if the Origin header has multiple possible values, we recommend that you select the Vary: Origin header to prevent errors in the local cache.

    Important

    If Vary: Origin is selected, access through the browser or the origin requests may increase.

  6. Click OK.

Permission control

Modify the ACL of a bucket

Note
  • Only the owner of a bucket can modify the ACL of the bucket.

  • If you modify the ACL of a bucket, the ACLs of all objects that inherit the bucket ACL change accordingly.

  1. Log on to the ENS console.

  2. In the left-side navigation pane, choose Storage and Snapshots > EOS.

  3. On the Buckets page, find the bucket that you want to manage and click Access Control List in the Actions column.

  4. On the Configure Access Control List page, change the ACL of the bucket based on your requirements.

  5. Click OK.

  • On this page (1, T)
  • Activate EOS
  • Bucket management
  • Create a bucket
  • Delete a bucket
  • Object management
  • Upload an object
  • Download an object
  • Delete an object
  • Search for objects
  • Lifecycle
  • Create a lifecycle rule
  • CORS
  • Permission control
  • Modify the ACL of a bucket
Feedback
phone Contact Us

Chat now with Alibaba Cloud Customer Service to assist you in finding the right products and services to meet your needs.

alicare alicarealicarealicare