incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-257) AWS Api is not correctly deployed
Date Sun, 07 Oct 2012 22:00:05 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471339#comment-13471339
] 

Prachi Damle edited comment on CLOUDSTACK-257 at 10/7/12 9:59 PM:
------------------------------------------------------------------

I tested this with latest build on 4.0 and cloudstack-aws-api-register worked successfully.
I could register a user an run ec2 commands without issues.

Steps I followed are:

- build and deploy latest 4.0 
- Create a user and generate keys
- Enable EC2 via global settings - enable.ec2.api to true
- Restart Management server


User client setup:
1. Copy the API key and Secret key from CS UI
2. Generate a private key and a self-signed X.509 certificate. Substitute your own desired
storage location for /path/to/… below. $ openssl req -x509 -nodes -days 365 -newkey rsa:2048
-keyout /path/to/private_key.pem -out /path/to/cert.pem
3. Register the mapping from the X.509 certificate to the API/Secret keys. 
$ cloudstack-aws-api-register --apikey=<User’s API key> --secretkey=<User’s Secret
key> --cert=</path/to/cert.pem> --url=http://<server>:7080/awsapi
4. Be sure you have the right version of EC2 Tools. The supported version is available at
http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip.
5. Set up the environment variables that will direct the tools to the server. As a best practice,
you may wish to place these commands in a script that may be sourced before using the AWS
API translation feature. 
$ export EC2_CERT=/path/to/cert.pem 
$ export EC2_PRIVATE_KEY=/path/to/private_key.pem 
$ export EC2_URL=http://<server>:7080/awsapi 
$ export EC2_HOME=/path/to/EC2_installation_directory

                
      was (Author: prachidamle):
    I tested this with latest build on 4.0 and cloudstack-aws-api-register worked successfully.
I could register a user an run ec2 commands without issues.

Steps I followed are:

- build and deploy latest 4.0 
- Create a user and generate keys
- Enable EC2 via global settings - enable.ec2.api to true
- Restart Management server


User client setup:
1. Copy the API key and Secret key from CS UI
2. Generate a private key and a self-signed X.509 certificate. Substitute your own desired
storage location for /path/to/… below. $ openssl req -x509 -nodes -days 365 -newkey rsa:2048
-keyout /path/to/private_key.pem -out /path/to/cert.pem
3. Register the mapping from the X.509 certificate to the API/Secret keys. 
$ cloudstack-aws-api-register --apikey=<User’s CloudPlatform API key> --secretkey=<User’s
CloudPlatform Secret key> --cert=</path/to/cert.pem> --url=http://<server>:7080/awsapi
4. Be sure you have the right version of EC2 Tools. The supported version is available at
http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip.
5. Set up the environment variables that will direct the tools to the server. As a best practice,
you may wish to place these commands in a script that may be sourced before using the AWS
API translation feature. 
$ export EC2_CERT=/path/to/cert.pem 
$ export EC2_PRIVATE_KEY=/path/to/private_key.pem 
$ export EC2_URL=http://<server>:7080/awsapi 
$ export EC2_HOME=/path/to/EC2_installation_directory

                  
> AWS Api is not correctly deployed
> ---------------------------------
>
>                 Key: CLOUDSTACK-257
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-257
>             Project: CloudStack
>          Issue Type: Bug
>          Components: AWSAPI
>    Affects Versions: pre-4.0.0
>         Environment: Centos 6.3
> non-oss build 60
>            Reporter: Pedro Navarro Pérez
>            Assignee: Likitha Shetty
>            Priority: Blocker
>             Fix For: 4.0.0
>
>         Attachments: api-server.log, management-server.log
>
>
> 1. Fresh install
> 2. Enable the EC2 service via global configuration settings
> 3. Generate API keys for the user
> 4. Call cloudstack-aws-api-register with the input parameters.
> Error User registration failed with http error code: 400

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message