錯誤碼列表
更新時間 2024-11-08 17:33:06
最近更新時間: 2024-11-08 17:33:06
分享文章
本節主要介紹OOS API錯誤碼。
| 狀態碼 | 錯誤碼 | 錯誤信息 | 描述 |
|---|---|---|---|
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed. | 簽名頭格式不正確。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, missing Credential. | 簽名頭格式不正確,需補充Credential。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, missing SignedHeaders. | 簽名頭格式不正確,需補充SignedHeaders。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, missing Signature. | 簽名頭格式不正確,需補充Signature。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, the Credential is mal-formed, expecting 'YOUR-AKID/YYYYMMDD/REGION/SERVICE/aws4_request'. | 簽名頭中Credential格式不正確,格式應該為'YOUR-AKID/YYYYMMDD/REGION/SERVICE/aws4_request'。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, the date format 'date' is wrong, expecting 'YYYYMMDD'. | 簽名頭中date格式不正確,應該為'YYYYMMDD'。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, the region*'region'*?is wrong, expecting 'region'. | 簽名頭中區域名不正確。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, incorrect service 'service'. This endpoint belongs to 'endpoint'. | 簽名頭不正確,服務域名不對。 |
| 400 | AuthorizationHeaderMalformed | The authorization header is malformed, incorrect terminal 'terminal'. This endpoint uses 'aws4_request'. | 簽名頭不正確,endpoint應使用服務aws4_request。 |
| 400 | AuthorizationPostFormFieldsError | Form Post authentication version 4 requires the policy, x-amz-algorithm, x-amz-credential, x-amz-signature, x-amz-date form fields. | V4簽名中policy、x-amz-algorithm、x-amz-credential、x-amz-signature、x-amz-date不能為空。 |
| 400 | AuthorizationPostFormFieldsError | X-amz-algorithm only supports 'AWS4-HMAC-SHA256'. | v4簽名算法僅支持AWS4-HMAC-SHA256。 |
| 400 | AuthorizationPostFormFieldsError | X-amz-date must be in the ISO8601 Long Format "yyyyMMdd'T'HHmmss'Z'". | x-amz-date必須是ISO8601時間格式yyyyMMdd'T'HHmmss'Z'。 |
| 400 | AuthorizationQueryParametersError | X-Amz-Algorithm only supports 'AWS4-HMAC-SHA256'. | V4預簽名簽名算法僅支持AWS4-HMAC-SHA256。 |
| 400 | AuthorizationQueryParametersError | Query-string authentication version 4 requires the X-Amz-Algorithm, X-Amz-Credential, X-Amz-Signature, X-Amz-Date, X-Amz-SignedHeaders, and X-Amz-Expires parameters. | V4預簽名需要下列參數:X-Amz-Algorithm, X-Amz-Credential, X-Amz-Signature, X-Amz-Date, X-Amz-SignedHeaders, and X-Amz-Expires。 |
| 400 | AuthorizationQueryParametersError | X-Amz-Expires must be less than a week (in seconds); that is, the given X-Amz-Expires must be less than 604800 seconds. | V4預簽名生成時間不能超過7天。 |
| 400 | AuthorizationQueryParametersError | X-Amz-Expires must be non-negative. | V4預簽名過期時間不能為負數。 |
| 400 | AuthorizationQueryParametersError | X-Amz-Date must be in the ISO8601 Long Format "yyyyMMdd'T'HHmmss'Z'". | V4預簽名X-Amz-Date必須是ISO8601時間格式yyyyMMdd'T'HHmmss'Z'。 |
| 400 | AuthorizationQueryParametersError | Invalid credential date*"date". This date is not the same as X-Amz-Date:"date"*. | V4預簽名credential date與X-Amz-Date的日期需要保持一致。 |
| 400 | BadDigest | The Content-MD5 you specified did not match what we received. | Content-MD5不正確。 |
| 400 | BadRequest | Advance cut's position is out of image. | 剪切圖片時起始坐標超過原圖片尺寸。 |
| 400 | CanNotModifyMetadataLocation | Can not modifiy bucket metadata location. | 不能修改元數據位置。 |
| 400 | IdMismatch | Document ID does not match the specified configuration ID. | 請求頭和請求體中清單ID輸入不一致。 |
| 400 | IncompleteBody | You did not provide the number of bytes specified by the Content-Length HTTP header. | Content-Length配置的長度與實際收到的數據長度不符,請檢查后重發。 |
| 400 | InvalidArgument | User key must have a length greater than 0. | 表單上傳文件時Key項的值不能為空。 |
| 400 | InvalidArgument | The authorization header is invalid. Expected AccessKeyId:signature. | v2簽名格式不正確,應該為“AccessKeyId:signature”。 |
| 400 | InvalidArgument | x-amz-content-sha256 must be UNSIGNED-PAYLOAD, STREAMING-AWS4-HMAC-SHA256-PAYLOAD, or a valid sha256 value. | v4簽名x-amz-content-sha256必須是UNSIGNED-PAYLOAD, STREAMING-AWS4-HMAC-SHA256-PAYLOAD或者有效的sha256值。 |
| 400 | InvalidArgument | Unsupported authorization type. | v4簽名Authentication標頭只支持AWS4-HMAC-SHA256算法。 |
| 400 | InvalidArgument | Bucket POST must contain a field named 'AWSAccessKeyId'. If it is specified, please check the order of the fields. | 必須包含字段AWSAccessKeyId。 |
| 400 | InvalidArgument | Bucket POST must contain a field named 'policy'. If it is specified, please check the order of the fields. | 必須包含字段policy。 |
| 400 | InvalidArgument | Bucket POST must contain a field named 'signature'. If it is specified, please check the order of the fields. | 必須包含字段signature。 |
| 400 | InvalidArgument | POST requires exactly one file upload per request. | POST請求每次只能上傳一個文件。 |
| 400 | InvalidArgument | Bucket POST must contain a field named 'key'. If it is specified, please check the order of the fields. | 表單上傳中必須指定key。如果已指定,請檢查字段順序。 |
| 400 | InvalidArgument | If the TargetBucket element does not exist, the TargetPrefix element cannot exist either. | 在配置日志規則時,如果TargetBucket元素不存在,則TargetPrefix也不能存在。 |
| 400 | InvalidArgument | The target prefix exceeds 900 bytes. | 配置日志記錄規則時,TargetPrefix的長度不能超過900字節。 |
| 400 | InvalidArgument | ID length should not exceed allowed limit of 255. | 配置生命周期規則時,Rule ID長度不能超過255。 |
| 400 | InvalidArgument | At least one action needs to be specified in a rule. | 配置生命周期規則時,必須配置過期時間,Days或Date。 |
| 400 | InvalidArgument | 'Days' for [Transition|Expiration] action must be a positive integer. | 配置生命周期規則時,Days必須為正整數。 |
| 400 | InvalidArgument | Only one action can be specified in the rule. | 配置生命周期規則時,Days或Date只能存在一個。 |
| 400 | InvalidArgument | 'Date' must be at midnight GMT. | 配置生命周期規則時,Date必須為ISO8601格式,并且為UTC的零點。 |
| 400 | InvalidArgument | Invalid target Storage class for Transition action. | 指定的存儲類型無效。 |
| 400 | InvalidArgument | Default retention period must be a positive integer value. | 合規保留日期取值必須是正整數。 |
| 400 | InvalidArgument | Object lock configuration has been enabled and can not be disabled. | 合規保留已經開啟,不能關閉。 |
| 400 | InvalidArgument | Default retention period cannot be less than previously value. | 設置的合規保留時長不能短于上次設置的時長。 |
| 400 | InvalidArgument | MaxUploads should be between 1~1000. | max-uploads的取值范圍為[1,1000]。 |
| 400 | InvalidArgument | The length of delimiter must be 1. | delimiter長度不能超過1。并且只能是‘/’或空。 |
| 400 | InvalidArgument | MaxKeys should be between 1~1000. | 參數maxKeys取值范圍為[1,1000]。 |
| 400 | InvalidArgument | Max-parts should be between 1~1000. | max-parts取值范圍為[1,1000]。 |
| 400 | InvalidArgument | Part-number-marker must be an integer between 0 and 2147483647. | part-number-marker必須是整數,取值范圍是(0, 2147483647)。 |
| 400 | InvalidArgument | x-amz-limitrate invalid. The input should be positive integer. | x-amz-limitrate取值必須為正整數。 |
| 400 | InvalidArgument | Invalid request parameter: value. | 參數無效。 |
| 400 | InvalidArgument | The object size should be less than 5TiB. | 文件大小不能超過5TiB。 |
| 400 | InvalidArgument | The 'Expires' field format invalid. The 'Expires' header format invalid. | Expires格式不正確。 |
| 400 | InvalidArgument | The metadata size should be less than 2KiB. | 用戶自定義元數據不能超過2KiB。 |
| 400 | InvalidArgument | Insufficient information. Origin request header needed. | 跨域預檢時,請求頭不正確。 |
| 400 | InvalidArgument | Please enter an integer not less than -1. | CORS配置中MaxAgeSeconds取值為不小于-1的整數。 |
| 400 | InvalidArgument | Invalid Access-Control-Request-Method:value . | Access-Control-Request-Method無效。 |
| 400 | InvalidArgument | The x-amz-copy-source-range value must be of the form bytes=first-last where first and last are the zero-based offsets of the first and last bytes to copy. | x-amz-copy-source-range形式必須為bytes=first -last,其中第一個和最后一個都是以零為基礎開始的偏移量。 |
| 400 | InvalidArgument | Invalid protocol, protocol can be http or https. If not defined the protocol will be selected automatically. | 指定的http協議值不正確。 |
| 400 | InvalidArgument | The provided host name contains?N characters. The maximum allowed redirect page size is 1024 characters. | HostName包含的字符個數大于1024。 |
| 400 | InvalidArgument | The provided home page contains N characters. The maximum allowed home page size is 1024 characters. | 首頁包含的字符個數大于1024。 |
| 400 | InvalidArgument | The provided error page contains?N characters. The maximum allowed error page size is 1024 characters. | 錯誤頁包含的字符個數大于1024。 |
| 400 | InvalidArgument | The provided replacement contains?N?characters. The maximum allowed replacement size is 1024 characters. | 重定向規則中ReplaceKeyPrefixWith或者ReplaceKeyWith包含的字符個數大于1024。 |
| 400 | InvalidArgument | The provided prefix contains?N?characters.The maximum allowed prefix size is 1024 characters. | 重定向規則中KeyPrefixEquals包含的字符個數大于1024。 |
| 400 | InvalidArgument | RedirectAllRequestsTo cannot be provided in conjunction with other Routing Rules. | 重定向所有請求不能與其他規則同時存在。 |
| 400 | InvalidArgument | The IndexDocument Suffix cannot contain the "/" character. | 索引頁配置不能包含斜杠“/”。 |
| 400 | InvalidArgument | The IndexDocument Suffix cannot be blank. | 索引頁配置不能為空。 |
| 400 | InvalidArgument | Missing required key 'Redirect'. | 缺少必需的參數Redirect。 |
| 400 | InvalidArgument | The ErrorDocument Key cannot be blank. | 錯誤頁配置不能為空。 |
| 400 | InvalidArgument | The HostName cannot be blank. | HostName配置不能為空。 |
| 400 | InvalidArgument | The HostName cannot contain the "/" character. | HostName不能包含斜杠“/”。 |
| 400 | InvalidArgument | The provided HTTP error code (value) is not valid. Valid codes are 4XX or 5XX. | 重定向條件中的HttpErrorCodeReturnedEquals不是有效值。 |
| 400 | InvalidArgument | Missing required key 'HostName'. | 缺少必需的參數HostName。 |
| 400 | InvalidArgument | The HostName cannot contain spaces. | HostName配置不能包含空格。 |
| 400 | InvalidArgument | A value for IndexDocument Suffix must be provided if RedirectAllRequestsTo is empty. | 重定向所有請求未配置時,索引文件必須配置。 |
| 400 | InvalidArgument | The destination bucket does not belong to you. | 目的Bucket為他人的Bucket。 |
| 400 | InvalidArgument | Invalid Format value. | 清單的格式不正確,取值只能為CSV。 |
| 400 | InvalidArgument | Invalid Field value. | Field值填寫錯誤。 |
| 400 | InvalidArgument | The maximum size of a Destination/Prefix is 512. | Prefix最大長度為512。 |
| 400 | InvalidArgument | The maximum size of a Filter/Prefix is 1024. | Prefix最大長度為1024。 |
| 400 | InvalidArgument | IsEnabled value expects true or false. | IsEnabled的取值只能為true或false。 |
| 400 | InvalidArgument | Frequency value expects Daily or Weekly. | Frequency的取值只能為Daily或Weekly。 |
| 400 | InvalidArgument | Schedule/Frequency missing. | Frequency未填寫。 |
| 400 | InvalidArgument | InventoryConfiguration/Destination/OOSBucketDestination/Bucket missing. | 清單的目的Bucket未填寫。 |
| 400 | InvalidArgument | IsEnabled missing. | IsEnabled缺失。 |
| 400 | InvalidArgument | InventoryConfiguration/Destination/OOSBucketDestination/Format missing. | 清單的輸出格式缺失。 |
| 400 | InvalidArgument | Invalid id. | Id無效。 |
| 400 | InvalidArgument | Id missing. | 請求體中的id缺失。 |
| 400 | InvalidArgument | The type of 'IsAccessTime' must be Boolean. | IsAccessTime取值應為布爾型,true或者false。 |
| 400 | InvalidArgument | 'Days' in the Expiration action for prefix 'prefix ' must be greater than 'Days' in the Transition action. | 兩生命周期規則重疊時,過期刪除天數必須大于過期轉儲天數。 |
| 400 | InvalidBucketCorsConfigure | The XML you provided is not valid. | XML無效。 |
| 400 | InvalidBucketName | The bucket name is:name . | Bucket名字無效。 |
| 400 | InvalidConfigurationId | The specified configuration id is invalid. | 請求頭的清單ID未填寫。 |
| 400 | InvalidLocationConstraint | The specified location constraint is not valid. | 指定的數據位置無效。 |
| 400 | InvalidObjectName | The object name is:name . | 文件名字無效。 |
| 400 | InvalidOOSDestinationBucket | Invalid Bucket ARN. | Bucket ARN的格式不正確。 |
| 400 | InvalidOOSDestinationBucket | Invalid Bucket Name:bucketname . | 清單輸出的目的Bucket不存在。 |
| 400 | InvalidPart | One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag. | 一個或者多個指定片段無法找到,片段可能沒有被上傳,或者指定的ETag值跟片段的ETag值不匹配。 |
| 400 | InvalidPartNumber | Part number must be an integer between 1 and 10000. | 參數PartNumber的取值是[1, 10000]。 |
| 400 | InvalidPartOrder | The list of parts was not in ascending order. The parts list must be specified in order by part number. | 分片片段列表沒有按升序排列。片段列表必須根據分片號按順序排列。 |
| 400 | InvalidPartSize | Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MiB in size, except the last part. | 合并分片文件時,只允許最后一片小于5MiB,其他分片至少5MiB。 |
| 400 | InvalidPolicyDocument | Invalid Policy: JSON invalid:value . | 策略無效,不是標準的json格式。 |
| 400 | InvalidPolicyDocument | Invalid according to Policy: Extra input fields:value . | 策略無效,輸入了額外的字段。 |
| 400 | InvalidPolicyDocument | Policy could not be parsed as a valid JSON string. | 策略必須是json格式。 |
| 400 | InvalidPolicyDocument | Policy is missing required element - Statement. | 策略必須配置Statement。 |
| 400 | InvalidPolicyDocument | Policy is missing required element - Principal. | 策略必須配置Principal。 |
| 400 | InvalidPolicyDocument | Policy element has invalid value - Principal. | 策略配置的Principal值無效。 |
| 400 | InvalidPolicyDocument | Policy is missing required element - Resource. | 策略必須配置Resource元素。 |
| 400 | InvalidPolicyDocument | Policy is missing required element - Resource content. | 策略的Resource元素必須賦值。 |
| 400 | InvalidPolicyDocument | Policy has invalid resource -resource . | 策略配置的Resource無效。 |
| 400 | InvalidPolicyDocument | Policy has an invalid condition key -key . | 策略配置的condition key無效。 |
| 400 | InvalidPolicyDocument | No such condition type -type. | 策略配置的condition type無效。 |
| 400 | InvalidPolicyDocument | Action does not apply to any resource(s) in statement. | 策略配置的Action無效。 |
| 400 | InvalidPolicyDocument | Policy is missing required element - Effect. | 策略必須配置Effect。 |
| 400 | InvalidPolicyDocument | Policy element has invalid value - Effect :Effect . | 策略配置的Effect無效。 |
| 400 | InvalidPolicyDocument | Policy element has invalid value - Version :Version . | 策略配置的Version無效。 |
| 400 | InvalidRedirectLocation | The website redirect location must be non-empty. | x-amz-website-redirect-location頭不能為空。 |
| 400 | InvalidRedirectLocation | The website redirect location must have a prefix of '//' or '//' or '/'. | x-amz-website-redirect-location必須有前綴'//'、'//'或'/'.。 |
| 400 | InvalidRedirectLocation | The length of website redirect location cannot exceed 2,048 characters. | x-amz-website-redirect-location長度不能超過2048。 |
| 400 | InvalidRequest | Missing required header for this request: x-amz-content-sha256. | v4簽名必須攜帶x-amz-content-sha256。 |
| 400 | InvalidRequest | Missing required header for this request: Content-MD5. | 請求頭必須包含Content-MD5。 |
| 400 | InvalidRequest | Please reduce your request rate. | 請降低您的請求頻率。 |
| 400 | InvalidRequest | The operation failed, please change a resource pool and try again. | 請換其他資源池或者重試。 |
| 400 | InvalidRequest | This copy request is illegal because it is trying to copy an object to itself without changing the object's metadata or storage class. | 復制文件時必須修改元數據或者存儲類型。 |
| 400 | InvalidRequest | x-amz-limitrate invalid.The input should be positive integer. | x-amz-limitrate只能是正整數。 |
| 400 | InvalidRequest | The source object size cannot be smaller than 5 GiB. | 如果源文件取range進行拷貝,源文件大小不能小于5G。 |
| 400 | InvalidRequest | You can only define ReplaceKeyPrefix or ReplaceKey but not both. | ReplaceKeyPrefix或者ReplaceKey不能同時存在。 |
| 400 | InvalidRequest | Condition cannot be empty. To redirect all requests without a condition, the condition element shouldn't be present. | Condition配置不能為空。不帶條件的情況下,重定向所有請求不應該出現condition元素。 |
| 400 | InvalidRequest | The maximum size of a prefix is 1024. | 配置生命周期規則時,前綴的最大長度為1024。 |
| 400 | InvalidRequest | Number of lifecycle rules should not exceed allowed limit of 1000 rules. | 同一Bucket配置的生命周期規則不能超過1000條。 |
| 400 | InvalidRequest | Rule ID must be unique. Found same ID for more than one rule. | 配置生命周期規則時,Rule ID必須唯一。 |
| 400 | InvalidRequest | Found two rules with same prefix 'prefix ' for same action type [Transition|Expiration]. | 同一Bucket的兩條生命周期規則不能有相同的prefix。 |
| 400 | InvalidRequest | Found overlapping prefixes 'prefix ' and ' prefix ' for same action type [Transition|Expiration]. | 同一Bucket的兩條生命周期規則不能有前綴重疊的情況。 |
| 400 | InvalidRequest | Found overlapping prefixes 'prefix ' and '' for same action type [Transition|Expiration]. | 同一Bucket的兩條生命周期規則不能同時存在有前綴和無前綴規則。 |
| 400 | InvalidStorageClass | The storage class you specified is not valid. | x-amz-storage-class無效。 |
| 400 | InvalidStorageClass | Can not specify the storage class. | 未合并的分段文件不能指定x-amz-storage-class進行拷貝。 |
| 400 | InvalidTargetBucketForLogging | The target bucket name is:name. | 日志記錄規則時,目標Bucket不存在或者無目標Bucket的權限。 |
| 400 | MalformedPOSTRequest | The body of your POST request is not well-formed multipart/form-data. | POST表單請求中content-type配置的boundary格式不規范。 |
| 400 | MalformedXML | CORS Rule is empty. | CORS Rule不能為空。 |
| 400 | MalformedXML | The number of CORS Rules you provided cannot exceed 100. | CORS Rules個數不能超過100。 |
| 400 | MalformedXML | The length of CORS Rule ID you provided cannot exceed 255 characters. | CORS Rule ID長度不能超255個字符。 |
| 400 | MalformedXML | AllowedOrigin does not exist. | CORS配置中AllowedOrigin不存在。 |
| 400 | MalformedXML | AllowedMethod does not exist. | CORS配置中AllowedMethod不存在。 |
| 400 | MalformedXML | AllowedOrigin "value" can not have more than one wildcard. | CORS配置中AllowedOrigin最多只能攜帶一個通配符。 |
| 400 | MalformedXML | AllowedHeader "value" can not have more than one wildcard. | CORS配置中AllowedHeader最多只能攜帶一個通配符。 |
| 400 | MalformedXML | ExposeHeader "value" contains wildcard. We currently do not support wildcard for ExposeHeader. | CORS配置中ExposeHeader不能攜帶通配符。 |
| 400 | MalformedXML | CORS Rule ID is not unique. | CORS Rule ID必須是唯一的。 |
| 400 | MalformedXML | The XML you provided was not well-formed or did not validate against our published schema. | XML格式不正確。 |
| 400 | MaxRequestBodyLengthExceeded | Your request was too big, the maximum size is %s . | 請求體長度太長。 |
| 400 | MissingRequestBodyError | Request Body is empty. | 請求body體為空。 |
| 400 | NoSuchUpload | The specified upload does not exist. The uploadId may be invalid, or the upload may have been aborted or completed. | 指定的分片上傳過程不存在,上傳ID可能非法,分片上傳過程可能被終止或者已經完成。 |
| 400 | PutObjectTooFast | Upload:value is updated too fast. | 同一文件并發上傳過快。 |
| 400 | TooManyBuckets | You have attempted to create more buckets than allowed. | Bucket數量已經到達上限。 |
| 400 | TooManyConfigurations | You are attempting to create a new configuration but have already reached the 10-configuration limit. | 超出清單配置規則的數量限制,每個Bucket最多配置10條清單。 |
| 403 | InvalidAccessKeyId | InvalidAccessKeyId. | AccessKeyId無效。 |
| 403 | InvalidAccessKeyId | The AccessKeyId is invalid. | AccessKeyId被禁用。 |
| 403 | InvalidAccessKeyId | The specified accessKey:accessKey does not exist. | 臨時密鑰不存在,需重新申請。 |
| 403 | AccessDenied | Please use primary access key. | 需要使用主密鑰。 |
| 403 | AccessDenied | Non-primary key can not list without prefix or prefix is not start with access key. | 非主密鑰只能list以自己access key為前綴的文件。 |
| 403 | AccessDenied | Non-primary key can not operate bucket. | 非主密鑰,不能操作該Bucket。 |
| 403 | AccessDenied | Non-primary key can not operate object that not start with access key. | 非主密鑰只能操作以自己access key為前綴的文件。 |
| 403 | AccessDenied | The secret token is expired, expiration:value . | secret token過期。 |
| 403 | AccessDenied | The OOS service has been closed due to overdue payment. If the overdue payment exceed 15 days, the data will be deleted. Please recharge it in time. | 由于逾期付款,OOS服務已關閉。如果逾期付款超過15天,數據將被刪除。請及時充值。 |
| 403 | AccessDenied | OOS authentication requires a valid Date or x-amz-date header. | OOS 簽名頭中需要攜帶Date或x-amz-date。 |
| 403 | AccessDenied | OOS authentication requires a valid Date or x-amz-date header, expecting" YYYYMMDD'T'HHMMSS'Z'". | OOS 簽名頭需要攜帶正確格式的Date或x-amz-date,格式為YYYYMMDD'T'HHMMSS'Z'。 |
| 403 | AccessDenied | Invalid according to Policy: Policy expired. | v4簽名的x-amz-date時間不能超過7天。 |
| 403 | AccessDenied | Invalid according to Policy: Policy Condition failed:xxx | 簽名策略不對。 |
| 403 | AccessDenied | Query-string authentication requires the Signature, Expires and AWSAccessKeyId parameters. | V2預簽名需要攜帶以下參數:Signature、Expires、AWSAccessKeyId。 |
| 403 | AccessDenied | Invalid date (should be seconds since epoch):date . | 過期時間需要精確到秒。 |
| 403 | AccessDenied | Request has expired. | 請求過期。 |
| 403 | AccessDenied | Anonymous access is forbidden for this operation. | 匿名用戶禁止此操作。 |
| 403 | AccessDenied | The user's permission is not enough. | 用戶權限不足。 |
| 403 | AccessDenied | You do not have permission to this resource pool, please try another resource pool. | 沒有該資源池的權限,請使用其他資源池。 |
| 403 | AccessDenied | CORSResponse: This CORS request is not allowed. This is usually because the evalution of Origin, request method / Access-Control-Request-Method or Access-Control-Request-Headers are not whitelisted by the resource's CORS spec. | 跨域預檢請求沒有通過CORS規則校驗。請檢查Origin、Access-Control-Request-Method、Access-Control-Request-Headers是否在CORS列表的白名單中。 |
| 403 | AccessDenied | CORSResponse: CORS is not enabled for this bucket. | 此Bucket未配置CORS。 |
| 403 | AccessDenied | Access denied by bucket policy. | 受Bucket Policy的規則影響,被顯示拒絕。 |
| 403 | AccessDenied | Access denied by bucket policy or anonymous access is forbidden. | 匿名訪問被拒絕,或者被Bucket Policy規則隱式拒絕。 |
| 403 | AccessDenied | User:useris not authorized to perform:actionon resource: resource . | 沒有權限訪問此資源。 |
| 403 | AccessDenied | The user does not belong to the region. | 沒有此資源池的上傳權限,請更換其他資源池重試。 |
| 403 | AccessDenied | You do not have permission to request the value data region. Please change the data region for the bucket and try again. | Bucket下配置的數據位置都已失效,請重新配置,或者修改為可以自動調度。 |
| 403 | AccessDenied | You are not allowed to set the public-read-write permission for the bucket. | 您不具備將容器設置為公有的權限,請聯系天翼云客服協助開通此功能。 |
| 403 | AccessDenied | You are not allowed to grant public-write permission to anonymous users. | 您不可以向匿名用戶授予寫權限,請聯系天翼云客服協助開通此功能。 |
| 403 | AccessDenied | Make sure that bucket's permissions are not private before using the static website hosting feature. | 在使用靜態網站托管功能之前,請確保Bucket權限不是私有。 |
| 403 | Forbidden | CORSResponse: Bucket not found. | 如果是pre-flight CORS請求,Bucket必須存在。 |
| 403 | IllegalObject | The object "bucket/object " is illegal, forbid copy. | 源文件是非法文件,不允許拷貝。 |
| 403 | RequestTimeTooSkewed | The difference between the request time and the server's time is too large. | 客戶端時間和服務器端時間相差超過15分鐘。 |
| 403 | SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your key and signing method. | 簽名計算錯誤,需按OOS的簽名規則,請檢查客戶端簽名計算方法。 |
| 403 | SignatureDoesNotMatch | The authorization type is malformed. | V2簽名頭不是AWS開頭,或者V4簽名頭不是AWS4-HMAC-SHA256。 |
| 403 | SignatureDoesNotMatch | Invalid order of SignedHeaders. | V4簽名SignedHeasers需按字典序排序 |
| 404 | MalformedContinuationToken | The continuation-token you provided invalid. | continuation-token的值不正確。 |
| 404 | NoSuchBucket | The resource you requested does not exist. | 請求的Bucket不存在。 |
| 404 | NoSuchBucket | The request bucketname is?name. | 復制文件時源Bucket不存在。 |
| 404 | NotSuchBucketPolicy | The bucket policy configuration does not exist. | 此Bucket Policy配置不存在。 |
| 404 | NoSuchCORSConfiguration | The CORS configuration does not exist. | Bucket下沒有配置CORS。 |
| 404 | NoSuchLifecycleConfiguration | The lifecycle configuration does not exist. | 生命周期規則配置不存在。 |
| 404 | NoSuchKey | The resource you requested does not exist. | 請求文件不存在。 |
| 404 | NoSuchKey | An Error Occurred While Attempting to Retrieve a Custom Error Document. | 嘗試檢索自定義錯誤文檔時發生錯誤。 |
| 404 | NoSuchWebsiteConfiguration | The specified bucket does not have a website configuration. | Bucekt未開啟website功能。 |
| 404 | ObjectLockConfigurationNotFoundError | Object lock configuration does not exist for this bucket. | 此Bucket不存在合規保留配置。 |
| 405 | MethodNotAllowed | The specified location constraint is not valid. | 指定的數據位置無效。 |
| 405 | MethodNotAllowed | The specified method is not allowed against this resource. | 此資源不允許使用該方法。 |
| 409 | BucketAlreadyExists | BucketAlreadyExists. | Bucket名字已存在,請更換名字。 |
| 409 | BucketNotEmpty | The bucket you tried to delete is not empty. | Bucket非空,不能刪除。 |
| 411 | MissingContentLength | You must provide the Content-Length HTTP header. | 需要提供Content-Length消息頭。 |
| 412 | PreconditionFailed | Bucket post must be of the enclosure-type multipart/form-data. | POST表單的content-type請求頭不正確。 |
| 412 | PreconditionFailed | The pre-conditions x-amz-copy-source-if-modified-since you specified did not hold. | 預處理條件下,指定的x-amz-copy-source-if-modified-since不匹配。 |
| 503 | ServiceUnavailable | Service is busy.Please try again. | 服務器繁忙,請重試。 |
| 503 | SlowDown | Please reduce your request rate. | 請降低請求頻率。 |