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 Service | service association role | Delete condition |
|---|---|---|
| container service | ServiceRoleForVKE | Clean up all container clusters |
| Cloud Database MySQL Edition | ServiceRoleForRDSMySQL | Clean up all MySQL database instances |
| Cloud Database PostgreSQL Edition | ServiceRoleForRDSPG | Clean up all PostgreSQL database instances |
| mirror warehouse | ServiceRoleForCR | Clean up all mirror repository instances |
| Message queue Kafka version | ServiceRoleForKafka | Clean up all Kafka instances |
| elastic stretching | ServiceRoleForAutoScaling | Clean up all telescopic groups |
| Message queue RocketMQ version | ServiceRoleForRocketMQ | Clean up all RocketMQ instances |
| Message queue RabbitMQ version | ServiceRoleForRabbitMQ | Clean up all RabbitMQ instances |
| private network connection | ServiceRoleForPrivateLink | Clean all end points |
| VPN connection | ServiceRoleForVPN | Clean up all VPN gateways |
| Web Application Firewall | ServiceRoleForWaf | Clean up all web application firewall instances |
| Cloud Firewall | ServiceRoleForFwCenter | Clean up all cloud firewall instances |