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

Route53 pool with health check that doesn't match the cname #504

Open
yfried opened this issue Mar 1, 2020 · 0 comments
Open

Route53 pool with health check that doesn't match the cname #504

yfried opened this issue Mar 1, 2020 · 0 comments

Comments

@yfried
Copy link

@yfried yfried commented Mar 1, 2020

Hi, I'm trying to do something that might be a little different than the general usecase, hope you might be able to help me.
I've created the following setup manually in route53 UI, and now trying to write it down to my octodns config:

In my example.com zone, 2 CNAME records for the same name test.example.com with Weighted routing policy, each with its own matching health check. However, the health checks and the CNAME targets have different domains

  1. test-primary.mydomain.com target, with weight 3, attached to health check that monitors test-health-primary.mydomain.com
  2. test-secondary.mydomain.com target, with weight 7, attached to health check that monitors test-health-secondary.mydomain.com

I'm not sure how to do that, as each record in the yaml requires type and value that have to be defined before the weighted routes and I couldn't find out how to create said healthchecks at all.

Can someone please help me with this?

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

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.