Initializing obsutil

Prerequisites

• The obsutil has been downloaded. For details, see Downloading Software.
• The access keys (AK and SK) have been obtained. For details, see 3 in Preparing the Environment.

Procedure

1. Run the following commands to initialize obsutil:

   chmod +x obsutil

   ./obsutil config -i=ak -k=sk -e=endpoint

   • ak: indicates the tenant access key, that is, the AK in Creating Access Keys (AK and SK).
   • sk: indicates the tenant secret key, that is, the SK in Creating Access Keys (AK and SK).
   • endpoint: The IP address of an endpoint varies from region to region. Table 1 lists OBS endpoint IP addresses. For more information about OBS endpoints, see Regions and Endpoints.

     Table 1 Endpoints

     Region Name	Endpoint Region	Endpoint
     CN-Hong Kong	ap-southeast-2	obs.ap-southeast-1.myhuaweicloud.com
     AP-Bangkok	ap-southeast-1	obs.ap-southeast-2.myhuaweicloud.com
     AF-Johannesburg	af-south-1	obs.af-south-1.myhuaweicloud.com

     

     • After running the preceding commands, a configuration file .obsutilconfig is automatically generated in the same directory of the user who executes obsutil commands (the ~ directory in Linux). .obsutilconfig contains all the configuration information of obsutil. For details about the parameters, see Parameter Description.
     • The .obsutilconfig file contains user AK and SK information. To prevent key leakage, the obsutil file is hidden by default. You can run the ls -a command in the directory of the user who executes obsutil commands to view the file.

2. After the configuration is complete, you can run the following command to check the connectivity:

   ./obsutil ls -s

   Check the command output.

   • If the command output contains Bucket number is:, the configuration is correct.
   • If the command output contains Http status [403], the access keys are incorrectly configured.
   • If the command output contains A connection attempt failed, the OBS service cannot be connected. Check whether the network is normal.