-
Notifications
You must be signed in to change notification settings - Fork 907
Unable to launch stack #15
Comments
@imkheong I am also facing same problem and my scenario is identical to yours. |
@imkheong Steps :
|
Still getting error on stack creation, I see that templates are already fixed to nodejs4.3. |
@rohitanytime During stack creation, under the Specify Details page, the 'HostingBucket' field is empty, just put a random name. That resolved my issue. |
Thanks, I got it fixed.
…Sent from my iPad
On Dec 4, 2017, at 8:53 PM, Jeffery He ***@***.***> wrote:
@rohitanytime During stack creation, under the Specify Details page, the 'HostingBucket' field is empty, just put a random name. That solved my issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The HostingBucket field needs to be filled in with an allowed name. A random name is fine if it's sufficiently random. From http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html: "A bucket name must be unique across all existing bucket names in Amazon S3. We recommend that all bucket names comply with DNS naming conventions." I finally put a timestamp at the end of mine. Also, based on my experience getting this to work, DynamoDB table names need to be unique within an Amazon account. So if the stack creation fails you need to delete any partially-created stacks before trying again. |
getting error for ConfigHelperStack...please help and advise Embedded stack arn:aws:cloudformation:us-east-1:570585003507:stack/serverless-web-refarch-2-ConfigHelperStack-U9F0YSLGOX2J/b6b718b0-9827-11e9-8a12-0a3a983b5e88 was not successfully created: The following resource(s) failed to create: [AddConfigSetting].| Physical ID:arn:aws:cloudformation:us-east-1:570585003507:stack/serverless-web-refarch-2-ConfigHelperStack-U9F0YSLGOX2J/b6b718b0-9827-11e9-8a12-0a3a983b5e88 |
Firstly, great effort in putting up the reference architecture, well done guys!
I have been trying to launch the stack recently to no avail.
I was using a user with admin role, and subsequently a root user (this is for my personal account, and I know this is a security risk). I used the default setting during the launch, I did not use IAM role to launch the stack.
This is the error when I click on the stack in Cloud Formation:
What could be the issue and how can I get around the error?
Thanks!
The text was updated successfully, but these errors were encountered: