0

I've recently set up TeamCity to use agents running on Amazon EC2. I've been using it for a week or so and noticed my bill was racking up quite quickly. When I looked in my dashboard I had 30 or so snapshots, which I presume I'm being charged for.

TeamCity starts agents on demand and stops them when they've been idle for about an hour. At that point, the instance is deleted. I would expect the corresponding snapshot to be deleted too, but that doesn't seem to be happening, they are piling up like zombies!

When setting this up I followed Roy Osherove's guide and I tried to follow to the letter, but I'm sure I must have missed something. Does anyone know where I went wrong?

Tim Long
  • 13,508
  • 19
  • 79
  • 147
  • Have you verified that those snapshots are indeed the main constituents of your bill? I'm not familiar with the TeamCity agent provisioning, but I doubt that ~30 left over EBS volume snapshots will have any significant impact on your AWS bill, insofar EBS cost usually amount for a fraction of the average AWS bill for any but the most special use cases; instead I'd suspect the created/running/terminated instances themselves to inflict the cost, which you could only remedy by adjusting the TeamCity provisioning algorithm and/or instance type. – Steffen Opel Apr 29 '13 at 08:28
  • 1
    I've given up on AWS, the cost was far more than the benefits and I felt like I wasn't in control. My bill was equivalent to almost $2 per build!! I've gone back to running build agents on-premises. – Tim Long May 17 '13 at 13:27

1 Answers1

0

you can create a special teamcity-agent image, when add esb volume, check the "Delete on Termination" checkbox.

enter image description here

jolestar
  • 1,285
  • 15
  • 21