Delete a delivery channel by calling DeleteConfigDeliveryChannel - Cloud Config - Alibaba Cloud - Cloud Config

Operation description

The following example deletes the cdc-38c3013b46c9002c**** delivery channel.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

config:DeleteConfigDeliveryChannel

delete

*Delivery

acs:config:*:{#accountId}:delivery/{#DeliveryChannelId}

None

Request parameters

Parameter	Type	Required	Description	Example
DeliveryChannelId	string	Yes	The ID of the delivery channel. For more information about how to obtain the ID of a delivery channel, see DescribeDeliveryChannels.	cdc-38c32e87cadb002c****

For more information about common request parameters, see Common parameters.

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	35F1DA37-ECB5-54E9-AC22-0D9111A665AA
DeliveryChannelId	string	The ID of the delivery channel.	cdc-38c32e87cadb002c****

Examples

Success response

JSON format

{
  "RequestId": "35F1DA37-ECB5-54E9-AC22-0D9111A665AA",
  "DeliveryChannelId": "cdc-38c32e87cadb002c****"
}

Error codes

HTTP status code	Error code	Error message
400	DeliveryChannelNotExists	The delivery channel does not exist.
400	Invalid.DeliveryChannelAssumeRoleArn.Format	The specified format of DeliveryChannelAssumeRoleArn is invalid.
400	Invalid.DeliveryChannelTargetArn.Format	The specified format of DeliveryChannelTargetArn is invalid.
400	Invalid.DeliveryChannelCondition.Format	The specified format of DeliveryChannelCondition is invalid.
400	MemberNotBelongToMaster	The specified member does not belong to your organization.
400	DeliveryChannelAccountNotSupport	Cross-account delivery that is not in the RD is not supported.
400	DeliveryChannelMnsUnreachable	The MNS topic is unreachable.
400	DeliveryChannelOssUnreachable	The OSS bucket is unreachable.
400	DeliveryChannelSlsUnreachable	SLS logstore is unreachable.
404	AccountNotExisted	Your account does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.