Error when creating Route53 record set with failover routing policy

252 views
Skip to first unread message

Roshan Mathew Paul

unread,
Feb 9, 2017, 7:55:19 PM2/9/17
to Terraform
I am facing issues when creating a Route53 record set with failover routing policy. I am not able to set evaluate_target_health and health_check_id . I am trying to create a non alias RT53 record set with type: CNAME and routing policy as failover with primary and secondary set to two other record sets. I read few terraform documentation and it looks like evaluate_target_health and health_check_id parameters are supported only for Alias record sets. Could someone in this group please confirm if this is true?

Thanks!

Lowe Schmidt

unread,
Feb 10, 2017, 4:40:01 AM2/10/17
to terrafo...@googlegroups.com
Hello Roshan,

have you tried doing the same steps in the AWS console or via the aws-cli tool? 

It could very well be that it's a constraint on how R53 was designed and not a terraform specific issue.

Regards,

--
Lowe Schmidt | +46 723 867 157

On 10 February 2017 at 01:55, Roshan Mathew Paul <rosha...@gmail.com> wrote:
I am facing issues when creating a Route53 record set with failover routing policy. I am not able to set evaluate_target_health and health_check_id . I am trying to create a non alias RT53 record set with type: CNAME and routing policy as failover with primary and secondary set to two other record sets. I read few terraform documentation and it looks like evaluate_target_health and health_check_id parameters are supported only for Alias record sets. Could someone in this group please confirm if this is true?

Thanks!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terraform-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/e7de5c95-1783-446b-bf33-fadb354339c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Roshan Mathew Paul

unread,
Feb 10, 2017, 7:18:23 PM2/10/17
to Terraform
Hi Lowe, 

Yeah i have got that set up working by manually setting up a RT53 with failover configuration with an associated (RT53) health check alarm that is configured with the (ELB- health check) cloud watch alarm. So when the ELB health check associated to the the Primary RT53 fails that will trigger the RT53 health check alarm to failover to the secondary RT53 record set. 

it might be that capability is not there in the terraform version i am using. I am using terraform 0.7.1v

Thanks!


On Friday, February 10, 2017 at 4:40:01 AM UTC-5, Lowe Schmidt wrote:
Hello Roshan,

have you tried doing the same steps in the AWS console or via the aws-cli tool? 

It could very well be that it's a constraint on how R53 was designed and not a terraform specific issue.

Regards,

--
Lowe Schmidt | +46 723 867 157

On 10 February 2017 at 01:55, Roshan Mathew Paul <rosha...@gmail.com> wrote:
I am facing issues when creating a Route53 record set with failover routing policy. I am not able to set evaluate_target_health and health_check_id . I am trying to create a non alias RT53 record set with type: CNAME and routing policy as failover with primary and secondary set to two other record sets. I read few terraform documentation and it looks like evaluate_target_health and health_check_id parameters are supported only for Alias record sets. Could someone in this group please confirm if this is true?

Thanks!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com.

Lowe Schmidt

unread,
Feb 11, 2017, 3:09:27 AM2/11/17
to terrafo...@googlegroups.com
A hunch, what region are you working in? I remember seeing something about R53 and health checks that didn't work unless it was in one of the US regions. 



--
Lowe Schmidt | +46 723 867 157

To unsubscribe from this group and stop receiving emails from it, send an email to terraform-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/014eb73b-dca5-4eb3-8427-7fbd1257c2c1%40googlegroups.com.

Roshan Mathew Paul

unread,
Feb 11, 2017, 8:47:20 AM2/11/17
to Terraform
I'm trying to failover from us-east-1 to us-west-2 region. I don't know if there is any restrictions of doing that.

Thanks!

Reply all
Reply to author
Forward
0 new messages