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

Make route53 independent of ec2 #527

Closed
grahamc opened this issue Oct 19, 2016 · 6 comments
Closed

Make route53 independent of ec2 #527

grahamc opened this issue Oct 19, 2016 · 6 comments

Comments

@grahamc
Copy link
Member

grahamc commented Oct 19, 2016

I (naively) expected to be able to use route53 on my other systems. Example:

{
  nix-dev = { resources, pkgs, lib, ... }: {
    deployment.targetEnv = "hetzner";
    deployment.route53.accessKeyId = "foo";
    deployment.route53.hostName = "foo.my-zone";
  };
}

I expected foo.my-zone to be created in my route53 hosted zone for this hetzner machine.

@roberth
Copy link
Member

roberth commented Mar 27, 2017

Maybe we can change the title to 'Make route53 independent of ec2'?

@grahamc grahamc changed the title Support using route53 on other backends Make route53 independent of ec2 Apr 2, 2017
@grahamc
Copy link
Member Author

grahamc commented Apr 2, 2017

Done, @robertth.

@domenkozar
Copy link
Member

Is anyone looking into this? We (https://github.com/input-output-hk) would like to look into round-robin DNS routing using multi-value.

@domenkozar
Copy link
Member

Ok then :)

@domenkozar
Copy link
Member

This was implemented in 97c0f9f

But it's not available in the manual yet (recordset, hosted zone, healthcheck).

@domenkozar
Copy link
Member

Added to the manual in 5ecfde3

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

No branches or pull requests

3 participants