tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
Documentation

LIST Bucket IntelligentTiering Configurations

Last updated: 2024-06-21 09:57:43

    Description

    The List Bucket IntelligentTiering Configurations API is used to request to return all intelligent tiering configurations in a bucket, including infrequent access tier rules (id is default), and archive and deep archive tier rules (id is not default). Up to 1000 rules can be configured in each bucket.
    Note:
    When calling this request, please ensure that you have sufficient permissions to perform operations on the intelligent tiering configurations of the bucket.
    The bucket owner has such permission by default. If you do not have the permission, please first request it from the bucket owner.

    Request

    Sample request

    GET /?intelligent-tiering HTTP/1.1
    Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
    Date: GMT Date
    Authorization: Auth String
    Note
    Host: <BucketName-APPID>.cos.<Region>.myqcloud.com, where <BucketName-APPID> is the bucket name with the APPID suffix, for example, examplebucket-1250000000. For details, refer to Bucket Overview>Basic Information and Bucket Overview>Bucket Naming Conventions documentation; <Region> refers to the available regions of COS. For details refer to Regions and Access Endpoints documentation.
    Authorization: Auth String (For details, refer to the Request Signature documentation).

    Request parameter

    This API has no request parameter.

    Request header

    This interface uses only common request headers. For details, refer to the Common Request Headers documentation.

    Request body

    The request body of this request is empty.

    Response

    Response header

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

    Response body

    The response body returns application/xml data, the content containing the entire node data is shown as follows:
    <ListBucketIntelligentTieringConfigurationOutput>
        <IntelligentTieringConfiguration>
            <Id>default</Id>
            <Status>Enabled</Status>
            <Tiering>
                <AccessTier>INFREQUENT</AccessTier>
                <Days>30</Days>
                <RequestFrequent>1</RequestFrequent>
            </Tiering>
        </IntelligentTieringConfiguration>
        <IntelligentTieringConfiguration>
            <Id></Id>
            <Status></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></Days>
            </Tiering>
            <Tiering>
                <AccessTier>DEEP_ARCHIVE_ACCESS</AccessTier>
                <Days></Days>
            </Tiering>
        </IntelligentTieringConfiguration>
        <IntelligentTieringConfiguration>
            <Id></Id>
            <Status></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></Days>
            </Tiering>
            <Tiering>
                <AccessTier>DEEP_ARCHIVE_ACCESS</AccessTier>
                <Days></Days>
            </Tiering>
        </IntelligentTieringConfiguration>
    </ListBucketIntelligentTieringConfigurationOutput>
    The nodes are described as follows:
    Name
    Parent Node
    Description
    Type
    ListBucketIntelligentTieringConfigurationOutput
    None
    List of all intelligent tiering configuration rules in the bucket
    Container
    IntelligentTieringConfiguration
    ListBucketIntelligentTieringConfigurationOutput
    Details on intelligent tiering configuration. For the XML structure, refer to
    Container

    Error Code

    This API adheres to standardized error responses and codes. For details, refer to the Error Codes documentation.

    Real-World Case

    Request

    The following request example demonstrates how to obtain intelligent tiering configuration rules from bucket examplebucket-1250000000.
    GET /?intelligent-tiering HTTP/1.1
    Date: Mon, 28 Aug 2018 02:53:38 GMT
    Authorization: q-sign-algorithm=sha1&q-ak=AKIDZfbOAo7cllgPvF9cXFrJD0a1ICvR98JM&q-sign-time=1503895278;1503895638&q-key-time=1503895278;1503895638&q-header-list=host&q-url-param-list=inventory&q-signature=f77900be432072b16afd8222b4b349aabd837cb9
    Host: examplebucket-1250000000.cos.ap-beijing.myqcloud.com

    Response

    After the request, COS returns the following response, indicating that there are currently the infrequent access tier rule default, and archive and deep archive tier rules rule1 and rule2 within this bucket.
    Infrequent Access Tier Rule default
    After 30 consecutive days of no access, intelligent tiering objects will transition from the frequent access tier to the infrequent access tier.
    Archive and Deep Archive Tier Rule rule1
    Effective for intelligent tiering objects with the prefix folder1 in bucket examplebucket-1250000000.
    After 100 consecutive days of no access, intelligent tiering objects will transition from the infrequent access tier to the archive tier.
    After 200 consecutive days of no access, intelligent tiering objects will transition from the archive tier to the deep archive tier.
    Archive and Deep Archive Tier Rule rule2
    Effective for intelligent tiering objects with the prefix folder2 in bucket examplebucket-1250000000.
    After 91 consecutive days of no access, intelligent tiering objects will transition from the infrequent access tier to the archive tier.
    HTTP/1.1 200 OK
    Content-Type: application/xml
    Content-Length: 331
    Date: Mon, 28 Aug 2018 02:53:39 GMT
    Server: tencent-cos
    x-cos-request-id: NTlhMzg1ZWVfMjQ4OGY3MGFfMWE1NF8****
    
    <ListBucketIntelligentTieringConfigurationOutput>
        <IntelligentTieringConfiguration>
            <Id>default</Id>
            <Status>Enabled</Status>
            <Tiering>
                <AccessTier>INFREQUENT</AccessTier>
                <Days>30</Days>
                <RequestFrequent>1</RequestFrequent>
            </Tiering>
        </IntelligentTieringConfiguration>
        <IntelligentTieringConfiguration>
            <Id>rule1</Id>
            <Status>Enabled</Status>
            <Filter>
                <Prefix>folder1</Prefix>
            </Filter>
            <Tiering>
                <AccessTier>ARCHIVE_ACCESS</AccessTier>
                <Days>100</Days>
            </Tiering>
            <Tiering>
                <AccessTier>DEEP_ARCHIVE_ACCESS</AccessTier>
                <Days>200</Days>
            </Tiering>
        </IntelligentTieringConfiguration>
        <IntelligentTieringConfiguration>
            <Id>rule2</Id>
            <Status>Enabled</Status>
            <Filter>
                <Prefix>folder2</Prefix>
            </Filter>
            <Tiering>
                <AccessTier>ARCHIVE_ACCESS</AccessTier>
                <Days>91</Days>
            </Tiering>
        </IntelligentTieringConfiguration>
    </ListBucketIntelligentTieringConfigurationOutput>
    
    
    Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
    Privacy PolicyLegalCookie Policy