Scalr v1 Instalation and Configuration

Can you add some verbiage about "Where XXXXXXXXXXXX is a Key Name" Where do I config the $AWS_KEYNAME?

Key Name is "Your Access Key ID" that can be taken on "AWS Access Identifiers" page inside AWS portal. Going to adjust the text, thanks.

Alex,

Do you think you could get scalr working for Linode.com? Better cost structure and mor flexible sizing of nodes.

I just want to know if i should install these in my own server( not EC2 ). I am quite new to Amazon Web Services and Scalr.

thanashyam, it's entirely up to you.

It's a little unclear from the docs as to what should be entered in the AWS Settings section of the Core Settings page.

Just to be clear, is this correct: Account ID = AWS Account Number eg. 123412341234 Key Name = The string between cert-XXXX.pem and pk-XXXX.pem in the x.509 certificates that get copied to /etc Access Key: AWS Secret Key Access Key ID: Public Access Key ID as shown in the AWS account page

Is this correct?

Thanks

I had to install Scalr today on Amazon EC2. Some of the documentation found on Internet is very old (dating from scalr 0.5) and the one you provide here is ... how should I say ... spartan. So I've wrote down everything I've done in the process of installing scalr on a new instance running Ubuntu Intrepid Ibex. I hope it will help other users to install scalr.

Here is the link: http://blog.getasysadmin.com/2008/11/how-to-install-scalr-on-ubuntu-810-ec2.html

If you find errors please let me know. Good luck!

I receive often this error WSSESoapClient::__doRequest? Failure Signing Data (Please, check your keys) in the Shared roles » View section.

The AWS settings is not clear. Account ID = AWS Account Number Key Name is the string between cert-xxxxxx.pem, these files must be copied in the /etc/ Access Key = what is ? Access Key ID = is the public Access Key ID

Maybe The Access Key is the AWS Secret Key ? If yes, the error is not resolved.

Please specify all the value in the Settings » General Section Thanks Fabio

I find the way, finally. The path where must be copied the two files .pem is /etc , but the /etc under the scalr/app/etc. I think more than me has mistaken this.

What's the diff between the scalr-ami/ images and scalr-images/ in ec2-describe-images? Also, do any of the AMIs in ec2 provide an already built, working Scalr install?

after installing (following Octavian´s nice guide), I assume I have to create a new client first before I can create a new app/farm? After creating a new client and trying to login with this new client, I keep on getting the error:

"Incorrect login or password"

anyone can help?

In order to use a freshly created client it needs to be activated..

After trying out scalr again for the 3rd time since inception I notice some really user-unfriendly things about it that made me go 'hrmmm??' #1, as above is users aren't activated by default (or have an option under their edit profile to mark them as active my default, or try to log in as them without any indication error that the account is not active.) #2 is that the field names for core settings don't match the AWS terms or have any help sentences, which would help greatly for matching things up. #3 is there is no documentation for DNS settings, which I have been using bind9 for about 8 years, and its still a bit confusing as to what it's going to actually do, and what settings are needed.) I think a bit of inline documentation is in order, even if it is a link or a single sentence explaining the setting next to the form element. </2cents>

Also on this new installation, I'm getting xml errors trying to go through the client's new farm wizard as of the latest version... sigh...

Skizzles, as for your error that you get, see the following blog for troubleshooting: http://blog.getasysadmin.com/2008/11/scalr-errors-after-install.html