You need to enable JavaScript to run this app.
IAM

IAM

Copy page
Download PDF
FAQ
Why did the service association role deletion fail?
Copy page
Download PDF
Why did the service association role deletion fail?

Why does service association role deletion fail?

In some scenarios where Cloud as a Service relies on the resources of another Cloud as a Service (e.g., a container service cluster relies on Cloud as a Service resources), services typically request service association roles for cross-service access. When a service-associated role is being used by Cloud as a Service, deleting the role may cause a resource exception, so you may be temporarily prohibited from deleting the service-associated role and asked to clean up the resource before deleting the cloud resource. The following are the deletion conditions for some service association roles:

Cloud as a Serviceservice association roleDelete condition
container serviceServiceRoleForVKEClean up all container clusters
Cloud Database MySQL EditionServiceRoleForRDSMySQLClean up all MySQL database instances
Cloud Database PostgreSQL EditionServiceRoleForRDSPGClean up all PostgreSQL database instances
mirror warehouseServiceRoleForCRClean up all mirror repository instances
Message queue Kafka versionServiceRoleForKafkaClean up all Kafka instances
elastic stretchingServiceRoleForAutoScalingClean up all telescopic groups
Message queue RocketMQ versionServiceRoleForRocketMQClean up all RocketMQ instances
Message queue RabbitMQ versionServiceRoleForRabbitMQClean up all RabbitMQ instances
private network connectionServiceRoleForPrivateLinkClean all end points
VPN connectionServiceRoleForVPNClean up all VPN gateways
Web Application FirewallServiceRoleForWafClean up all web application firewall instances
Cloud FirewallServiceRoleForFwCenterClean up all cloud firewall instances
Last updated: 2025.06.23 19:21:32