Nice job @rcoedo! Just one comment about the live tests: If you create tests as private methods and manually call them from other tests, they won't appear in the test report and one wouldn't be able to know if that is properly tested, or if there are regressions in them without looking at the code.
A better way to configure that would be to make them public, and use the `dependsOnMethod` attribute in the `@Test` annotation to force them to be executed after the methods that create the vaults. Then, the cleanup logic could be moved outside the "create" method, either to a `testDelete` method, or to a method annotated with an `@AfterClass` (I tend to prefer the first one, as the after class method does not appear as a test in the test report). You can have a look at some [digitalocean](https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/test/java/org/jclouds/digitalocean/features/DropletApiLiveTest.java) tests for an example. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-aws/pull/4#issuecomment-43980562
