This topic introduces Edge Object Storage (EOS).
Overview
EOS is a distributed object storage service that is based on the edge cloud. EOS provides high reliability and high security at low costs. EOS provides stable storage services with at least 99.9999% data durability and at least 99.9% data availability. EOS allows you to download one or more objects of different types by using a variety of tools, such as the console, API, and SDK, without the need to consider the storage location. EOS is suitable for storing images of social networking and sharing applications. EOS is also suitable for storing data of audio and video applications, large websites, and big data analysis.
Terms
The terms and usage of EOS are similar to the terms and usage of Object Storage Service (OSS). For example, if you want to use EOS to store data, you need to first create a bucket and configure the access control list (ACL) for the bucket. After you create a bucket, you can upload data to the bucket as objects and specify the names (also referred to as keys) of the objects. The name of an object is used as the unique identifier of the object within a bucket.
EOS provides external services by using the OSS API and uses a unified endpoint eos.aliyuncs.com.
Term | Description |
bucket | A bucket is a container that stores objects. Objects must belong to a bucket. You can create buckets of different storage classes to store data based on your business requirements. |
object | An object is the smallest unit of data that is stored in EOS. Unlike typical file systems, objects in EOS are stored in a flat structure instead of a hierarchical structure. An object is composed of a key, metadata, and data that is stored in the object. A key uniquely identifies an object. |
object name | In EOS SDKs for different programming languages, ObjectKey, Key, and ObjectName indicate the full path of the object. You need to specify the full path of an object when you perform operations on the object. For example, when you upload an object to a bucket, ObjectKey indicates the full path that includes the extension of the object name. For example, you can set ObjectKey to abc/efg/123.jpg. |
endpoint | Endpoints are the domain names that are used to access EOS. EOS provides external services over HTTP by using the RESTful API. The public endpoint of EOS is eos.aliyuncs.com. You cannot access EOS buckets over an internal network. |
AccessKey pair | The access credentials that are used to identify the requester. An AccessKey pair consists of an AccessKey ID and an AccessKey secret. EOS uses an AccessKey pair to implement symmetric encryption and verify the identity of a requester. The AccessKey ID is used to identify a user. The AccessKey secret is used to encrypt and verify the signature string. The AccessKey secret must be kept confidential. EOS supports AccessKey pairs that are obtained by using the following methods:
|
atomicity and strong consistency | Object operations in EOS are atomic. Operations can either succeed or fail without intermediate states. After an object is uploaded, you can read the whole object. EOS does not return partial data. Object operations in EOS are highly consistent. For example, when a user receives an upload (PUT) success response, the uploaded object can be immediately read, and replicas of the object are created for redundancy. This ensures that you can always obtain data when you perform the read-after-write operation. Delete operations in EOS are highly consistent. After a user deletes an object, the object and its replicas no longer exist. |
Features
Category | Feature | Description |
Bucket management | Create a bucket | Before you upload objects to EOS, you need to first create a bucket and configure the ACL for the bucket based on your business requirements. |
Delete a bucket | You can delete a bucket that you no longer use to reduce costs. | |
Lifecycle | EOS supports lifecycle rules. You can configure lifecycle rules to automatically delete objects. | |
Object management | Upload an object | Alibaba Cloud provides various methods to upload objects to EOS buckets. |
Download an object | Alibaba Cloud provides various methods to download objects that are stored in EOS buckets. You can download objects to the default download path of your browser, or specify a local path to store the downloaded objects. | |
List objects | By default, when you list objects in a bucket, the objects are returned in alphabetical order. You can list all objects, objects whose names contain a specific prefix, or a specific number of objects in a bucket. | |
Copy an object | You can copy objects from a bucket to another bucket without modifying the object content. | |
Configure object tags | You can configure object tags to classify objects. Tags allow you to manage objects that have the same tag. | |
Delete an object | You can delete one or more objects and parts at a time. You can also configure lifecycle rules to periodically delete expired objects to reduce storage costs. | |
Bucket ACL | Bucket ACL | You can configure the ACL of a bucket when you create the bucket or modify the ACL of the bucket after you create the bucket. Only the owner of a bucket can configure or modify the ACL of the bucket. You can set the ACL of a bucket to one of the following values: public read/write, public read, and private. |
Billing
EOS uses the pay-as-you-go billing method. You are charged for the actual usage of each billable item.
Item | Description |
Billing rule | You are charged based on the resource usage. Bills are generated and fees are deducted from the balance of your Alibaba Cloud account after a billing cycle ends. |
Billing cycle | You are billed on an hourly basis. The fees are automatically deducted from the balance of your Alibaba Cloud account. In most cases, bills are generated after a billing cycle ends. The time when bills are generated is determined by the system. |
Billable items and pricing |
|