There seems to be some access constraint with `terraform init` regarding the S3 bucket where the actual terraform configuration resides, preventing me from testing this without access (on my current machine anyways). I'll take a look at this later tonight. This might be solved by adding some base64 string to the bucket names (to avoid collisions) and some logic to check whether QASM buckets exist in the account of the deployer. It also could be a skill issue on my part.

It is probably worth looking into some interoperability (for both testing and deployment) between locally available and assumed AWS credentials. Either a config specification for AWS_PROFILE or a "setup GUI" to do so would be handy to make sure things are deployed in the right spot, and make pure-standalone applications easier to test. (By pure-standalone, I mean applications that access only public resources or the necessary credentials are bundled in deployment, e.g. the demo build).

Originally posted by @joshua-dean in #19 (comment)