Amazon EC2 API Access Control
===

We are trying to do some development within our EC2 cloud that requires the use of certain API calls (Create/Delete Volume, Start/Stop Instance, etc). After reading Amazon's documentation, I find that while I can share instance-level access with a different AWS account, I have no granular access control with my users created in IAM; if I give them a Destroy right it applies globally.

My question is, how have others dealt with this issue? I'm adverse to giving a global destroy right in our production environment to any software that is under development, and doubly so because these are contract developers. At the same time, I'm also wary of even the production program having those rights globally because it seems to be bad practice and inherently insecure code.

Is there any sort of workaround that people have found?