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.

Sign up for GitHub

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

Jump to bottom

Use terraform-aws-route53-alias instead of terraform-aws-route53-cluster-hostname #134

Open
razorsedge opened this issue Aug 16, 2020 · 0 comments
Open

Use terraform-aws-route53-alias instead of terraform-aws-route53-cluster-hostname #134

razorsedge opened this issue Aug 16, 2020 · 0 comments
Labels
bug 🐛 An issue with the system

Comments

@razorsedge
Copy link
Contributor

Describe the Bug

Use terraform-aws-route53-alias instead of terraform-aws-route53-cluster-hostname in order to create a Route53 ALIAS instead of a CNAME.

Expected Behavior

I expect Route53 to be configured with an ALIAS and not a CNAME. This way our Beanstalk A record will point to the actual IPs and not process a CNAME.
@razorsedge razorsedge added the bug 🐛 An issue with the system label Aug 16, 2020
@razorsedge razorsedge mentioned this issue Sep 17, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 An issue with the system
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set DNS ALIAS instead of CNAME. teamclairvoyant/terraform-aws-elastic-beanstalk-environment
1 participant
@razorsedge