Cloudformation Failure : GitLab template

Four Stars

Cloudformation Failure : GitLab template

Hi,

 

I have tried the Talend AWS Quick Start (https://aws.amazon.com/quickstart/architecture/data-lake-with-talend-big-data-platform/) 6 times in different regions, all with the same error. It appears there is a timeout.

 

screenshot-eu-west-1.console.aws.amazon.com 2018-02-01 15-01-20-261.png

 

 

 

I have tried twice in each of these regions
US-EAST1

US-WEST1

EU-WEST1

 

The settings are rather basic - I am doing an investigation so I do not change any defaults.
I have tried each region with all optional stacks true on one occasion and false on another.

Any ideas on what I can do to get this to run would be great.

 

Dominic Messenger

 


Accepted Solutions
Six Stars

Re: Cloudformation Failure : GitLab template

Dominic

 

I'm not sure if I ran in to the same issue you're having but I did get failures and rollback on GitLab. In my case what I found was, I was using passwords that were to complex. There's only a handful of special characters that you can use with the passwords and I don't think the form catches that yet. The other issue I ran in to was trying to use the same password in multiple places. 

 

This is an example of a password that works for me.
d1jPvA2Ef9TR!

 

The frustrating thing that I found was that you lose the error messages on rollback. Edward Ost suggested disabling the rollback. You enable this after you fill in the form. One the same page where you enter in your tags, there is an advanced section. Change the rollback from yes to no. That should keep everything running and give you a chance to diagnose. 


All Replies
Six Stars

Re: Cloudformation Failure : GitLab template

Dominic

 

I'm not sure if I ran in to the same issue you're having but I did get failures and rollback on GitLab. In my case what I found was, I was using passwords that were to complex. There's only a handful of special characters that you can use with the passwords and I don't think the form catches that yet. The other issue I ran in to was trying to use the same password in multiple places. 

 

This is an example of a password that works for me.
d1jPvA2Ef9TR!

 

The frustrating thing that I found was that you lose the error messages on rollback. Edward Ost suggested disabling the rollback. You enable this after you fill in the form. One the same page where you enter in your tags, there is an advanced section. Change the rollback from yes to no. That should keep everything running and give you a chance to diagnose. 

Four Stars

Re: Cloudformation Failure : GitLab template

Thanks, I'll try very simple passwords.

I noticed that the Redshift password profile was different to the others, but the password I was using (across all, btw, as this is just a test install) was very simple.

 

I'm deploying without rollback as standard.

 

Dominic

Six Stars

Re: Cloudformation Failure : GitLab template

I'm not sure why using the same password for all causes a problem but it was an issue for me. 

Employee

Re: Cloudformation Failure : GitLab template

Yep, I had the same issue myself.  We don't really control the password requirements for the services we consume, and those requirements are somewhat inconsistent.  I think Talend1234 actually met the requirement for most of them.  Let me know if you have any other issues.  We did take an action item thanks to Dustin to see if we can track down the password requirements and elaborate our regex expressions for the Quickstart form.  Ideally we want to reject bad passwords up front rather than getting to the actual build stage only to throw an error.

 

Ed