mirror of
https://github.com/coredns/coredns.git
synced 2025-10-27 08:14:18 -04:00
fd7abd9849
This should have everyone, but the process was quite manual. The rename from middleware -> plugin also meant I had to do some extra digging on who actually submitted the PR. I also double checked the current list of people with commit access. Every plugin now has an OWNERS, except *reverse*. I'll file a bug for that.
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 only supports A and AAAA records. The route53 plugin can be used when coredns is deployed on AWS.
Syntax
route53 [ZONE:HOSTED_ZONE_ID...] {
[aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY]
}
- ZONE the name of the domain to be accessed.
- 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.
Examples
Enable route53, with implicit aws credentials:
. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7
}
Enable route53, with explicit aws credentials:
. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY
}
}