Creates an OpenSearch application.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
opensearch:CreateAppGroup | create |
|
| none |
Request syntax
POST /v4/openapi/app-groups HTTP/1.1
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
body | object | No | The request body. | |
name | string | No | The name of the application. | jmbon_analyzer |
chargeType | string | No | The billing method. Valid values:
| POSTPAY |
type | string | No | The type of the application. Valid values:
| enhanced |
resourceGroupId | string | No | The ID of the resource group to which the instance belongs. | rg-acfm2ij6pwxsvua |
quota | object | No | The quota. | |
docSize | integer | No | The storage capacity. Unit: GB. | 1 |
computeResource | integer | No | The computing resources. Unit: logical computing unit (LCU). | 20 |
spec | string | No | The specifications. Valid values:
| opensearch.share.common |
Request body
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
name | String | Yes | "my_app" | The name of the application. |
type | String | Yes | "standard" | The type of the application.Valid values: standardand enhanced. |
quota | Object | Yes | The quota information about the application.For more information, see Quota . | |
chargeType | String | No | "POSTPAY" | The billing method.Valid values: POSTPAYand PREPAY. |
order | Object | No | {"duration": 1,"pricingCycle": "Year"} | The information about the subscription period. |
order.duration | Integer | -- | 1 | The subscription duration.The minimum value is no less than 0. |
order.pricingCycle | String | -- | "Year" | The unit of the subscription duration.YearMonth. |
order.autoRenew | Boolean | No | true | Specifies whether to enable auto-renewal. This parameter takes effect only when the chargeType parameter is set to PREPAY. Valid values:true.false (the default value). |
Response parameters
Examples
Sample success responses
JSON
format
{
"requestId": "766CF6DB-CA02-3E12-7CBA-6AC21FC978FD",
"result": {
"created": 1590139542,
"currentVersion": "100302903",
"lockMode": "Unlock",
"updated": 1590978265,
"id": "100302881",
"chargeType": "POSTPAY",
"hasPendingQuotaReviewTask": 0,
"name": "lsh_test_1",
"instanceId": "-",
"chargingWay": 1,
"type": "enhanced",
"status": "normal",
"projectId": "-",
"switchedTime": 1590486386,
"commodityCode": "opensearch",
"expireOn": "-",
"domain": "GENERAL",
"description": "-",
"produced": 1,
"quota": {
"spec": "opensearch.share.common",
"docSize": 1,
"computeResource": 20
},
"engineType": "ha3"
}
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-09-03 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2024-08-08 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2024-08-08 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2024-07-16 | The response structure of the API has changed | View Change Details |
2023-05-30 | The request parameters of the API has changed | View Change Details |