Stack Failed in AWS - Hubs Cloud

[jesudarrigrande]

Hi! I want to create my own event with Hubs Cloud and I followed the step by step video of "How to deploy Hubs Cloud AWS", I created my 2 domains with Route 53, create the Key pair and did everithing that the tutorial said from the beginning, but the creation process of my stack failed. Please help me, this is for my title project to graduate from university.

(I appreciate any help, if someone speaks Spanish even better)

[robinkwilson]

Did you agree to the Terms + Conditions and hit "Subscribe"? It looks like you didn't "Subscribe" to hubs cloud yet so it failed. I've never seen this before, so I'm curious if you didn't go through the aws menus all the way (before the cloudformation template).

[jesudarrigrande]

I deleted the stack and create a new one with the same domains and keys, following the instructions of the AWS Troubleshooting, were I selected the "Disabled" option for "Rollback on failure". This is the error the stack failed on, what does it mean?

On another hand, the domain support send me this email to get my website listed on Google, Yahoo, Bing and all the other main search engines. Is this related to the stack problem?

[robinkwilson]

Interesting, this doesn't tell me the classification of errors or any error message -- could be a problem on our side if it's not descriptive -- but I'm not sure that's the first error event. That one looks like the last error event.

Is that the first error message scrolling down as far as you can? Down past the first red error should be green and blue. Usually it tells us which step failed so we can debug it.
For Cloudformation deploys, the last error is at the top. The first is at the bottom.

If that's not the case and that is the first error message, please email [email protected] and mention this discussion thread.

[jesudarrigrande]

Oh ok!! I understand, sorry the one that I sent was the last error. This is the first one: (down past it is all green and blue as you said)

[robinkwilson]

Perfect, that's what we're looking for!!

Seems like your AWS account is missing some permissions to create resources/access AWSLambdaInternal service. Are you using an account with that permission available or a managed AWS account for a larger organization where your permissions to create resources is limited?

I can't help you get that AWS permission since it's a problem on the AWS account permissions side. Ask your AWS account manager to give you creation permissions for AWSLambdaInternal resources.

Alternatively, the fastest way to get you up and running is to create a new AWS account (then you have ALL AWS create permissions available on that account) and go through the Hubs Cloud Cloudformation template again.

[robinkwilson]

[Temporarily marked comment as answered] Unmark this comment as "answered", when you add more information.