In the kluster
directory, type cat keys.sh
. You should see output like the following:
# cat keys.sh export AWS_ACCESS_KEY=ABCDEFGIPFDASZFDAXYZ export AWS_SECRET_KEY=ABCXPQB8LPOfDA9pbiUzFFDASFsAFDA3PFfpXYZ
These are just placeholders for your AWS access keys. If you don't have an AWS account already, create one at http://aws.amazon.com/. Then:
AWS_ACCESS_KEY=
in keys.shAWS_SECRET_KEY=
in keys.shRemember not to put a space after the equals sign (you knew this, right?)
These keys give the ec2 API tools authorization to do things in the Amazon cloud. Don't worry: the "kluster" tools won't magically start creating things in the cloud without your knowledge. It will be obvious when you are creating nodes and so on.
Now, source this file in your shell:
. vars.sh
This will in turn source keys.sh. We assume your shell is bash or something similar such as dash, or this won't work correctly. The file vars.sh
contains the things required for Amazon's ec2 API tools to work, plus sets your path. Next, type
ec2din
This is the short form of the command ec2-describe-instances
, which will output information about any machines you have running in the Amazon cloud. If it gives you an error message, try to fix it before proceeding. This will be a problem with your ec2 API tools installation or your access keys.
Next: Setting up a security group
Up: Kluster Wiki
Wiki: GettingStarted
Wiki: Home
Wiki: SecurityGroupSetup
type ec2din in terminal in address root/kluster or root/kluster/ec2-api-tools-1.6.9.0/bin ?
Last edit: abbaskarimi 2013-09-07
I must have assumed that you have the bin directory on your path at that point.
Do the instructions not tell you to do something like source a shell
script that sets the path?
Dan
On Sat, Sep 7, 2013 at 9:23 AM, abbaskarimi abbaskarimi@users.sf.net wrote: