tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Bucket Binding to Cloud Infinite

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-06 17:29:50

Description

This interface is used to activate the Cloud Infinite service and bind the specified existing Bucket on COS to the Cloud Infinite service.
After activation, you can directly use the Cloud Infinite Image Processing synchronous request API, CR synchronous request API, and Content Moderation API. To use other capabilities, separate binding is required.
For other features of the Bucket such as querying, modifying, and so on, please use the COS API.

Authorization Description

When a sub-account is used, it is necessary to add the ci:CreateCIBucket permission to the action in the authorization policy. For all operation interfaces supported by Cloud Infinite, see action.

Fee Instructions

Using this API to activate Cloud Infinite or bind the Cloud Infinite service to a Bucket will not incur any fees. After actual usage occurs, Cloud Infinite will be billed based on usage. For detailed billing information, see Billing Overview.

Request

Request sample

PUT / HTTP/1.1
Host: <BucketName-APPID>.ci.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Note:
Authorization: Auth String. For details, see the Request Signature documentation.

Request header

This API only uses common request headers. For details, see Common Request Headers.

Request body

The request body is empty.

Response

Response Headers

This API only returns common response headers. For details, see Common Response Headers.

Response Body

The response body returns application/xml data. The content containing complete node data is displayed as follows:
<Response>
<RequestId>NjJmMzRlZGZfOTBmYTUwNjRfNzI0XXXX</RequestId>
<CIBucket>
<BucketId>test-1234567890</BucketId>
<Region>ap-chongqing</Region>
</CIBucket>
</Response>
The specific data content is as follows:
Node Name (Keyword)
Parent Node
Description
Type
Response
None.
Container for saving results
Container
Response content of the Container node:
Node Name (Keyword)
Parent Node
Description
Type
RequestId
Response
unique request ID
String
CIBucket
Response
Bucket Information
Container
Content of the Container node CIBucket:
Node Name (Keyword)
Parent Node
Description
Type
BucketId
Response.CIBucket
Bucket ID
String
Region
Response.CIBucket
Region
String

Error Codes

This request operation has no special error messages. For common error messages, see Error Codes.

Practical Case

Request:

POST / HTTP/1.1
Authorization:q-sign-algorithm=sha1&q-ak=************************************&q-sign-time=1497530202;1497610202&q-key-time=1497530202;1497610202&q-header-list=&q-url-param-list=&q-signature=**************************************************
Host:test-1234567890.ci.ap-chongqing.myqcloud.com
Content-Length: 0

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 197
Connection: keep-alive
Date: Mon, 28 Jun 2022 15:23:12 GMT
Server: tencent-ci
x-ci-request-id: NjJmMzRlZGZfOTBmYTUwNjRfNzI0XXXX

<Response>
<RequestId>NjJmMzRlZGZfOTBmYTUwNjRfNzI0XXXX</RequestId>
<CIBucket>
<BucketId>test-1234567890</BucketId>
<Region>ap-chongqing</Region>
</CIBucket>
</Response>


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan