Rajani,
Take a look at your ~/.aws/config and make sure the keys are correct.  Also
is you are using a current version of the AWS CLI make sure to add the
signature_version block as mentioned in the ec2stack readme.

>From the above looks like you are not using profiles therefore your config
file should look something like this:


[default]

output = json

region =

aws_access_key_id = xxxxxxxxxx

aws_secret_access_key = yyyyyyyyy

ec2 =

    signature_version = v2



Regards,
Carlos


On Fri, Aug 28, 2015 at 4:04 AM, Rajani Karuturi <rajani.karut...@citrix.com
> wrote:

> Hi Sebastien,
>
> I am trying to configure and use ec2stack. This is what I have done
>
> $ pip install awscli
> $ cd cloudstack-ec2stack
> $ python setup.py install
> $ ec2stack-configure
> $ ec2stack &
> $ ec2stack-register http://localhost:5000 cs_api_key cs_secret_key
> $ aws ec2 describe-images --endpoint=http://localhost:5000
> # it gave the below error message
> # Unable to locate credentials. You can configure credentials by running
> "aws configure”.
> $ aws configure # gave AWS api and secret key
> $ aws ec2 describe-images --endpoint=http://localhost:5000
> # this is the output I see
> # localhost - - [28/Aug/2015 16:25:24] "POST / HTTP/1.1" 401 -
> # ‘RequestID’
>
> I don’t see anything in cloudstack logs
>
> If I change the api key and secret key to
> $ ec2stack-register http://localhost:5000 aws_api_key aws_secret_key
>
> I see below in cloudstack logs
>
> 2015-08-28 16:22:37,118 DEBUG [c.c.a.ApiServlet]
> (1188257713@qtp-2099531272-3:ctx-29d29342) ===START===  10.147.28.40 --
> GET
> apikey=aws_api_key&command=listTemplates&listAll=true&response=json&templatefilter=executable&signature=6OggS6Zb2vbejw60BbFbYhaiEEY%3D
> 2015-08-28 16:22:37,120 DEBUG [c.c.a.ApiServer]
> (1188257713@qtp-2099531272-3:ctx-29d29342 ctx-574b2cf4) apiKey does not
> map to a valid user -- ignoring request, apiKey:aws_api_key
> 2015-08-28 16:22:37,122 DEBUG [c.c.a.ApiServlet]
> (1188257713@qtp-2099531272-3:ctx-29d29342 ctx-574b2cf4) ===END===
> 10.147.28.40 -- GET
> apikey=aws_api_key&command=listTemplates&listAll=true&response=json&templatefilter=executable&signature=6OggS6Zb2vbejw60BbFbYhaiEEY%3D
>
>
> where are the logs for ec2stack? how can I see what it is happening?
>
> ~Rajani
>
>
>
> On 27-Aug-2015, at 12:54 am, sebgoa <run...@gmail.com> wrote:
>
> >
> > On Aug 26, 2015, at 7:08 PM, David Nalley <da...@gnsa.us> wrote:
> >
> >> +1 (binding)
> >>
> >> sigs and hashes look good.
> >> builds fine
> >> no binaries present.
> >> A few files seem to be missing license headers, but I don't think it's
> >> a blocker.
> >> License and NOTICE appear to be correct.
> >>
> >> I wish we pointed to the cloudstack docker hub account rather than the
> >> runseb account, but don't think it's a blocker for release
> >>
> >
> > missed that, now fixed.
> >
> >> --David
> >>
> >> On Wed, Aug 26, 2015 at 5:25 AM, sebgoa <run...@gmail.com> wrote:
> >>> Hi All,
> >>>
> >>> I've created a 0.8.0 release of EC2stack, with the following artifacts
> up for a vote:
> >>>
> >>> Git Branch and Commit SH:
> >>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-ec2stack.git
> >>>
> >>> Commit: a61d7c01129dfe4c31515a48e0f6b4a53436c208
> >>>
> >>> There are no code changes from the time the code was donated to the
> ASF, only license headers and a Dockerfile.
> >>>
> >>> Source release (checksums and signatures are available at the same
> >>> location):
> >>> https://dist.apache.org/repos/dist/dev/cloudstack/ec2stack-0.8.0/
> >>>
> >>> PGP release keys (signed using 8F89EB84):
> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>>
> >>> For testing functionality you might consider using the Docker image:
> >>> docker pull cloudstack/cloudstack-ec2stack
> >>>
> >>> Do remember that the official release artifact is the source code,
> which needs to contain proper licensing and proper signatures.
> >>>
> >>> Vote will be open for 72 hours.
> >>>
> >>> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> >>>
> >>> [ ] +1  approve
> >>> [ ] +0  no opinion
> >>> [ ] -1  disapprove (and reason why)
> >
>
>

Reply via email to