[
https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722031#comment-13722031
]
Andrew Phillips commented on JCLOUDS-207:
-----------------------------------------
Note that a method "cleanUpIncidentalResourcesOfDeadNodes" [1] already
exists...perhaps it's just a question of calling that at the appropriate time?
[1]
https://github.com/jclouds/jclouds/blob/master/apis/ec2/src/main/java/org/jclouds/ec2/compute/EC2ComputeService.java#L278
> Key Pair and Security Groups created by jclouds are not removed when the node
> is destroyed (via Jclouds)
> --------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-207
> URL: https://issues.apache.org/jira/browse/JCLOUDS-207
> Project: jclouds
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Eugen Paraschiv
> Labels: ec2
>
> Simply stated, the problem is that the nodes that are created in EC2 via
> jclouds leave a key-pair and a security group each, after they're deleted
> (also via jclouds).
> This issue is described in much more detail here:
> http://www.cloudsoftcorp.com/blog/tidying-up-after-jclouds/
> Hopefully it's an easy fix and the operation of first creating and then
> destroying the node will leave no unnecessary artifacts on the EC2 account.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
