# Inspur Cloud (浪潮云)

> Inspur Cloud is the public-cloud arm of Chinese IT conglomerate Inspur Group, operating from
> cloud.inspur.com across three regions — cn-north-3 (华北三), cn-south-1 (华南一) and cn-east-1
> (华东一). It documents 94 products, of which at least 16 publish a public HTTP API reference
> covering compute, bare metal, block storage, backup, VPC networking, elastic IP, load
> balancing, IAM, MySQL, time-series database, container engine, blockchain, conversational AI,
> IoT and an S3-compatible object storage service.

## What an agent needs to know first

- There is **no machine-readable contract**. No OpenAPI, Swagger, AsyncAPI, GraphQL SDL, JSON
  Schema, Protobuf or WSDL is published anywhere. All reference material is hand-written
  GitBook HTML in Simplified Chinese. `/openapi.json`, `/swagger.json`, `/v2/api-docs` and
  `/api-docs` return 404 or 403 on every host (probed 2026-08-23).
- There is **no MCP server, no agent card, no llms.txt and no /.well-known/ surface** of any
  kind. Every well-known path returns 404.
- The documented API endpoint hosts serve **expired TLS certificates**
  (ecs.cn-north-3.inspurcloudapi.com expired 2020-12-09; ecs.cn-east-1.inspurcloudapi.com
  expired 2022-07-08). A client performing normal certificate validation cannot connect.
- There is **no idempotency mechanism**. The Nonce / x-random values are replay prevention,
  which stops a retried request from being accepted rather than making it safe to retry.
- There is **no rate limit documentation and no rate-limit response header**. Quota
  exhaustion surfaces as an error code inside the response body, not as a status code.
- This file was generated by API Evangelist from the provider's public documentation. Inspur
  Cloud does not publish an llms.txt.

## Authentication

Two schemes, documented at https://console1.cloud.inspur.com/document/iam/9-signate.html

- **AK/SK signature** (all platform APIs). Headers: `x-secret-id` (AccessKey ID),
  `x-sign-algorithm` (sha1 | md5 | sha256), `x-time` (13-digit ms epoch), `x-random` (nonce),
  `x-sign` (signature). The signed string is httpMethod \n (x-time + x-random + SK) \n
  (sorted-query URI) \n (hex MD5 of the body), hashed, hex-encoded and base64-encoded.
- **IAM bearer token**. `Authorization: Bearer <token>`, obtained from the GetToken interface.
- **OSS** uses the Amazon S3 Signature Version 2 construction with an `x-oss-` header prefix.

## API references

- ECS elastic compute (51 ops): https://console1.cloud.inspur.com/document/ecs/5-API/5.1-1-api-overview.html
- CPS bare metal (14 ops): https://console1.cloud.inspur.com/document/cps/5-API/5.1-1-api-overview.html
- EBS block storage (52 ops): https://console1.cloud.inspur.com/document/ebs/5-API/5.1-1-api-overview.html
- CBS backup (10 ops): https://console1.cloud.inspur.com/document/cbs/5-API/5.1-1-api-overview.html
- VPC networking (26 ops): https://console1.cloud.inspur.com/document/vpc/5-API/5.1-1-api-overview.html
- EIP elastic IP (27 ops): https://console1.cloud.inspur.com/document/eip/5-API/5.1-1-api-overview.html
- IPTS IPv6 translation (6 ops): https://console1.cloud.inspur.com/document/ipts/5-API/5.1-1-api-overview.html
- SLB load balancing (40 ops): https://console1.cloud.inspur.com/document/slb/5-API/5.1-1-api-overview.html
- IAM identity (59 ops): https://console1.cloud.inspur.com/document/iam/5-API/5.1-1-api-overview.html
- RDS for MySQL (57 ops): https://console1.cloud.inspur.com/document/rds/5-API/1.1-1-api-overview.html
- TSDB time series (67 ops): https://console1.cloud.inspur.com/document/tsdb/5-API/5.1-1-api-overview.html
- ICE/CKS containers (34 ops): https://console1.cloud.inspur.com/document/cks/9-opencontainer-api/9.1-1-container-menu.html
- OSS object storage, S3-compatible (34 ops): https://console1.cloud.inspur.com/document/oss/5-API/5.1.2-api-overview.html
- IBaaS blockchain (5 ops): https://console1.cloud.inspur.com/document/ibaas/docs/api/5-API/5.1-1-api-overview.html
- ACS consortium chain (6 ops): https://console1.cloud.inspur.com/document/acs/docs/api/5-API/5.1-1-api-overview.html
- IBot conversational AI (4 ops): https://console1.cloud.inspur.com/document/ibot/5-API-api-overview.html
- IoT platform: https://console1.cloud.inspur.com/document/iot/5-API/IotOpenAPI.html
- API Gateway product: https://console1.cloud.inspur.com/document/apig/4-operations-guide.html

## API hosts

- ECS: ecs.cn-north-3 / ecs.cn-south-1 / ecs.cn-east-1 .inspurcloudapi.com
- CPS: cps.cn-north-3.inspurcloudapi.com
- EBS: ebs.cn-north-3 / ebs.cn-south-1 .inspurcloudapi.com
- CBS: cbs.cn-north-3.inspurcloudapi.com
- VPC: vpc.cn-north-3 / vpc.cn-south-1 .inspurcloudapi.com
- EIP and IPTS: eip.cn-north-3.inspurcloudapi.com
- IAM: iam.inspurcloudapi.com (one global host for all regions)
- RDS MySQL: mysql.cn-north-3.inspurcloudapi.com
- OSS: oss.cn-north-3 / oss.cn-south-1 .inspurcloudoss.com
- SLB, TSDB, ICE/CKS, IBaaS, ACS and IBot do not publish a service host in their references.

## Request and response shape

- Compute and network APIs are RPC over query parameters: `https://<host>?Action=<name>&Version=<date>&Timestamp=&Nonce=&Format=json|xml`. ECS Version is `2019-01-31`. The documented default Format is XML.
- IAM, TSDB and IBot are resource-oriented REST under `/auth/v1`, `/tsdb/v1` and `/qa/bot/sdk`, with non-CRUD verbs expressed as `/action/<verb>`.
- Response envelope: `RequestId`, `Code`, `Data`, `Message`. Success codes 200, 201, 202, 204.
- Errors are dotted numeric codes in the body — 101.x ECS, 104.x CPS, 107.x SLB, 003.x IAM — not RFC 9457 problem+json. OSS returns the S3 XML Error envelope with a real HTTP status.
- Long-running operations return a task; poll the instance status table (20 states).

## SDKs

Only Object Storage and IoT ship first-party SDKs.

- Python: `pip install inspurcloud-oss-sdk` — v1.1.2, published 2024-02-01, supports Python 3.6/3.7 only
- Java: direct JAR download, inspur-cloud-oss-sdk-4.0.19.jar, last modified 2023-05-12; not on Maven Central
- C++: https://github.com/OpenInspur/inspur-oss-cpp-sdk — source only, last pushed 2020-08-13
- C (IoT device SDK): download from the authenticated IoT console; MQTT over mbedTLS
- No SDK exists for compute, networking, IAM or the databases.

## Third-party S3 clients that work against OSS

S3cmd, S3Browser and Rclone are documented by the provider as supported ways to use OSS.

## Operational surface

- SLA: per-product documents under /document/declaration/protocol/rank/. ECS commits 99.95% monthly per-instance availability. OSS claims 99.99% availability and twelve nines durability.
- Status page: none. Support is a hotline, cloudkf@inspur.com, and an authenticated ticket queue at https://bss.cloud.inspur.com/workorders/list
- Changelog: per-product 发布记录 pages. The most recent entry anywhere is 2023-06-01 (OSS); API Gateway ends at 2022-03-22; the ECS API update history has one row, 2019-01-31.
- Deprecation policy: none published. No Sunset or Deprecation headers.
- Vulnerability disclosure: Inspur Group PSIRT, sec@inspur.com, PGP key 0xC483FD05 — https://www.inspur.com/lcjtww/2312126/2432763/index.html. No bug bounty, no security.txt.

## Commercial

- Two billing modes: 包年包月 prepaid (monthly/annual, cheaper, upgrade-only) and 按需计费 pay-as-you-go (per-second metering, hourly settlement, ~3-4x prepaid unit price, CNY 100 minimum balance).
- Unit prices are not published publicly; they appear inside the authenticated purchase flow. One exception: standard cloud disk at CNY 0.35 per GiB per month.
- No free tier and no free trial.
- Pricing model: https://console1.cloud.inspur.com/document/ecs/2-product-pricing.html
- Terms: https://console1.cloud.inspur.com/document/declaration/protocol/client/client.html
- Privacy: https://cloud.inspur.com/privacy-policy/index.html
- Console / sign-up: https://console1.cloud.inspur.com/