0038-00000004

Problem description

The specified Anti-DDoS instance in the request does not exist.

Causes

You initiated an OSS DDoS protection related request, such as UpdateBucketAntiDDosInfo, but used the x-oss-defender-instance header to specify an Anti-DDoS instance ID that does not exist.

Examples

For example, you initiate the following request:

POST /?antiDDos HTTP/1.1
Date:  GMT Date
Host: BucketName.oss-cn-hangzhou.aliyuncs.com
Authorization: SignatureValue
x-oss-defender-instance: cbcac8d2-4f75-4d6d-9f2e-c3447f73****
x-oss-defender-status: Init
<AntiDDOSConfiguration>
  <Cnames>
    <Domain>abc1.example.cn</Domain>
    <Domain>abc2.example.cn</Domain>
  </Cnames>
</AntiDDOSConfiguration>

An error is returned because the Anti-DDoS instance ID specified by the x-oss-defender-instance header does not exist.

Solutions

Make sure that the Anti-DDoS instance ID specified by the x-oss-defender-instance header exists. You can call the InitUserAntiDDosInfo operation to create an Anti-DDoS instance. The following code provides an example.

PUT /?antiDDos HTTP/1.1
Date:  GMT Date
Host: oss-cn-hangzhou.aliyuncs.com
Authorization: SignatureValue

The x-oss-defender-instance header in the response is the created Anti-DDoS instance.

For more information about how to configure DDoS protection in the OSS console, see OSS DDoS protection.

References

UpdateBucketAntiDDosInfo