[
https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404793#comment-15404793
]
ASF GitHub Bot commented on JCLOUDS-207:
----------------------------------------
Github user mikezaccardo commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/98#discussion_r73238334
--- Diff: guide/ops/locations/_AWS.md ---
@@ -19,21 +19,35 @@ and [AWS IAM
instructions](http://docs.aws.amazon.com/IAM/latest/UserGuide/Manag
An example of the expected format is shown below:
- brooklyn.location.jclouds.aws-ec2.identity=ABCDEFGHIJKLMNOPQRST
-
brooklyn.location.jclouds.aws-ec2.credential=abcdefghijklmnopqrstu+vwxyzabcdefghijklm
+ location:
+ jclouds:aws-ec2:
+ region: us-east-1
+ identity: ABCDEFGHIJKLMNOPQRST
+ credential: abcdefghijklmnopqrstu+vwxyzabcdefghijklm
+Users are strongly recommended to use
+[externalized configuration]({{ site.path.guide
}}/ops/externalized-configuration.html) for better
+credential management, for example using
[Vault](https://www.vaultproject.io/).
-### Tidying up after jclouds
-Security groups are not always deleted by jclouds. This is due to a
limitation in AWS (see
-https://issues.apache.org/jira/browse/JCLOUDS-207). In brief, AWS prevents
the security group
-being deleted until there are no VMs using it. However, there is eventual
consistency for
-recording which VMs still reference those security groups: after deleting
the VM, it can sometimes
-take several minutes before the security group can be deleted. jclouds
retries for 3 seconds, but
-does not block for longer.
+### Common Configuration Options
-There is utility written by Cloudsoft for deleting these unused resources:
-http://www.cloudsoftcorp.com/blog/2013/03/tidying-up-after-jclouds.
+Below are examples of configuration options that use values specific to
AWS EC2:
+
+* The `region` is the [AWS region
code](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html).
+ For example, `region: us-east-1`. One can also in-line this value when
such as `jclouds:aws-ec2:us-east-1`.
--- End diff --
+1
> 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)
