From 6cc49c5ba912c1662c3742b175d4e9784281dbb0 Mon Sep 17 00:00:00 2001 From: zhangyue Date: Fri, 11 Jul 2025 12:37:59 +0000 Subject: [PATCH] OBS UMN DOC Reviewed-by: Sabelnikov, Dmitriy Co-authored-by: zhangyue Co-committed-by: zhangyue --- docs/obs/umn/ALL_META.TXT.json | 10 +++++----- docs/obs/umn/CLASS.TXT.json | 8 ++++---- docs/obs/umn/en-us_topic_0045853755.html | 2 +- docs/obs/umn/en-us_topic_0045853854.html | 2 +- docs/obs/umn/en-us_topic_0066088957.html | 4 ++-- docs/obs/umn/obs_03_0002.html | 2 +- docs/obs/umn/obs_03_0054.html | 2 +- docs/obs/umn/obs_03_0102.html | 2 +- docs/obs/umn/obs_03_0109.html | 2 +- docs/obs/umn/obs_03_0114.html | 4 ++-- docs/obs/umn/obs_03_0123.html | 4 ++-- docs/obs/umn/obs_03_0142.html | 2 +- docs/obs/umn/obs_03_0201.html | 2 +- docs/obs/umn/obs_03_0316.html | 2 +- docs/obs/umn/obs_03_0322.html | 2 +- docs/obs/umn/obs_03_0326.html | 2 +- docs/obs/umn/obs_03_0327.html | 2 +- docs/obs/umn/obs_03_0329.html | 2 +- docs/obs/umn/obs_03_0335.html | 2 +- docs/obs/umn/obs_41_0054.html | 2 +- docs/obs/umn/obs_faq_0014.html | 6 +++--- docs/obs/umn/obs_faq_0027.html | 2 +- 22 files changed, 34 insertions(+), 34 deletions(-) diff --git a/docs/obs/umn/ALL_META.TXT.json b/docs/obs/umn/ALL_META.TXT.json index 01bdcbfc4..503e51f3a 100644 --- a/docs/obs/umn/ALL_META.TXT.json +++ b/docs/obs/umn/ALL_META.TXT.json @@ -667,7 +667,7 @@ "node_id":"obs_03_0316.xml", "product_code":"obs", "code":"34", - "des":"This section describes how to create a folder on OBS Console. Folders facilitate data management in OBS.Unlike a file system, OBS does not involve the concepts of file an", + "des":"You can create folders in a bucket on OBS Console to help organize and manage your data more efficiently.Unlike a file system, OBS does not involve the concepts of file a", "doc_type":"usermanual", "kw":"folder creation,folder create,Creating a Folder,Managing Objects,User Guide", "search_title":"", @@ -1227,9 +1227,9 @@ "node_id":"obs_03_0114.xml", "product_code":"obs", "code":"62", - "des":"Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always take precedence over an allow statement", + "des":"Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always takes precedence over an allow statemen", "doc_type":"usermanual", - "kw":"How Does Authorization Work When Multiple Access Control Mechanisms Co-Exist?,Permission Control Mec", + "kw":"Which Permissions Apply When They Conflict?,Permission Control Mechanisms,User Guide", "search_title":"", "metedata":[ { @@ -1239,7 +1239,7 @@ "documenttype":"usermanual" } ], - "title":"How Does Authorization Work When Multiple Access Control Mechanisms Co-Exist?", + "title":"Which Permissions Apply When They Conflict?", "githuburl":"" }, { @@ -4287,7 +4287,7 @@ "node_id":"obs_faq_0014.xml", "product_code":"obs", "code":"215", - "des":"Resumable transfer is supported for all transfer methods except API.", + "des":"The following table describes the resumable transfer support across OBS tools.", "doc_type":"usermanual", "kw":"Does OBS Support Resumable Transfer?,OBS Basics,User Guide", "search_title":"", diff --git a/docs/obs/umn/CLASS.TXT.json b/docs/obs/umn/CLASS.TXT.json index 9d932cc0e..6fab282b9 100644 --- a/docs/obs/umn/CLASS.TXT.json +++ b/docs/obs/umn/CLASS.TXT.json @@ -297,7 +297,7 @@ "code":"33" }, { - "desc":"This section describes how to create a folder on OBS Console. Folders facilitate data management in OBS.Unlike a file system, OBS does not involve the concepts of file an", + "desc":"You can create folders in a bucket on OBS Console to help organize and manage your data more efficiently.Unlike a file system, OBS does not involve the concepts of file a", "product_code":"obs", "title":"Creating a Folder", "uri":"obs_03_0316.html", @@ -549,9 +549,9 @@ "code":"61" }, { - "desc":"Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always take precedence over an allow statement", + "desc":"Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always takes precedence over an allow statemen", "product_code":"obs", - "title":"How Does Authorization Work When Multiple Access Control Mechanisms Co-Exist?", + "title":"Which Permissions Apply When They Conflict?", "uri":"obs_03_0114.html", "doc_type":"usermanual", "p_code":"57", @@ -1926,7 +1926,7 @@ "code":"214" }, { - "desc":"Resumable transfer is supported for all transfer methods except API.", + "desc":"The following table describes the resumable transfer support across OBS tools.", "product_code":"obs", "title":"Does OBS Support Resumable Transfer?", "uri":"obs_faq_0014.html", diff --git a/docs/obs/umn/en-us_topic_0045853755.html b/docs/obs/umn/en-us_topic_0045853755.html index 862af92eb..4b89e3e2d 100644 --- a/docs/obs/umn/en-us_topic_0045853755.html +++ b/docs/obs/umn/en-us_topic_0045853755.html @@ -9,7 +9,7 @@

Procedure

  1. In the bucket list, click the bucket you want to operate to go to the Objects page.
  2. (Optional) If the static website files in the bucket are not accessible to everyone, perform this step. If they are already accessible to everyone, skip this step.

    To grant required permissions, see Granting Anonymous Users Permission to Access Objects.

    If the bucket contains only static website files, configure the Object Read-Only policy for the bucket, so that all files in it are publicly accessible.

    -
    1. Choose Permissions > Bucket Policies.
    2. Click Create.
    3. Configure bucket policy information. +
      1. Choose Permissions > Bucket Policies.
      2. Click Create.
      3. Configure bucket policy information.
        Table 1 Parameters for configuring a public read policy

        Parameter

        Description

        diff --git a/docs/obs/umn/en-us_topic_0045853854.html b/docs/obs/umn/en-us_topic_0045853854.html index 68ae26ffa..1facb89ed 100644 --- a/docs/obs/umn/en-us_topic_0045853854.html +++ b/docs/obs/umn/en-us_topic_0045853854.html @@ -13,7 +13,7 @@

        Current Version or Historical Version:

        • Current Version and Historical Version are two concepts for versioning. If versioning is enabled for a bucket, uploading objects with the same name to the bucket creates different object versions. The last uploaded object is called the current version, while those previously uploaded are called historical versions.
        • You can configure either the Current Version or Historical Version, or both of them.
        -
        • Transition to Warm: After this number of days since the last update, objects meeting specified conditions will be transitioned to Warm. This number must be at least 30.
        • Transition to Cold: After this number of days since the last update, objects meeting specified conditions will be transitioned to Cold. If you configure to transition objects first to Warm and then Cold, the objects must stay Warm at least 30 days before they can be transitioned to Cold. If transition to Cold is used, but transition to Warm is not, there is no limit on the number of days for transition.
        • Delete Objects After (Days): After this number of days since the last update, objects meeting certain conditions will be expired and then deleted. This number must be an integer larger than that specified for any of the transition operations.
        • Delete Fragments After (Days): After this number of days since the fragment generation, OBS will automatically delete fragments in the bucket.
        +
        • Transition to Warm: After this number of days since the last update, objects meeting specified conditions will be transitioned to Warm.
        • Transition to Cold: After this number of days since the last update, objects meeting specified conditions will be transitioned to Cold.
        • Delete Objects After (Days): After this number of days since the last update, objects meeting certain conditions will be expired and then deleted. This number must be an integer larger than that specified for any of the transition operations.
        • Delete Fragments After (Days): After this number of days since the fragment generation, OBS will automatically delete fragments in the bucket.
        For example, on January 7, 2015, you saved the following files in OBS:
        • log/test1.log
        • log/test2.log
        • doc/example.doc
        • doc/good.txt
        On January 10, 2015, you saved another four files:
        • log/clientlog.log
        • log/serverlog.log
        • doc/work.doc
        • doc/travel.txt
        diff --git a/docs/obs/umn/en-us_topic_0066088957.html b/docs/obs/umn/en-us_topic_0066088957.html index 548139bde..264567192 100644 --- a/docs/obs/umn/en-us_topic_0066088957.html +++ b/docs/obs/umn/en-us_topic_0066088957.html @@ -6,10 +6,10 @@

        The static website files hosted in the bucket are accessible to anonymous users.

        Static web page files in the Cold storage class have been restored. For more information, see Restoring an Object from Cold Storage.

        -

        Procedure

        1. In the bucket list, click the bucket you want to operate to go to the Objects page.
        2. In the navigation pane, choose Data Management > Static Website Hosting.
        3. Click Configure Static Website Hosting. The Configure Static Website Hosting dialog box is displayed.
        4. Enable Status.
        5. Set Hosting By to Redirection, and enter the access domain name or URL of the bucket to which requests are redirected.

          Figure 1 Configuring redirection
          +

          Procedure

          1. In the bucket list, click the bucket you want to operate to go to the Objects page.
          2. In the navigation pane, choose Data Management > Static Website Hosting.
          3. Click Configure Static Website Hosting. The Configure Static Website Hosting dialog box is displayed.
          4. Enable Status.
          5. Set Hosting By to Redirection, and enter the access domain name or URL of the bucket to which requests are redirected.

            Figure 1 Configuring redirection

          6. Click OK.
          7. In the bucket list, click the bucket to which requests for the static website are redirected.
          8. (Optional) If the static website files in the bucket are not accessible to everyone, perform this step. If they are already accessible to everyone, skip this step.

            To grant required permissions, see Granting Anonymous Users Permission to Access Objects.

            If the bucket contains only static website files, configure the Object Read-Only policy for the bucket, so that all files in it are publicly accessible.

            -
            1. Choose Permissions > Bucket Policies.
            2. Click Create.
            3. Configure bucket policy information. +
              1. Choose Permissions > Bucket Policies.
              2. Click Create.
              3. Configure bucket policy information.
                - - diff --git a/docs/obs/umn/obs_03_0109.html b/docs/obs/umn/obs_03_0109.html index 425c3c27c..3fa78a088 100644 --- a/docs/obs/umn/obs_03_0109.html +++ b/docs/obs/umn/obs_03_0109.html @@ -12,7 +12,7 @@
              4. Relationship Between a Bucket ACL and a Bucket Policy
                5. -
              5. How Does Authorization Work When Multiple Access Control Mechanisms Co-Exist?
                +
              6. Which Permissions Apply When They Conflict?
                7. diff --git a/docs/obs/umn/obs_03_0114.html b/docs/obs/umn/obs_03_0114.html index f9c765c2f..c9ee456ce 100644 --- a/docs/obs/umn/obs_03_0114.html +++ b/docs/obs/umn/obs_03_0114.html @@ -1,7 +1,7 @@ -

                How Does Authorization Work When Multiple Access Control Mechanisms Co-Exist?

                -
                • Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always take precedence over an allow statement.

                  Suppose that IAM policies grant a user the access to an object, a bucket policy denies the user's access to that object, and there is no ACL configured. Then user's access to the object will be denied.

                  +

                  Which Permissions Apply When They Conflict?

                  +
                  • Based on the principle of least privilege, the default access control result is always deny, and an explicit deny statement always takes precedence over an allow statement.

                    Suppose that IAM policies grant a user the access to an object, a bucket policy denies the user's access to that object, and there is no ACL configured. Then user's access to the object will be denied.

                  • If no method specifies an allow statement, then the request will be denied by default. Only if no method specifies a deny statement and one or more methods specify an allow statement, will the request be allowed.

                    For example, if a bucket has multiple bucket policies with allow statements, the adding of a new bucket policy with an allow statement will simply add the allowed permissions to the bucket, but the adding of a new bucket policy with a deny statement will result in a re-arrangement of the permissions. The deny statement will take precedence over allowed statements, even the denied permissions are allowed in other bucket policies.

                  Figure 1 Authorization process
                  diff --git a/docs/obs/umn/obs_03_0123.html b/docs/obs/umn/obs_03_0123.html index 1ce7e985c..19ff02f78 100644 --- a/docs/obs/umn/obs_03_0123.html +++ b/docs/obs/umn/obs_03_0123.html @@ -3,7 +3,7 @@

                  Configuring a Custom Bucket Policy (Common Mode)

                  You can customize bucket policies based on your needs. A custom bucket policy consists of five basic elements: effect, principals, resources, actions, and conditions.

                  This section describes how to configure a custom bucket policy in common mode (GUI).

                  -

                  Procedure

                  1. In the bucket list, click the bucket you want to operate to go to the Objects page.
                  2. In the navigation pane, choose Permissions > Bucket Policies.
                  3. Click Create.
                  4. Configure a bucket policy.

                    Figure 1 Configuring a bucket policy
                    +

                    Procedure

                    1. In the bucket list, click the bucket you want to operate to go to the Objects page.
                    2. In the navigation pane, choose Permissions > Bucket Policies.
                    3. Click Create.
                    4. Configure a bucket policy.

                      Figure 1 Configuring a bucket policy
                Table 1 Parameters for configuring a public read policy

                Parameter

                Description

                diff --git a/docs/obs/umn/obs_03_0002.html b/docs/obs/umn/obs_03_0002.html index 6e7759d65..74bb36d60 100644 --- a/docs/obs/umn/obs_03_0002.html +++ b/docs/obs/umn/obs_03_0002.html @@ -11,7 +11,7 @@

                Application Scenarios

                • The same OBS resources need to be accessed in different locations. To minimize the access latency, you can use cross-region replication to create object copies in the nearest region.
                • Due to business reasons, you need to migrate OBS data to the data center in another region.
                • To ensure data security and availability, you need to create explicit backups for all data written to OBS in the data center of another region. Therefore, secure backup data is available if the source data is damaged irrevocably.

                Constraints

                Cross-region replication has the following constraints:

                -
                • Currently, only buckets of version 3.0 support cross-region replication. To check the bucket version, go to the Overview page of the bucket on OBS Console. Then you can view the bucket version in the Basic Information area.
                • The source bucket and the destination bucket must belong to different regions separately. Data cannot be copied between buckets in the same region.
                • Objects of the Cold storage class in the source bucket cannot be copied to the destination bucket through the cross-region replication function.
                • If the region where the destination bucket resides does not support the storage classes, object copies will be stored in the standard storage class.
                • The versioning status of the source and destination buckets must keep the same.
                • Objects in a source bucket can be copied to only one destination bucket, and cannot be copied again from the destination bucket to another bucket. For example, bucket A and bucket B are in two different regions. You can copy data from bucket A to bucket B or the other way round. However, data copies in either bucket A or bucket B cannot be replicated anymore.
                • Object deletion actions made on the source bucket are usually not synchronized to the destination bucket when synchronous deletion of objects is disabled. The object deletion synchronization will happen only when both the source and destination buckets have versioning enabled and you delete an object from the source bucket without specifying a version.

                  When synchronous deletion of objects is enabled, object deletion actions made on the source bucket will be synchronized to the destination bucket. Deleting an object from the source bucket also deletes the object from the destination bucket.

                  +
                  • Only buckets of version 3.0 or later support cross-region replication. To check the bucket version, go to the Overview page of the bucket on OBS Console. Then you can view the bucket version in the Basic Information area.
                  • The source bucket and the destination bucket must belong to different regions separately. Data cannot be copied between buckets in the same region.
                  • Objects of the Cold storage class in the source bucket cannot be copied to the destination bucket through the cross-region replication function.
                  • If the region where the destination bucket resides does not support the storage classes, object copies will be stored in the standard storage class.
                  • The source and destination buckets must have the same versioning status.
                  • Objects in a source bucket can be copied to only one destination bucket, and cannot be copied again from the destination bucket to another bucket. For example, bucket A and bucket B are in two different regions. You can copy data from bucket A to bucket B or the other way round. However, data copies in either bucket A or bucket B cannot be replicated anymore.
                  • Object deletion actions made on the source bucket are usually not synchronized to the destination bucket when synchronous deletion of objects is disabled. The object deletion synchronization will happen only when both the source and destination buckets have versioning enabled and you delete an object from the source bucket without specifying a version.

                    When synchronous deletion of objects is enabled, object deletion actions made on the source bucket will be synchronized to the destination bucket. Deleting an object from the source bucket also deletes the object from the destination bucket.

                  • For an enabled cross-region replication rule, if you change the versioning status of the destination bucket, the replication of objects will fail. If you want to change the versioning status of the source bucket, delete the replication configuration first, and then make the change.
                  • Ensure that owners of the source and destination buckets have the read and write permissions to the two buckets. Otherwise, data cannot be synchronized. If the system does not have the permissions to read the source bucket or write the destination bucket due to read/write permission errors, objects cannot be copied successfully, and such replication will not be resumed even if the permission error is rectified.
                  • For a source bucket, you can create only one cross-region replication rule that applies to the whole bucket for replication of all objects in the bucket. However, you can create a maximum of 100 cross-region replication rules based on object prefixes for the replication of objects that match the prefixes.
                  • OBS currently only supports the replication between one source bucket and one destination bucket. Replication from one source bucket to multiple destination buckets is not supported. The destination bucket can be modified. However, modifying the destination bucket will change the destination bucket of all existing rules.
                  • If you delete the OBS agency for an enabled cross-region replication rule, the object replication will be in the FAILED status.
                  • Do not delete, overwrite object replicas in the destination bucket, or modify their ACLs, which may cause inconsistency of latest object versions or permission control settings between the destination bucket and the source bucket.
                  • After a replication with Synchronize Existing Objects enabled is complete, if the replication policy keeps unchanged, any ACL changes of source objects will be synchronized to object copies. However, ACL changes of source historical objects will not be synchronized to the copies of historical objects.

                Important Notes

                • If the cross-region replication rule is enabled but the function of synchronizing existing objects is disabled, the rule takes effect several minutes later. Objects uploaded during this period may not be replicated.
                • If the cross-region replication rule and the function of synchronizing existing objects are both enabled, existing objects will be replicated 5 minutes later.
                diff --git a/docs/obs/umn/obs_03_0054.html b/docs/obs/umn/obs_03_0054.html index 6eae236a8..9739be4f6 100644 --- a/docs/obs/umn/obs_03_0054.html +++ b/docs/obs/umn/obs_03_0054.html @@ -21,7 +21,7 @@

                Server-side encryption

                Encrypts objects on the server side to enhance security of objects stored on OBS.

                +

                Encrypts objects on the server side to enhance the security of objects stored in OBS.

                Object metadata

                diff --git a/docs/obs/umn/obs_03_0102.html b/docs/obs/umn/obs_03_0102.html index 94f5d2c9f..ff87bf5c1 100644 --- a/docs/obs/umn/obs_03_0102.html +++ b/docs/obs/umn/obs_03_0102.html @@ -13,7 +13,7 @@

                * (binary stream, which does not know the type of the file to be downloaded)

                +

                .* (binary stream, unknown file type)

                application/octet-stream
                @@ -23,7 +23,7 @@ -
                Table 1 Parameters for configuring a custom bucket policy

                Parameter

                Effect

                • Allow: The policy allows the matched requests.
                • Deny: The policy denies the matched requests.
                +
                • Allow: The policy allows the matched requests.
                • Deny: The policy denies the matched requests.

                Principals

                diff --git a/docs/obs/umn/obs_03_0142.html b/docs/obs/umn/obs_03_0142.html index 302e2d487..c689e9917 100644 --- a/docs/obs/umn/obs_03_0142.html +++ b/docs/obs/umn/obs_03_0142.html @@ -2,7 +2,7 @@

                Configuring a Standard Bucket Policy

                OBS Console provides bucket policy templates for multiple typical scenarios. You can use these templates to quickly configure bucket policies.

                -

                Procedure

                1. In the bucket list, click the bucket you want to operate to go to the Objects page.
                2. In the navigation pane, choose Permissions > Bucket Policies.
                3. Click Create.
                4. Choose a policy template. For details about the parameters, see Bucket Policies and Object Policies.

                  Figure 1 Choosing the Public Read template
                  +

                  Procedure

                  1. In the bucket list, click the bucket you want to operate to go to the Objects page.
                  2. In the navigation pane, choose Permissions > Bucket Policies.
                  3. Click Create.
                  4. Choose a policy template. For details about the parameters, see Bucket Policies and Object Policies.

                    Figure 1 Choosing the Public Read template
                    Figure 2 Choosing the Public Read/Write template
                    Figure 3 Choosing the Bucket Read-Only template
                    Figure 4 Choosing the Bucket Read/Write template
                    diff --git a/docs/obs/umn/obs_03_0201.html b/docs/obs/umn/obs_03_0201.html index dc4a4686b..937e0aca6 100644 --- a/docs/obs/umn/obs_03_0201.html +++ b/docs/obs/umn/obs_03_0201.html @@ -36,7 +36,7 @@
          -

          OBS Advantages

          • Data durability and service continuity: OBS supports access of massive number of users.
          • Multi-level protection and authorization management: Measures, including versioning, server-side encryption, URL validation, virtual private cloud (VPC)-based network isolation, access log audit, and fine-grained access control are provided to keep data secure and trusted.
          • Highly concurrent access for massive number of objects: With intelligent scheduling and response, optimized access paths, and technologies such as transmission acceleration, event notifications, and big data vertical optimization, you can store massive number of objects in OBS and still experience smooth concurrent access with ultra-high bandwidth and low latency.
          • Easy use and management: OBS provides standard REST APIs, SDKs in different programming languages, and data migration tools, like OBS Browser, to help you quickly move your workloads to cloud. Storage resources are linearly, infinitely scalable, without compromising performance. You do not have to plan storage capacity beforehand or worry about expansion or reduction.
          +

          OBS Advantages

          • Data durability and service continuity: OBS supports access of massive number of users.
          • Multi-level protection and authorization management: Measures, including versioning, server-side encryption, URL validation, virtual private cloud (VPC)-based network isolation, access log audit, and fine-grained access control are provided to keep data secure and trusted.
          • Highly concurrent access for massive number of objects: With intelligent scheduling and response, optimized access paths, and technologies such as transmission acceleration, event notifications, and big data vertical optimization, you can store massive number of objects in OBS and still experience smooth concurrent access with ultra-high bandwidth and low latency.
          • Easy use and management: OBS provides standard REST APIs, SDKs in different programming languages, and data migration tools, like OBS Browser, to help you quickly move your workloads to cloud. Storage resources are linearly, infinitely scalable, without compromising performance. You do not have to plan storage capacity beforehand or worry about expansion or reduction.
          diff --git a/docs/obs/umn/obs_03_0316.html b/docs/obs/umn/obs_03_0316.html index 65f72afd4..2f7559c75 100644 --- a/docs/obs/umn/obs_03_0316.html +++ b/docs/obs/umn/obs_03_0316.html @@ -1,7 +1,7 @@

          Creating a Folder

          -

          This section describes how to create a folder on OBS Console. Folders facilitate data management in OBS.

          +

          You can create folders in a bucket on OBS Console to help organize and manage your data more efficiently.

          Background Information

          • Unlike a file system, OBS does not involve the concepts of file and folder. For easy data management, OBS provides a method to simulate folders. In OBS, an object is simulated as a folder by adding a slash (/) to the end of the object name on OBS Console. If you call the API to list objects, paths of objects are returned. In an object path, the content following the last slash (/) is the object name. If a path ends with a slash (/), it indicates that the object is a folder. The hierarchical depth of the object does not affect the performance of accessing the object.
          • OBS Console does not support the download of folders. You can use OBS Browser to download folders.

          Procedure

          1. In the bucket list, click the bucket you want to operate to go to the Objects page.
          2. Click Create Folder, or click a folder in the object list to open it and click Create Folder.
          3. In the Folder Name text box, enter a name for the folder.

            • You can create single-level or multi-level folders.
            • The name cannot contain the following special characters: \:*?"<>|
            • The name cannot start or end with a period (.) or slash (/).
            • The folder's absolute path cannot exceed 1,023 characters.
            • Any single slash (/) separates and creates multiple levels of folders at once.
            • The name cannot contain two or more consecutive slashes (/).
            diff --git a/docs/obs/umn/obs_03_0322.html b/docs/obs/umn/obs_03_0322.html index 897db7c00..ce86c0679 100644 --- a/docs/obs/umn/obs_03_0322.html +++ b/docs/obs/umn/obs_03_0322.html @@ -1,7 +1,7 @@

            Enabling Server-Side Encryption When Uploading an Object

            -

            OBS allows you to encrypt objects with server-side encryption so that the objects can be securely stored in OBS.

            +

            OBS allows you to encrypt objects with server-side encryption so that the objects can be securely stored in OBS.

            When you upload an object to a bucket with server-side encryption disabled, you can separately configure server-side encryption for the object. If the bucket has server-side encryption enabled, the object you upload inherits encryption from the bucket by default. You can also configure new encryption for the object.

            Constraints

            • The object encryption status cannot be changed.
            • A key in use cannot be deleted. Otherwise, the object encrypted with this key cannot be downloaded.
            • Objects encrypted on the server side cannot be shared.
            diff --git a/docs/obs/umn/obs_03_0326.html b/docs/obs/umn/obs_03_0326.html index 1c9bf1d10..1c4eda994 100644 --- a/docs/obs/umn/obs_03_0326.html +++ b/docs/obs/umn/obs_03_0326.html @@ -5,7 +5,7 @@

            Procedure

            1. In the bucket list, click the bucket you want to operate to go to the Objects page.
            2. In the navigation pane, choose Permissions > Bucket ACLs.
            3. On the Bucket ACLs page, choose Private, Public Read, or Public Read/Write to grant the bucket ACL permission for anonymous users.

              • After you change Public Read or Public Read/Write to Private, only the bucket owner or object owner has the access.
              • After you change Private to Public Read, anyone can read objects in the bucket. No identity authentication is required.
              • After you change Private to Public Read/Write, anyone can read, write, and delete objects in the bucket. No identity authentication is required.
              -

            4. In the Operation column, click Edit to grant the owner, anonymous user, or log delivery user required ACL permissions for the bucket.
            5. In the middle of the page, click Export to get the bucket ACL configuration. The file includes the user type, account, bucket access, and ACL access.
            6. In the middle of the page, click Add to apply specific ACL permissions to an account.

              Enter an account ID and specify ACL permissions for the account. You can obtain the account ID from the My Credentials page.

              +

            7. In the Operation column, click Edit to grant the owner, anonymous user, or log delivery user required ACL permissions for the bucket.
            8. In the middle of the page, click Export to get the bucket ACL configuration. The file includes the user type, account, bucket access, and ACL access.
            9. In the middle of the page, click Add to apply specific ACL permissions to an account.

              Enter an account ID and specify ACL permissions for the account. You can obtain the account ID from the My Credentials page.

              Click OK.

            diff --git a/docs/obs/umn/obs_03_0327.html b/docs/obs/umn/obs_03_0327.html index 383cace35..e1c753311 100644 --- a/docs/obs/umn/obs_03_0327.html +++ b/docs/obs/umn/obs_03_0327.html @@ -6,7 +6,7 @@

            Related Operations

            After versioning is configured for a bucket, you can go to the object details page, click the Versions tab, and then delete, share, and download object versions.

            1. In the bucket list, click the bucket you want to operate to go to the Objects page.
            2. In the object list, click the object you want to go to the object details page.
            3. On the Versions tab page, view all versions of the object.
            4. Perform the following operations on object versions:

              1. Download a desired version of the object by clicking Download in the Operation column.

                If the version you want to download is in the Cold storage class, restore it first.

                -
              2. Share a version of the object by clicking Share in the Operation column.
              3. Delete a version of the object by choosing More > Delete in the Operation column. If you delete the latest version, the most recent version will become the latest version.
              +
            5. Share a version of the object by clicking Share in the Operation column.
            6. Permanently delete a version of the object by choosing More > Delete in the Operation column. The deleted object version cannot be recovered. If you delete the latest version, the most recent version will become the latest version.

          diff --git a/docs/obs/umn/obs_03_0329.html b/docs/obs/umn/obs_03_0329.html index a75cb1c12..f73677889 100644 --- a/docs/obs/umn/obs_03_0329.html +++ b/docs/obs/umn/obs_03_0329.html @@ -2,7 +2,7 @@

          Configuring Access Logging for a Bucket

          After logging is enabled for a bucket, OBS automatically converts bucket logs into objects following the naming rules and writes the objects into a target bucket.

          -

          Procedure

          1. In the bucket list, click the bucket you want to operate to go to the Objects page.
          2. In the navigation pane, choose Overview.
          3. In the Basic Configurations area, click Logging. The Logging dialog box is displayed.
          4. Select Enable.

            Figure 1 Logging
            +

            Procedure

            1. In the bucket list, click the bucket you want to operate to go to the Objects page.
            2. In the navigation pane, choose Overview.
            3. In the Basic Configurations area, click Logging. The Logging dialog box is displayed.
            4. Select Enable.

              Figure 1 Logging

            5. Select an existing bucket where you want to store log files. Log delivery users of the selected bucket will be automatically granted the permissions to read the bucket ACL and write logs to the bucket.
            6. Enter a prefix for the Log File Name Prefix.

              After logging is enabled, generated logs are named in the following format:

              <Log File Name Prefix>YYYY-mm-DD-HH-MM-SS-<UniqueString>

              • <Log File Name Prefix> is the shared prefix of log file names.
              • YYYY-mm-DD-HH-MM-SS indicates when the log is generated.
              • <UniqueString> indicates a character string generated by OBS.
              diff --git a/docs/obs/umn/obs_03_0335.html b/docs/obs/umn/obs_03_0335.html index c6b63eb4b..c55831676 100644 --- a/docs/obs/umn/obs_03_0335.html +++ b/docs/obs/umn/obs_03_0335.html @@ -15,7 +15,7 @@

              Current Version or Historical Version:

              • Current Version and Historical Version are two concepts for versioning. If versioning is enabled for a bucket, uploading objects with the same name to the bucket creates different object versions. The last uploaded object is called the current version, while those previously uploaded are called historical versions.
              • You can configure either the Current Version or Historical Version, or both of them.
              -
              • Transition to Warm: After this number of days since the last update, objects meeting specified conditions will be transitioned to Warm. This number must be at least 30.
              • Transition to Cold: After this number of days since the last update, objects meeting specified conditions will be transitioned to Cold. If you configure to transition objects first to Warm and then Cold, the objects must stay Warm at least 30 days before they can be transitioned to Cold. If transition to Cold is used, but transition to Warm is not, there is no limit on the number of days for transition.
              • Delete Objects After (Days): After this number of days since the last update, objects meeting certain conditions will be expired and then deleted. This number must be an integer larger than that specified for any of the transition operations.
              • Delete Fragments After (Days): After this number of days since the fragment generation, OBS will automatically delete fragments in the bucket.
              +
              • Transition to Warm: After this number of days since the last update, objects meeting specified conditions will be transitioned to Warm.
              • Transition to Cold: After this number of days since the last update, objects meeting specified conditions will be transitioned to Cold.
              • Delete Objects After (Days): After this number of days since the last update, objects meeting certain conditions will be expired and then deleted. This number must be an integer larger than that specified for any of the transition operations.
              • Delete Fragments After (Days): After this number of days since the fragment generation, OBS will automatically delete fragments in the bucket.
              For example, on January 7, 2015, you saved the following files in OBS:
              • log/test1.log
              • log/test2.log
              • doc/example.doc
              • doc/good.txt
              On January 10, 2015, you saved another four files:
              • log/clientlog.log
              • log/serverlog.log
              • doc/work.doc
              • doc/travel.txt
              diff --git a/docs/obs/umn/obs_41_0054.html b/docs/obs/umn/obs_41_0054.html index 3e0b2fe3c..215ed2d27 100644 --- a/docs/obs/umn/obs_41_0054.html +++ b/docs/obs/umn/obs_41_0054.html @@ -35,7 +35,7 @@
            -

            Configuring Object Tags

            On OBS Console, you can add tags to an object when uploading it (see Procedure). You can also add tags to an existing object, as described in the following:

            +

            Configuring Object Tags

            On OBS Console, you can add tags to an object when uploading it (see Procedure). You can also add tags to an existing object, as described in the following:

            1. In the bucket list, click the bucket you want to operate. The Objects page is displayed.
            2. In the object list, click the name of the object you want to add tags to.
            3. Click the Tags tab. Then, click Add Tag in the upper left corner.
            4. In the Add Tag dialog box, enter a tag key and a tag value.

              diff --git a/docs/obs/umn/obs_faq_0014.html b/docs/obs/umn/obs_faq_0014.html index b3ce2707c..a6ab1a2c6 100644 --- a/docs/obs/umn/obs_faq_0014.html +++ b/docs/obs/umn/obs_faq_0014.html @@ -1,11 +1,11 @@

              Does OBS Support Resumable Transfer?

              -

              Resumable transfer is supported for all transfer methods except API.

              +

              The following table describes the resumable transfer support across OBS tools.

              -
              Table 1 Parameter description

              Parameter
              Table 1 Support for resumable transfer by different OBS tools

              OBS Tool

              +
              - diff --git a/docs/obs/umn/obs_faq_0027.html b/docs/obs/umn/obs_faq_0027.html index acaf79536..23c9004e4 100644 --- a/docs/obs/umn/obs_faq_0027.html +++ b/docs/obs/umn/obs_faq_0027.html @@ -3,7 +3,7 @@

              What Are the Application Scenarios of Lifecycle Management?

              You may configure lifecycle rules to:
              • Periodically delete logs that are only meant to be retained for a specific period of time (a week or a month).
              • Transition documents that are seldom accessed to the Warm or Cold storage class or delete them.
              -

              If you want to delete a large number of objects from a bucket, you can configure a lifecycle rule to automatically delete the expired objects. Table 1 lists the parameters for configuring such a lifecycle rule on OBS Console.

              +

              If you want to delete a large number of objects from a bucket, you can configure a lifecycle rule to automatically expire and delete the objects. Table 1 lists the parameters for configuring such a lifecycle rule on OBS Console.

              Table 1 Resumable transfer support across OBS tools

              OBS Tool

              Resumable Data Transfer

              +

              Resumable Transfer
              Table 1 Parameters for deletion upon expiration

              Parameter