tencent cloud

Cloud Object Storage

DokumentasiCloud Object StorageAPI DocumentationBucket APIs Intelligent TieringGET Bucket IntelligentTiering

GET Bucket IntelligentTiering

Download
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-05-19 16:00:35

Feature Description

The GET Bucket IntelligentTiering API is used to query the intelligent tiering configuration information of a bucket. When making this request, you must provide a rule name and obtain a request signature, which indicates that the request is authorized.
Note:
Only a root account or a sub-account that has been granted permission for the GET Bucket IntelligentTiering API can call this API.
An id of `default` is used to query the infrequent access tier rules, while an id other than `default` is used to query the archive and deep archive tier rules.
Obtain the rule with an id of `default`.
If you have never enabled INTELLIGENT_TIERING on a bucket, the response is 404:
<?xml version='1.0' encoding='utf-8' ?>
<Error>
	<Code>IntelligentTieringConfigurationNotFoundError</Code>
	<Message>The Intelligenttiering configuration was not found.</Message>
</Error>
If you have enabled INTELLIGENT_TIERING on a bucket, the response is 200:
<IntelligentTieringConfiguration>
    <Id>default</Id>
    <Status>Enabled</Status>
    <Tiering>
        <AccessTier>INFREQUENT</AccessTier>
        <Days>30|60|90</Days>
    </Tiering>
</IntelligentTieringConfiguration>

Authorization Description

In an authorization policy, set the action to cos:GetBucketIntelligentTiering. View all actions.

id is default (Querying Infrequent Access Tier Rules)

Request

Request Example

GET /?intelligent-tiering&id=default HTTP 1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT date
Authorization: Auth String
Note:
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com. Here, <BucketName-APPID> is the bucket name with the APPID suffix, for example, examplebucket-1250000000. For details, see the Bucket Overview > Basic Information and Bucket Overview > Bucket Naming Conventions documents. <Region> is the available region of COS. For details, see the Regions and Access Domains document.
Authorization: Auth String (For details, see Request Signature).

Request Parameter

To call the GET Bucket IntelligentTiering API, you must use the rule name parameter. The rule name for the infrequent access tier is fixed as `default`.
Parameter
Description
Type
Required
id
The name of the intelligent tiering rule name list task. The id is set to default, which indicates querying the low-frequency tier rules.
String
Yes

Request Header

This API only uses common request headers. For details, see Common Request Headers.

Request Body

The request body of this request is empty.

Response

Response Headers

This API only returns common response headers. For details, see Common Response Headers.

Response Body

<IntelligentTieringConfiguration>
    <Id>default</Id>
    <Status>Enabled</Status>
    <Tiering>
        <AccessTier>INFREQUENT</AccessTier>
        <Days>30|60|90</Days>
        <RequestFrequent>1</RequestFrequent> 
    </Tiering>
</IntelligentTieringConfiguration>
The detailed node descriptions are as follows:
Name
Parent Node
Description
Type
IntelligentTieringConfiguration
None
Specific information for INTELLIGENT_TIERING configuration
Container
Id
IntelligentTieringConfiguration
Specifies the name of the INTELLIGENT_TIERING configuration rule. The rule name for the low-frequency tier is fixed as default.
String
Status
IntelligentTieringConfiguration
Indicates whether the intelligent tiering rule is enabled. Valid values: Enabled, Disabled. When the id is default, only Enabled can be set.
Enum
Tiering
IntelligentTieringConfiguration
Configuration information for data transition in the intelligent tiering rule
Container
AccessTier
IntelligentTieringConfiguration.Tiering
Indicates the low-frequency tier when the id is default. Valid value: INFREQUENT.
Enum
Days
IntelligentTieringConfiguration.Tiering
Specifies the number of days after which data in the standard tier is transitioned to the low-frequency tier. The default value is 30 days. Valid values: 30, 60, 90.
Int
RequestFrequent
IntelligentTieringConfiguration.Tiering
Specifies the number of accesses limit for transitioning data from the standard tier to the low-frequency tier. The default value is 1. When it is used together with the number of days, it achieves the transition effect.
For example, if you set this parameter to 1 and the access days to 30, it means that objects accessed less than once in 30 consecutive days are transitioned from the standard tier to the low-frequency tier.
Int

Error Codes

This API follows unified error responses and error codes. For details, see Error Codes.

Practical Case

Request

GET /?intelligenttiering&id=default HTTP/1.1
Host: examplebucket-1250000000.cos.ap-chengdu.myqcloud.com
Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: */*
User-Agent: python-requests/2.12.4
Authorization: q-sign-algorithm=sha1&q-ak=************************************&q-sign-time=1480932292;1981012292&q-key-time=1480932292;1981012292&q-url-param-list=versioning&q-header-list=host&q-signature=****************************************

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 120
Connection: keep-alive
Date: Sun, 23 Aug 2020 08:15:16 GMT
Server: tencent-cos
x-cos-request-id: NTk5ZDM5OTRfZDNhZDM1MGFfMjYyMTFfZmU3****

<IntelligentTieringConfiguration>
    <Id>default</Id>
    <Status>Enabled</Status>
    <Tiering>
        <AccessTier>INFREQUENT</AccessTier>
        <Days>30</Days>
        <RequestFrequent>1</RequestFrequent> 
    </Tiering>
</IntelligentTieringConfiguration>

Request Header

Request

Request Example

GET /?intelligent-tiering&id=Id HTTP 1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT date
Authorization: Auth String
Note:
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com. Here, <BucketName-APPID> is the bucket name with the APPID suffix, for example, examplebucket-1250000000. For details, see the Bucket Overview > Basic Information and Bucket Overview > Bucket Naming Conventions documents. <Region> is the available region of COS. For details, see the Regions and Access Domains document.
Authorization: Auth String (For details, see Request Signature).

Request Parameter

To call the GET Bucket IntelligentTiering API, you must use the rule name parameter. The rule name for the infrequent access tier is fixed as `default`. A rule name other than `default` indicates an archive or deep archive tier rule.
Parameter
Description
Type
Required
id
The name of the intelligent tiering rule name list task. Set the id to a string other than default, indicating that the rule is for archive tier and deep archive tier conversion.
String
Yes

Request Header

This API only uses common request headers. For details, see Common Request Headers.

Request Body

The request body of this request is empty.

Response

Response Headers

This API only returns common response headers. For details, see Common Response Headers.

Response Body

<IntelligentTieringConfiguration>
    <Id>rule1</Id>
    <Status>Enabled</Status>
    <Filter>
        <And>
            <Prefix>string</Prefix>
            <Tag>
                <Key>string</Key>
                <Value>string</Value>
            </Tag>
            <Tag>
                <Key>string</Key>
                <Value>string</Value>
            </Tag>
            ...
        </And>
    </Filter>
    <Tiering>
        <AccessTier>ARCHIVE_ACCESS</AccessTier>
        <Days>100</Days>
    </Tiering>
    <Tiering>
        <AccessTier>DEEP_ARCHIVE_ACCESS</AccessTier>
        <Days>200</Days>
    </Tiering>
</IntelligentTieringConfiguration>
The detailed node descriptions are as follows:
Name
Parent Node
Description
Type
IntelligentTieringConfiguration
None
Detailed information of the intelligent tiering rule.
Container
Id
IntelligentTieringConfiguration
The name of the intelligent tiering rule name list task. Set the id to a string other than default, indicating that the rule is for archive tier and deep archive tier conversion.
String
Status
IntelligentTieringConfiguration
Indicates whether the intelligent tiering rule is enabled. Valid values: Enabled, Disabled.
When the id is default, only Enabled can be set.
Enum
Filter
IntelligentTieringConfiguration
Filters the objects to be analyzed. When the id is not default, the archive and deep archive tier rules take effect on objects that match the prefix and Tag set in the Filter.
Container
And
IntelligentTieringConfiguration.Filter
Filtering condition. If both the prefix and object Tag conditions are required, use And to wrap them.
Container
Prefix
IntelligentTieringConfiguration.Filter.And
Filters the object prefix. At most one prefix can be specified.
String
Tag
IntelligentTieringConfiguration.Filter.And
When objects to be analyzed are filtered, object Tags (multiple supported) can be used as filtering conditions.
Container
Tiering
IntelligentTieringConfiguration
Configuration information for data transition in the INTELLIGENT_TIERING configuration.
Container
AccessTier
IntelligentTieringConfiguration.Tiering
Specifies the archive or deep archive tier when the id is not default. Valid values: ARCHIVE_ACCESS, DEEP_ARCHIVE_ACCESS.
Enum
Days
IntelligentTieringConfiguration.Tiering
Specifies the day limit for data transition to the archive or deep archive tier in the INTELLIGENT_TIERING configuration when the id is not default.
The archive tier (ARCHIVE_ACCESS) supports a configurable range from 91 to 730.
The deep archive tier (DEEP_ARCHIVE_ACCESS) supports a configurable range from 180 to 730.
Within the same rule, the number of days for the deep archive tier must be greater than that for the archive tier.
Int

Error Codes

This API follows unified error responses and error codes. For details, see Error Codes.

Practical Case

Request

GET /?intelligent-tiering&id=rule1 HTTP/1.1
Host: examplebucket-1250000000.cos.ap-chengdu.myqcloud.com
Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: */*
User-Agent: python-requests/2.12.4
Authorization: q-sign-algorithm=sha1&q-ak=************************************&q-sign-time=1480932292;1981012292&q-key-time=1480932292;1981012292&q-url-param-list=versioning&q-header-list=host&q-signature=****************************************

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 120
Connection: keep-alive
Date: Sun, 23 Aug 2020 08:15:16 GMT
Server: tencent-cos
x-cos-request-id: NTk5ZDM5OTRfZDNhZDM1MGFfMjYyMTFfZmU3****

<IntelligentTieringConfiguration>
    <Id>rule1</Id>
    <Status>Enabled</Status>
    <Tiering>
        <AccessTier>ARCHIVE_ACCESS</AccessTier>
        <Days>100</Days>
    </Tiering>
    <Tiering>
        <AccessTier>DEEP_ARCHIVE_ACCESS</AccessTier>
        <Days>200</Days>
    </Tiering>
</IntelligentTieringConfiguration>
Topik sebelumnya: PUT Bucket IntelligentTieringTopik selanjutnya: LIST Bucket IntelligentTiering Configurations

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan