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

Bug: Cannot create a production stack when a non-aws DNS is used #105

Open
gkpty opened this issue Aug 14, 2020 · 0 comments
Open

Bug: Cannot create a production stack when a non-aws DNS is used #105

gkpty opened this issue Aug 14, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@gkpty
Copy link
Collaborator

gkpty commented Aug 14, 2020

Describe the bug
when using godaddy DNS the full template fails to deploy because the ACM certificate cannot be verified automatically when the DNS used is not route53.

We will have to keep certificates outside of the cloudformation template for now. This can hopefully be fixed when using terraform.

for now must make a function that creates and verifies the ACM certificate using the AWS SDK and the createRecord method from the domains SDK.

this function must be called right before calling the deployFullTemplate.

the verification of the cert can be run in parallel to the template deployment

@gkpty gkpty added the bug Something isn't working label Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant