All Products
Search
Document Center

Virtual Private Cloud:Public error codes

Last Updated:Jan 28, 2026

Error codes

HTTP status code

Error code

Error message

Description

Action

400 BothEmpty.TagsAndResources The specified Tags and ResourcesIds are not allow to both empty. The tag and resource information cannot be empty at the same time. diagnosis
400 Conflict.Operation There are other peering operations on the requester VPC or accepter VPC, try again later. There are other VpcPeer changes to the initiator VPC or the receiver VPC. You need to try again later. diagnosis
400 DryRunOperation The operation DryRun verifies success. The operation DryRun verifies success. diagnosis
400 Forbidden.NoPermission Authentication is failed for %s. Permission verification failed. diagnosis
400 Forbidden.TagKey.Duplicated The specified tag key already exists. The tag resources are duplicate. diagnosis
400 Forbidden.TagKeys The tag key cannot be operated by the request. You cannot manage the tag key by calling the operation. diagnosis
400 IllegalParam.%s The param of %s is illegal. The specified parameter is set to an invalid value. diagnosis
400 IllegalParam.TagKey The param of Tag.Key is illegal. The specified parameter Tag.Key is invalid. diagnosis
400 IllegalParam.TagValue The param of Tag.Value is illegal. The specified parameter Tag.Value is illegal. diagnosis
400 IncorrectBusinessStatus.AcceptUserVpcPeer The business status of %s [%s] is incorrect. The peer VPC is in an invalid business state. diagnosis
400 IncorrectBusinessStatus.AcceptVpcPeer The business status of peer account is incorrect. The business status of the peer VpcPeer in an invalid state. diagnosis
400 IncorrectBusinessStatus.VpcPeer The business status of %s [%s] is incorrect. The current instance status is abnormal and the current operation is not allowed. diagnosis
400 IncorrectStatus.AcceptingVpc The status of %s [%s] is incorrect. The receiving VPC status is incorrect. diagnosis
400 IncorrectStatus.Vpc The status of %s [%s] is incorrect. The status of the initiator VPC instance is incorrect. diagnosis
400 IncorrectStatus.VpcPeer %s [%s] status is invalid. The VPC peering connection is in an invalid state. diagnosis
400 IncorrectStatus.VpcPeer The status of %s [%s] is incorrect. The status of the peer-to-peer connection instance does not meet the requirements. In this status, the peer-to-peer connection instance cannot be received. diagnosis
400 InvalidAcceptingAliUid Specified parameter AcceptingAliUid is not valid. The Alibaba Cloud account for which you want to create an accepter VPC is invalid. diagnosis
400 InvalidBandwidth Specified parameter Bandwidth is not valid. The specified bandwidth is invalid and cannot be modified. diagnosis
400 InvalidInstanceIds.NotFound The instance IDs are not found. The instance ID is invalid. diagnosis
400 InvalidInstanceIds.NotFound The operation failed because of invalid instanceId. The specified instance ID is invalid. diagnosis
400 InvalidInstanceType.NotFound The instance type is not found. The instance type is invalid. diagnosis
400 InvalidTagKey The tag keys are not valid. The tag index is invalid. diagnosis
400 NumberExceed.ResourceIds The maximum number of resource IDs is exceeded. The number of resource group IDs exceeds the upper limit. diagnosis
400 NumberExceed.Tags The maximum number of tags is exceeded. The number of tags has reached the upper limit. diagnosis
400 OperationDenied.CloudBoxExistsInAcceptingVpc The operation is not allowed because the CloudBox device exists in accepting vpc. Cloud box instances exist in the receiving end VPC, so VpcPeer instances are not allowed to be created. diagnosis
400 OperationDenied.CloudBoxExistsInVpc The operation is not allowed because the CloudBox device exists in vpc. A cloud box instance exists in the initiator VPC, so it is not allowed to create a VpcPeer instance. diagnosis
400 OperationDenied.OperateShareResource The operation is not allowed because of operating shared resource. Operating on shared resources causes the operation to fail diagnosis
400 OperationDenied.RouteEntryExist The operation is not allowed because of existing routeEntry point to VpcPeer. The VPC peering connection cannot be deleted because a route points to the VPC peering connection. diagnosis
400 OperationFailed.AcceptUserCdtNotOpened The operation failed because the Cdt service of accept user is not opened. The operation failed because CDT is not activated for the peer. diagnosis
400 OperationFailed.AcceptUserCrossBorderCdtNotOpened The operation failed because the CrossBorderCdt service of accept user is not opened. The operation failed because the cross-border service of CDT is not activated for the peer. diagnosis
400 OperationFailed.BandwidthCannotBeChangedInSameRegion The operation failed because the bandwidth cannot be changed in the same region. The operation failed because VpcPeer instances in the same region are not allowed to modify the bandwidth value. diagnosis
400 OperationFailed.CdtNotOpened The operation failed because the Cdt service is not opened. The operation failed because CDT is not activated. diagnosis
400 OperationFailed.CrossBorderCdtNotOpened The cross-border data transmission function of Alibaba Cloud is not enabled. diagnosis
400 OperationFailed.CrossBorderCdtNotOpened The operation failed because the CrossBorderCdt service is not opened. diagnosis
400 OperationFailed.InterRegionLinkTypeNotSupported The same region not supported link type feature. Link type characteristics are not supported in the same region. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because the resource group does not exist. The operation failed because the resource group does not exist. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because the resource group not exist. The operation failed because the resource group does not exist. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because resourceGroup not exist. The specified resource group does not exist. diagnosis
400 OperationFailed.RegionIdNotSupportLinkType The feature link type is not supported in the region. The gold, silver and copper settings for this feature are not supported in the region. diagnosis
400 OperationFailed.SpecificLinkTypeNotSupported The operation failed because the special link type of user is not opened. The account does not support special link types. diagnosis
400 OperationFailed.ViolativeVpcPeer The creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. the creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. diagnosis
400 OperationFailed.ViolativeVpcPeer The operation failed because it is out of compliance to create a vpc peer between originating region and accepting region. the creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. diagnosis
400 QuotaExceeded.Bandwidth The quota of bandwidth is exceeded. The specified bandwidth is invalid. diagnosis
400 QuotaExceeded.CrossRegionVpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of cross-region VpcPeer in the specified VPC exceeds the limit diagnosis
400 QuotaExceeded.IntraRegionVpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of VpcPeer in the same region in the specified VPC exceeds the limit diagnosis
400 QuotaExceeded.VpcPeerCountPerUserPerRegion The quota of %s is exceeded, usage %s/%s. The number of VpcPeer instances in a region exceeds the threshold. diagnosis
400 QuotaExceeded.VpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of VPC peering connections to the VPC has reached the upper limit. diagnosis
400 ResourceAlreadyExist.RouterInterface The specified resource of %s already exists. The specified router interface already exists. diagnosis
400 ResourceAlreadyExist.VpcPeer The specified resource of %s already exists. The specified VPC peering connection already exists. diagnosis
400 ResourceNotFound.InstanceId The specified resource of %s is not found. The specified instance is not found diagnosis
400 ResourceNotFound.VpcPeer The specified resource of VpcPeer is not found. The VPC peering connection does not exist. diagnosis
400 UnsupportedRegion The feature of %s is not supported in the region of %s. VPC peering connections are not supported in this region. diagnosis
400 OperationFailed.UserForbiddenInPreEnv Current user is forbidden to operate in pre environment. The current user is prohibited from operating in the advance environment diagnosis
400 BothEmpty.TagsAndResources The specified Tags and ResourcesIds are not allow to both empty. The tag and resource information cannot be empty at the same time. diagnosis
400 Conflict.Operation There are other peering operations on the requester VPC or accepter VPC, try again later. There are other VpcPeer changes to the initiator VPC or the receiver VPC. You need to try again later. diagnosis
400 DryRunOperation The operation DryRun verifies success. The operation DryRun verifies success. diagnosis
400 Forbidden.NoPermission Authentication is failed for %s. Permission verification failed. diagnosis
400 Forbidden.TagKey.Duplicated The specified tag key already exists. The tag resources are duplicate. diagnosis
400 Forbidden.TagKeys The tag key cannot be operated by the request. You cannot manage the tag key by calling the operation. diagnosis
400 IllegalParam.%s The param of %s is illegal. The specified parameter is set to an invalid value. diagnosis
400 IllegalParam.TagKey The param of Tag.Key is illegal. The specified parameter Tag.Key is invalid. diagnosis
400 IllegalParam.TagValue The param of Tag.Value is illegal. The specified parameter Tag.Value is illegal. diagnosis
400 IncorrectBusinessStatus.AcceptUserVpcPeer The business status of %s [%s] is incorrect. The peer VPC is in an invalid business state. diagnosis
400 IncorrectBusinessStatus.AcceptVpcPeer The business status of peer account is incorrect. The business status of the peer VpcPeer in an invalid state. diagnosis
400 IncorrectBusinessStatus.VpcPeer The business status of %s [%s] is incorrect. The current instance status is abnormal and the current operation is not allowed. diagnosis
400 IncorrectStatus.AcceptingVpc The status of %s [%s] is incorrect. The receiving VPC status is incorrect. diagnosis
400 IncorrectStatus.Vpc The status of %s [%s] is incorrect. The status of the initiator VPC instance is incorrect. diagnosis
400 IncorrectStatus.VpcPeer %s [%s] status is invalid. The VPC peering connection is in an invalid state. diagnosis
400 IncorrectStatus.VpcPeer The status of %s [%s] is incorrect. The status of the peer-to-peer connection instance does not meet the requirements. In this status, the peer-to-peer connection instance cannot be received. diagnosis
400 InvalidAcceptingAliUid Specified parameter AcceptingAliUid is not valid. The Alibaba Cloud account for which you want to create an accepter VPC is invalid. diagnosis
400 InvalidBandwidth Specified parameter Bandwidth is not valid. The specified bandwidth is invalid and cannot be modified. diagnosis
400 InvalidInstanceIds.NotFound The instance IDs are not found. The instance ID is invalid. diagnosis
400 InvalidInstanceIds.NotFound The operation failed because of invalid instanceId. The specified instance ID is invalid. diagnosis
400 InvalidInstanceType.NotFound The instance type is not found. The instance type is invalid. diagnosis
400 InvalidTagKey The tag keys are not valid. The tag index is invalid. diagnosis
400 NumberExceed.ResourceIds The maximum number of resource IDs is exceeded. The number of resource group IDs exceeds the upper limit. diagnosis
400 NumberExceed.Tags The maximum number of tags is exceeded. The number of tags has reached the upper limit. diagnosis
400 OperationDenied.CloudBoxExistsInAcceptingVpc The operation is not allowed because the CloudBox device exists in accepting vpc. Cloud box instances exist in the receiving end VPC, so VpcPeer instances are not allowed to be created. diagnosis
400 OperationDenied.CloudBoxExistsInVpc The operation is not allowed because the CloudBox device exists in vpc. A cloud box instance exists in the initiator VPC, so it is not allowed to create a VpcPeer instance. diagnosis
400 OperationDenied.OperateShareResource The operation is not allowed because of operating shared resource. Operating on shared resources causes the operation to fail diagnosis
400 OperationDenied.RouteEntryExist The operation is not allowed because of existing routeEntry point to VpcPeer. The VPC peering connection cannot be deleted because a route points to the VPC peering connection. diagnosis
400 OperationFailed.AcceptUserCdtNotOpened The operation failed because the Cdt service of accept user is not opened. The operation failed because CDT is not activated for the peer. diagnosis
400 OperationFailed.AcceptUserCrossBorderCdtNotOpened The operation failed because the CrossBorderCdt service of accept user is not opened. The operation failed because the cross-border service of CDT is not activated for the peer. diagnosis
400 OperationFailed.BandwidthCannotBeChangedInSameRegion The operation failed because the bandwidth cannot be changed in the same region. The operation failed because VpcPeer instances in the same region are not allowed to modify the bandwidth value. diagnosis
400 OperationFailed.CdtNotOpened The operation failed because the Cdt service is not opened. The operation failed because CDT is not activated. diagnosis
400 OperationFailed.CrossBorderCdtNotOpened The cross-border data transmission function of Alibaba Cloud is not enabled. diagnosis
400 OperationFailed.CrossBorderCdtNotOpened The operation failed because the CrossBorderCdt service is not opened. diagnosis
400 OperationFailed.InterRegionLinkTypeNotSupported The same region not supported link type feature. Link type characteristics are not supported in the same region. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because the resource group does not exist. The operation failed because the resource group does not exist. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because the resource group not exist. The operation failed because the resource group does not exist. diagnosis
400 OperationFailed.NotExist.ResourceGroup The operation failed because resourceGroup not exist. The specified resource group does not exist. diagnosis
400 OperationFailed.RegionIdNotSupportLinkType The feature link type is not supported in the region. The gold, silver and copper settings for this feature are not supported in the region. diagnosis
400 OperationFailed.SpecificLinkTypeNotSupported The operation failed because the special link type of user is not opened. The account does not support special link types. diagnosis
400 OperationFailed.ViolativeVpcPeer The creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. the creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. diagnosis
400 OperationFailed.ViolativeVpcPeer The operation failed because it is out of compliance to create a vpc peer between originating region and accepting region. the creation operation fails because it is not allowed to create a vpc peer instance between the originating region and the receiving region. diagnosis
400 QuotaExceeded.Bandwidth The quota of bandwidth is exceeded. The specified bandwidth is invalid. diagnosis
400 QuotaExceeded.CrossRegionVpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of cross-region VpcPeer in the specified VPC exceeds the limit diagnosis
400 QuotaExceeded.IntraRegionVpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of VpcPeer in the same region in the specified VPC exceeds the limit diagnosis
400 QuotaExceeded.VpcPeerCountPerUserPerRegion The quota of %s is exceeded, usage %s/%s. The number of VpcPeer instances in a region exceeds the threshold. diagnosis
400 QuotaExceeded.VpcPeerCountPerVpc The quota of %s is exceeded, usage %s/%s. The number of VPC peering connections to the VPC has reached the upper limit. diagnosis
400 ResourceAlreadyExist.RouterInterface The specified resource of %s already exists. The specified router interface already exists. diagnosis
400 ResourceAlreadyExist.VpcPeer The specified resource of %s already exists. The specified VPC peering connection already exists. diagnosis
400 ResourceNotFound.InstanceId The specified resource of %s is not found. The specified instance is not found diagnosis
400 ResourceNotFound.VpcPeer The specified resource of VpcPeer is not found. The VPC peering connection does not exist. diagnosis
400 UnsupportedRegion The feature of %s is not supported in the region of %s. VPC peering connections are not supported in this region. diagnosis
400 OperationFailed.UserForbiddenInPreEnv Current user is forbidden to operate in pre environment. The current user is prohibited from operating in the advance environment diagnosis