All Products
Search

This Product

    Edge Security Acceleration:CreateEdgeContainerApp

    Document Center

    Edge Security Acceleration:CreateEdgeContainerApp

    Last Updated:Nov 15, 2025

    Creates a containerized application. You can deploy and release a version of the application across points of presence (POPs).

    Debugging

    You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

    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:
      • For mandatory resource types, indicate with a prefix of * .
      • 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.
    OperationAccess levelResource typeCondition keyAssociated operation
    esa:CreateEdgeContainerAppnone
    *All Resources
    *
      none
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    NamestringYes

    The name of the application. The name must start with a lowercase letter and can contain lowercase letters, digits, and hyphens (-). The name must be 6 to 128 characters in length.

    		app-test
    ServicePortintegerYes

    The server port. Valid values: 1 to 65535.

    		80
    TargetPortintegerYes

    The backend port, which is also the service port of the application. Valid values: 1 to 65535.

    		80
    RemarksstringNo

    The remarks. This parameter is empty by default.

    		test app
    HealthCheckTypestringNo

    The health check type. By default, this parameter is left empty.

    Valid values:

    • l4: Layer 4 health check.
    • l7: Layer 7 health check.
    		l7
    HealthCheckHoststringNo

    The domain name that is used for health checks. This parameter is empty by default.

    		www.aliyun.com
    HealthCheckHttpCodestringNo

    The HTTP status code returned for a successful health check. Valid values:

    • http_2xx (default)
    • http_3xx
    		http_2xx
    HealthCheckMethodstringNo

    The HTTP request method for health checks. Valid values:

    • HEAD (default): requests the headers of the resource.
    • GET: requests the specified resource and returns both the headers and entity body.
    		HEAD
    HealthCheckURIstringNo

    The URI used for health checks. The URI must be 1 to 80 characters in length. Default value: "/".

    		/health_check
    HealthCheckPortintegerNo

    The port used for health checks. Valid values: 1 to 65535. Default value: 80.

    		80
    HealthCheckTimeoutintegerNo

    The timeout period of a health check response. If a backend ECS instance does not respond within the specified timeout period, the ECS instance fails the health check. Unit: seconds.
    Valid values: 1 to 100.
    Default value: 3.

    		5
    HealthCheckIntervalintegerNo

    The interval between two consecutive health checks. Unit: seconds. Valid values: 1 to 50. Default value: 5.

    		5
    HealthCheckSuccTimesintegerNo

    The number of consecutive successful health checks required for an application to be considered as healthy. Valid values: 1 to 10. Default value: 2.

    		2
    HealthCheckFailTimesintegerNo

    The number of consecutive failed health checks required for an application to be considered as unhealthy. Valid values: 1 to 10. Default value: 5.

    		3

    Response parameters

    ParameterTypeDescriptionExample
    object

    The response parameters.

    AppIdstring

    The ID of the application that is created.

    		app-880688675783794688
    RequestIdstring

    The request ID.

    		04F0F334-1335-436C-A1D7-6C044FE73368

    Examples

    Sample success responses

    JSONformat

    {
  "AppId": "app-880688675783794688",
  "RequestId": "04F0F334-1335-436C-A1D7-6C044FE73368"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400InvalidParameter.HealthCheckTypeSpecified parameter HealthCheckType is not valid.Parameter HealthCheckType format is incorrect.
    400InvalidParameter.HealthCheckHostSpecified parameter HealthCheckHost is not valid.Parameter HealthCheckHost format is incorrect.
    400InvalidParameter.HealthCheckHttpCodeSpecified parameter HealthCheckHttpCode is not valid.Parameter HealthCheckHttpCode format is incorrect.
    400InvalidParameter.HealthCheckMethodSpecified parameter HealthCheckMethod is not valid.Parameter HealthCheckMethod format is incorrect.
    400InvalidParameter.HealthCheckURISpecified parameter HealthCheckURI is not valid.Parameter HealthCheckURI format is incorrect.
    400InvalidParameter.HealthCheckIntervalSpecified parameter HealthCheckInterval is not valid.Parameter HealthCheckInterval format is incorrect.
    400InvalidParameter.HealthCheckTimeoutSpecified parameter HealthCheckTimeout is not valid.Parameter HealthCheckTimeout format is incorrect.
    400InvalidParameter.HealthCheckSuccTimesSpecified parameter HealthCheckSuccTimes is not valid.Parameter HealthCheckHost format is incorrect.
    400InvalidParameter.HealthCheckFailTimesSpecified parameter HealthCheckFailTimes is not valid.Parameter HealthCheckFailTimes format is incorrect.
    400InvalidParameter.HealthCheckPortSpecified parameter HealthCheckPort is not valid.Parameter HealthCheckPort format is incorrect.
    400InvalidParameter.PageNumberFailed to verify parameter PageNumber.Check whether the parameter exists and is set to a positive integer.Failed to verify parameter PageNumber.Check whether the parameter exists and is set to a positive integer.
    400InvalidParameter.appidThe format of the application ID is invalid. You can call ListEdgeContainerApps to obtain the application ID.The format of the application ID is invalid. You can call ListEdgeContainerApps to obtain the application ID.
    400InvalidParameterThe specified parameter is invalid.The specified parameter is invalid.
    400NameAlreadyExistsThe name already exists.Name already exists.
    400ParamNameErrorThe Name parameter is invalid.The Name parameter is illegal.
    404InvalidApp.NotFoundThe application does not exist. Check whether the application ID you specified is correct and try again.The application does not exist. Check whether the application ID you specified is correct and try again.
    500InternalErrorFailed to call the service. Try again later or contact technical support.Failed to call the service. Try again later or contact technical support.

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    No change history