Question: AWS Charges for Multiple Instances, how do I terminate
0
gravatar for nicole.hawkins
2.3 years ago by
nicole.hawkins0 wrote:

I am being charged on AWS for two instances r3.2X and r3.8x. I have no idea how to turn them off and the AWS website is impossible for someone new to cloud computing. The hours being charged do not make sense (+300 hrs), so I am guessing there are multiple r3.2x instances going. Does anyone know how to terminate multiple instances on Cloudman?

ADD COMMENTlink modified 2.3 years ago • written 2.3 years ago by nicole.hawkins0
1
gravatar for Dannon Baker
2.3 years ago by
Dannon Baker3.7k
United States
Dannon Baker3.7k wrote:

Did you start multiple clusters, or have you been using a single cluster with multiple workers?

For terminating complete clusters, ideally you use the built-in cloudman functionality to terminate clusters as it'll handle all the cleanup correctly. If you just have a single cluster with many workers running, you should kill those through the currently running cloudman instance, by going to http://your_cloud_instance/cloud

If you have no idea what's running and just want to shut it all down quickly:

1) go to console.aws.amazon.com 2) click "EC2" in the Compute section 3) click "Running Instances"

You should now see a list of instances. The name of the instance indicates what type it is. Cluster 'master' instances will be named master: <clustername>.

For each of these master instances, copy that Public DNS you see and paste it into a new tab, appending /cloud. Now you'll see the cloudman interface, where you can click "Terminate", and if you're done (permanently) with that cluster and data, make sure to check the option for deleting residual cruft.

If you see workers, then the master will automatically terminate these when it shuts down.

Please let me know if you only see workers and no masters, because that's a problem.

ADD COMMENTlink modified 2.3 years ago • written 2.3 years ago by Dannon Baker3.7k
0
gravatar for nicole.hawkins
2.3 years ago by
nicole.hawkins0 wrote:

Thank you. Turns out, I just spent 3 hours trying to figure it out and it was because my AWS was defaulting to Oregon, when the Galaxy console is in Virginia... So it was always saying 0 instances running. When I changed to Virginia, there were 4 instances. Wow.

ADD COMMENTlink written 2.3 years ago by nicole.hawkins0

Ahh, that's unfortunate. Glad you figured it out though. We're working on a new view that'll sit on top of what you see in the console, showing all of the Galaxy stuff you have running in a particular account, so that should make this a bit easier to handle.

ADD REPLYlink written 2.3 years ago by Dannon Baker3.7k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 182 users visited in the last hour