Cant install storm deploy on EC2

[rakatti]

I keep getting following exception when I start storm cluster...Please advise

Exception in thread "main" org.jclouds.rest.AuthorizationException: POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 -> HTTP/1.1 401 Unauthorized (NO_SOURCE_FILE:1)

I am running nimbus, supervisor, zookeeper on the same machine...

here is the storm.yaml

storm.local.dir: "/mnt/storm" storm.zookeeper.servers: - "localhost" java.library.path: "/usr/local/lib/" nimbus.host: "127.0.0.1" nimbus.task.launch.secs: 240 supervisor.worker.start.timeout.secs: 240 supervisor.worker.timeout.secs: 240 storm.zookeeper.servers: - "127.0.0.1" supervisor.slots.ports: - 6700 - 6701 - 6702 - 6703

here is the cluster.yaml

nimbus.image: "us-east-1a/ami-idxxxx" #64-bit ubuntu nimbus.hardware: "m1.large" supervisor.count: 1 supervisor.image: "us-east-1a/ami-idxxxx" #64-bit ubuntu on us-east supervisor.hardware: "c1.xlarge"

supervisor.spot.price: 1.60

zookeeper.count: 1 zookeeper.image: "us-east-1a/ami-idxxxx" #64-bit ubuntu zookeeper.hardware: "m1.large"

here is the config.clj - (I have not setup any ssh keys .. all you need is username password to get in...)

(defpallet :services { :default { :blobstore-provider "aws-s3" :provider "aws-ec2" :environment {:user {:username "storm" ; this must be "storm" :private-key-path "" :public-key-path ""} :aws-user-id "id i see on aws dashboard"} :identity "userid" :credential "password" :jclouds.regions "us-east-1a" } })

[jasonm]

You'll need to include the keypair - see https://help.ubuntu.com/community/EC2StartersGuide "Types of Credentials" part 2.3 for a quick explanation of how to retrieve the private and public keys.

Another note, the identity/credential keys must be your AWS access key and secret, not any instance SSH userid/password.

Did you get it up & working eventually?

[rakatti]

thanks Jason.... I will get the keypair and give it a try.... I just went ahead and did a normal EC2 install instead of the storm-deploy... storm is awesome

[adsummos]

I am getting the same unauthorized error and I have been able to deploy using this configuration within the last month or so, but I am no longer able to. I tried using a different AMI, but then I had problems with either zmq or ganglia