I have EC2 cloud agents configured with my Team City instance. Unfortunately, this month I am being hit with a huge EC2 build because of the way TC is handling agents. Specifically, when TC terminates a build agent, it doesn't delete the EBS volume associated with that build agent. Consequently, the detached EBS volume is left "available" and accumulates storage fees.
How do I fix this? Can TC be configured to delete the volumes? Can I change the configuration of my AMI so that the volumes are not created in the first place?