Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminates and Rollback on Route 53 setup #15

Closed
summithr opened this issue Dec 17, 2017 · 3 comments
Closed

Terminates and Rollback on Route 53 setup #15

summithr opened this issue Dec 17, 2017 · 3 comments

Comments

@summithr
Copy link

Hello,

I've tried to utilise this stack twice without success. As soon as it tries to set up the Route 53 section it fails, terminates and rolls back. I'm trying to set it up in ap-southeast-2 using the launch button. Whilst I'm no AWS expert I can't see what I might be doing wrong.

Also, I note whilst ap-southeast-2 is listed as supported in the description here, it is not listed in the CloudFormation stack description, only the other regions are. Any advice is appreciated.

Nathan
Stack Detail.pdf

@michael-newman
Copy link

Nathan,

I had a Route53 rollback due to not creating a Hosted Zone prior to running the template as the template creates the record set, not the Hosted Zone itself--in my case, I was just trying to test the CloudFormation template on test.mysite.com and realized the template rolls back if the test.mysite.com Hosted Zone is not created ahead of time and fails if run just on mysite.com as it does not create my desired test.mysite.com Hosted Zone.

If you are trying to just run this on mysite.com, know the template desires to create an A-Record of www.mysite.com... so, if this record already exists in Route53, it can't create another one and I would expect the template to fail/rollback.

Just sharing a couple of my experiences for your consideration...

Regards, Mike

@darrylsosborne
Copy link
Contributor

Nathan,

Mike is right. Create the hosted zone first using Route 53 then include the domain name as the WPDomain parameter.

It is fully supported in ap-southeast-2.

Let us know if this resolves your issue.

Darryl

@summithr
Copy link
Author

Hello Mike & Darryl,

Thanks for the prompt response, much appreciated.

Yes, I was going to try setting up the record framework and running the script though wasn't such how much needed to be entered without interrupting the script. I may use white label nameservers in the future so I'll consider options in terms of when I set the Route 53 records up. Thanks again for your assistance.

Regards

Nathan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants