dnscontrol/docs/_providers/route53.md

74 lines
2.1 KiB
Markdown
Raw Normal View History

2017-01-12 04:02:45 +08:00
---
name: Route 53
layout: default
jsId: ROUTE53
---
# Amazon Route 53 Provider
## Configuration
By default, you can configure aws setting like the [go sdk configuration](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html). For example you can use environment variables:
```
$ export AWS_ACCESS_KEY_ID=XXXXXXXXX
$ export AWS_SECRET_ACCESS_KEY=YYYYYYYYY
```
It is also possible to specify an aws access key in the providers config json file:
2017-01-12 04:02:45 +08:00
{% highlight json %}
{
"r53":{
"KeyId": "your-aws-key",
"SecretKey": "your-aws-secret-key"
}
}
{% endhighlight %}
## Metadata
This provider does not recognize any special metadata fields unique to route 53.
## Usage
Example javascript:
{% highlight js %}
var REG_NAMECOM = NewRegistrar("name.com","NAMEDOTCOM");
var R53 = NewDnsProvider("r53", "ROUTE53");
2017-01-12 04:02:45 +08:00
D("example.tld", REG_NAMECOM, DnsProvider(R53),
A("test","1.2.3.4")
);
{%endhighlight%}
## Activation
DNSControl depends on a standard [aws access key](https://aws.amazon.com/developers/access-keys/) with permission to list, create and update hosted zones.
## New domains
If a domain does not exist in your Route53 account, DNSControl
will *not* automatically add it. You can do that either manually
via the control panel, or via the command `dnscontrol create-domains`
command.
## Caveats
This code may not function properly if a domain has R53 as a Registrar
but not as a DnsProvider. The situation is described in
[PR#155](https://github.com/StackExchange/dnscontrol/pull/155).
In this situation you will see a message like:
```
----- Registrar: r53
Error getting corrections: AccessDeniedException: User: arn:aws:iam::868399730840:user/dnscontrol is not authorized to perform: route53domains:GetDomainDetail
status code: 400, request id: 48b534a1-7902-11e7-afa6-a3fffd2ce139
Done. 1 corrections.
```
If this happens to you, we'd appreciate it if you could helps us
fix the code. In the meanwhile, you can give the account additional
IAM permissions so that it can do DNS-related actions, or simply
use `NewRegistrar(..., 'NONE')` for now.