You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/01/23 23:13:34 UTC
[jira] [Updated] (JCLOUDS-207) Key Pair and Security Groups created
by jclouds are not removed when the node is destroyed (via Jclouds)
[ https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gaul updated JCLOUDS-207:
--------------------------------
Component/s: jclouds-compute
> 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
> Components: jclouds-compute
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)