mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00

Files

Matt Kulka 45e17c325c [plugin/route53]: Increase ListResourceRecordSets paging size. (#3073 )

without the paging parameter set, it will default to 100 records per request. with large enough zones and
potentially multiple coredns daemons configured to pull from route 53, this can quickly add up and reach
aws global api rate limits (5/sec per root account). increasing paging to max can help reduce the number
of requests needed to pull records for a zone without no down side that i am aware of.

this helps issue #2353, but probably is not a complete fix.

Signed-off-by: Matt Kulka <mkulka@parchment.com>

2019-07-31 12:09:10 -07:00

log_test.go

Clean up tests logging (#1979 )

2018-07-19 16:23:06 +01:00

OWNERS

Add @dilyevsky to reviewers. (#2094 )

2018-09-13 15:22:57 -07:00

README.md

plugin/route53: small doc cleanups (#3016 )

2019-07-17 13:40:15 -07:00

route53_test.go

Run gofmt -w -s on codebase (#2773 )

2019-04-08 11:13:46 +01:00

route53.go

[plugin/route53]: Increase ListResourceRecordSets paging size. (#3073 )

2019-07-31 12:09:10 -07:00

setup_test.go

Update Caddy to 1.0.1, and update import path (#2961 )

2019-07-03 09:04:47 +08:00

setup.go

plugin/route53: fix IAM credential file (#2983 )

2019-07-15 05:56:28 +00:00

README.md

route53

Name

route53 - enables serving zone data from AWS route53.

Description

The route53 plugin is useful for serving zones from resource record sets in AWS route53. This plugin supports all Amazon Route 53 records (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html). The route53 plugin can be used when coredns is deployed on AWS or elsewhere.

Syntax

route53 [ZONE:HOSTED_ZONE_ID...] {
    aws_access_key [AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY]
    credentials PROFILE [FILENAME]
    fallthrough [ZONES...]
}

ZONE the name of the domain to be accessed. When there are multiple zones with overlapping domains (private vs. public hosted zone), CoreDNS does the lookup in the given order here. Therefore, for a non-existing resource record, SOA response will be from the rightmost zone.
HOSTED_ZONE_ID the ID of the hosted zone that contains the resource record sets to be accessed.
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY the AWS access key ID and secret access key to be used when query AWS (optional). If they are not provided, then coredns tries to access AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file, instance profile credentials, etc.
credentials is 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 is authoritative. If specific zones are listed (for example in-addr.arpa and ip6.arpa), then only queries for those zones will be subject to fallthrough.
ZONES zones it should be authoritative for. If empty, the zones from the configuration block.

Examples

Enable route53 with implicit AWS credentials and resolve CNAMEs via 10.0.0.1:

. {
	route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7
    forward . 10.0.0.1
}

Enable route53 with explicit AWS credentials:

. {
    route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
      aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY
    }
}

Enable route53 with fallthrough:

. {
    route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 example.gov.:Z654321543245 {
      fallthrough example.gov.
    }
}

Enable route53 with multiple hosted zones with the same domain:

. {
    route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 example.org.:Z93A52145678156
}