Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-12-03 00:54:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

plugins/route53: add AWS credentials file support (#2118)

Browse Source 
Automatically submitted.
This commit is contained in:
Can Yucel
2018-09-25 15:57:16 -07:00
committed by corbot[bot]
parent a0396e2673
commit 8148408301
3 changed files with 75 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
plugin/route53/README.md
View File

@@ -16,6 +16,7 @@ The route53 plugin can be used when coredns is deployed on AWS or elsewhere.
route53 [ZONE:HOSTED_ZONE_ID...] {
[aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY]
upstream [ADDRESS...]
credentials PROFILE [FILENAME]
fallthrough [ZONES...]
}
~~~
@@ -30,6 +31,9 @@ route53 [ZONE:HOSTED_ZONE_ID...] {
to external hosts (eg. used to resolve CNAMEs). If no **ADDRESS** is given, CoreDNS will resolve
against itself. **ADDRESS** can be an IP, an IP:port or a path to a file structured like
resolv.conf (**NB**: Currently a bug (#2099) is preventing the use of self-resolver).
* `credentials` used for reading the credential file and setting the profile name for a given zone.
* **PROFILE** AWS account profile name. Defaults to `default`.
* **FILENAME** AWS credentials filename. Defaults to `~/.aws/credentials`
are used.
* `fallthrough` If zone matches and no record can be generated, pass request to the next plugin.
If **[ZONES...]** is omitted, then fallthrough happens for all zones for which the plugin
@@ -39,7 +43,7 @@ route53 [ZONE:HOSTED_ZONE_ID...] {
## Examples
Enable route53 with implicit aws credentials and an upstream:
Enable route53 with implicit AWS credentials and an upstream:
~~~ txt
. {
@@ -48,7 +52,7 @@ Enable route53 with implicit aws credentials and an upstream:
}
~~~
Enable route53 with explicit aws credentials:
Enable route53 with explicit AWS credentials:
~~~ txt
. {
@@ -67,3 +71,13 @@ Enable route53 with fallthrough:
}
}
~~~
Enable route53 with AWS credentials file:
~~~ txt
. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
credentials_file some-user
}
}
~~~