Unable to terminate EC2 Host due to allocation error

If you encounter an error when trying to delete an EC2 Host that states "the allocation has no hosts and cannot support containers yet", this typically occurs when logging is enabled on the tenant and the system is trying to schedule agents or containers on the host you're attempting to delete. Why this happens When logging is enabled on a tenant, the system automatically tries to schedule logging agents and containers on available hosts. If the host you're trying to delete is the only host in the tenant, the system cannot complete the deletion because it needs to maintain the logging infrastructure. Resolution To resolve this issue, you'll need to contact support to have the host terminated manually. The support team can safely remove the host while handling any dependent logging agents or containers that may be preventing the deletion. SSH Access to EC2 Hosts If you need to access your EC2 hosts directly, you can SSH from your local terminal if you're connected to VPN. For detailed instructions on SSH access, refer to the SSH EC2 Instance documentation .