Cloudformation deploy failing to create S3 bucket

Issue #15 resolved
Peter McGuire created an issue

Using attached yaml file and command (works when deploying to AWS directly):

aws --endpoint-url=http://localhost:4581 cloudformation deploy --template-file website.yaml --stack-name littlestack

Response is:

Unable to parse response (syntax error: line 1, column 54), invalid XML received: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>

Comments (3)

  1. Waldemar Hummer Account Deactivated

    Thanks for reporting, this functionality is currently not implemented, but it is relatively high up in the priority list and we will (hopefully) be able to add this soon.

  2. Waldemar Hummer Account Deactivated

    Basic support for CloudFormation deployments has been implemented in this commit: https://bitbucket.org/atlassian/localstack/commits/9940a665eb821283053c54e8029cbe9e3f68a575

    Please note that this is only an initial implementation with very rudimentary support (basically only S3 buckets and SQS queues are supported at the moment). Going forward, we can extend the CloudFormation deployment logic to cover the full set of resources in complex templates. I would also be very happy to receive pull requests to cover the new functionality. Thanks

  3. Log in to comment