Problem description
The Anti-DDoS instance is associated with more buckets than allowed.
Causes
An InitBucketAntiDDosInfo request was submitted to initialize bucket protection, but the Anti-DDoS instance specified in the x-oss-defender-instance header has already reached its bucket association limit.
Examples
The following request triggers this error because the Anti-DDoS instance cbcac8d2-4f75-4d6d-9f2e-c3447f73**** is already associated with the maximum allowed number of buckets:
PUT /?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-type: UnkownType
<AntiDDOSConfiguration>
<Cnames>
<Domain>abc1.example.cn</Domain>
<Domain>abc2.example.cn</Domain>
</Cnames>
</AntiDDOSConfiguration>Solutions
Make sure that the number of buckets associated with the Anti-DDoS instance specified by the x-oss-defender-instance header does not exceed the limit. You can obtain the maximum number of buckets allowed for an Anti-DDoS instance by checking the error message returned by OSS.
To manage DDoS protection settings in the OSS console, see OSS DDoS protection.