Unable to create cloudformation stack

Issue #41 resolved
Yohei Onishi created an issue

I am using cloudstack on Windows 7.

  • I could create a s3 bucket and put some files on the bucket. So, cloudstack is working.
  • But I could not create cloudformation. Please help!

I started cloudstack by docker on Windows 7.

docker run -it -p 4567-4578:4567-4578 -p 8080:8080 atlassianlabs/localstack

S3 on the cloudstack is working.

$ aws --endpoint-url=http://192.168.99.100:4572 s3 ls s3://bucket
2017-06-29 15:56:07      21712 serverless-state.json
2017-06-29 15:56:22     590167 serverless-typescript-demo.zip
2017-06-29 15:54:14       1581 serverless.yml

I could not create a cloudformation stack.

$ aws --endpoint-url=http://192.168.99.100:4581 cloudformation create-stack --s
tack-name sample

('Connection aborted.', error(10061, '\x91\xce\x8f\xdb\x82\xcc\x83R\x83\x93\x83s
\x83\x85\x81[\x83^\x81[\x82\xc9\x82\xe6\x82\xc1\x82\xc4\x8b\x91\x94\xdb\x82\xb3\
x82\xea\x82\xbd\x82\xbd\x82\xdf\x81A\x90\xda\x91\xb1\x82\xc5\x82\xab\x82\xdc\x82
\xb9\x82\xf1\x82\xc5\x82\xb5\x82\xbd\x81B'))

Thanks.

Comments (4)

  1. Yohei Onishi reporter

    I tried it on Arch Linux (VM on Virtualbox). It is also not working as follows.

    $ aws --endpoint-url=http://localhost:4581 cloudformation list-stacks
    
    ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))
    
  2. Waldemar Hummer Account Deactivated

    Hi, thanks for reporting. The problem is that the port range of your docker run command is incorrect (should be 4567-4582).

    The preferred way of starting the Docker container these days is:

    pip install localstack
    localstack start --docker
    

    Can you please give that a try? Thanks

    (The reason is that there are a bunch of configurations that need to be passed down to Docker, which we better maintain in a CLI - if we put the entire docker run ... command in the README, it becomes confusing and unreadable.)

    Note: We currently still don't have full support for Windows yet, so if you come across any other errors/problems, please post them here.

  3. Log in to comment