Package: octodns-route53
Route53Provider provider for octoDNSAnoctoDNSprovider that targetsRoute53.InstallationCommand linepip install octodns-route53requirements.txt/setup.pyPinning specific versions or SHAs is recommended to avoid unplanned upgrades.Versions# Start with the latest versions and don't just copy what's here
octodns==0.9.14
octodns-route53==0.0.1SHAs# Start with the latest/specific versions and don't just copy what's here
-e git+https://git@github.com/octodns/octodns.git@9da19749e28f68407a1c246dfdf65663cdc1c422#egg=octodns
-e git+https://git@github.com/octodns/octodns-route53.git@ec9661f8b335241ae4746eea467a8509205e6a30#egg=octodns_route53ConfigurationRoute53 Providerproviders:route53:class:octodns_route53.Route53Provider# The AWS access key idaccess_key_id:env/AWS_ACCESS_KEY_ID# The AWS secret access keysecret_access_key:env/AWS_SECRET_ACCESS_KEY# The AWS session token (optional)# Only needed if using temporary security credentials#session_token: env/AWS_SESSION_TOKENAlternatively, you may leave out access_key_id, secret_access_key and session_token.  This will result in boto3 deciding authentication dynamically.In general the account used will need full permissions on Route53.Ec2Souceproviders:ec2:class:octodns_route53.Ec2Source# auth options are the same as Route53Provideraccess_key_id:env/AWS_ACCESS_KEY_IDsecret_access_key:env/AWS_SECRET_ACCESS_KEY# The region in which to look for EC2 instances, required.region:us-east-1# Prefix for tag keys containing fqdn(s)#tag_prefix: octodns#ttl: 3600In general the account used will need read permissions on EC2 instances.Records are driven off of the tags attached to the EC2 instances. The "Name" tag and any tags starting withtag_prefixare considered.The value of the tag should be one or more fqdns separated by a/character.When a zone is being populated any fqdns matching the zone name will result in records. When the instance has a private IPv4 address an A record will be created. When the instance has an IPv6 address a AAAA record will be created.When the zone is a sub-zone of in-addr.arpa. PTR records will be created for private IPv4 addresses that match the zone. The value(s) will be the fqdn(s) associated with that private IPv4 address.When the zone is a sub-zone of ip6.arpa. PTR records will be created for IPv6 addresses that match the zone. The value(s) will be the fqdn(s) associated with that IPv6 address.ElbSouceproviders:elb:class:octodns_route53.ElbSource# auth options are the same as Route53Provideraccess_key_id:env/AWS_ACCESS_KEY_IDsecret_access_key:env/AWS_SECRET_ACCESS_KEY# The region in which to look for ELB instances, required.region:us-east-1# Prefix for tag keys containing fqdn(s)#tag_prefix: octodns#ttl: 3600In general the account used will need read permissions on ELB instances and tags.Records are driven off of the ELB name and the tags attached to the ELB instances. Any tag withtag_prefixis considered.The value of the tag should be one or more fqdns separated by a/character.When a zone is being populated any fqdns matching the zone name will result in records CNAME records with the target value being the DNSName of the ELB instance.Example Tags for EC2/ELB# This will result in an ALIAS record for example.com. -> DNSNameoctodns:example.com.# This will result in a CNAME record for foo.example.com. -> DNSNameoctodns:foo.example.com.# This will result in CNAME records for foo.example.com. and bar.other.com.# -> DNSNameoctodns:foo.example.com./bar.other.com.# Tags are limited to 255 characters so in order to support long and/or# numerous fqdns tags prefixed with `tag_prefix` are considered. It is also# acceptable to add multiple tags rather than separating things with `/`octodns-1:foo.example.com.octodns-2:bar.other.com.Processorsprocessors:awsacm:class:octodns.processor.acme.AwsAcmMangingProcessor...zones:something.com.:...processors:-awsacm...Support InformationRecordsA, AAAA, CAA, CNAME, MX, NAPTR, NS, PTR, SPF, SRV, TXTRoot NS RecordsRoute53Provider supports full root NS record management.DynamicRoute53Provider supports dynamic records, CNAME health checks don't support a Host header.Provider Specific TypesRoute53Provider/ALIASadds support for the Route53 specific symlink style alias records.# "symlink" to another record in the same zonealias:type:Route53Provider/ALIASvalues:# ALIAS for the zone APEX A record-type:A# ALIAS for www.whatever.com. AAAA-evaluate-target-health:false# same-zone aliases omit the zone namename:wwwtype:AAAA# "symlink" to a AWS servicealb:type:Route53Provider/ALIASvalue:# default for evaluate-target-health is Falseevaluate-target-health:true# hosted-zone-id should only be used when pointing to service endpointshosted-zone-id:Z42SXDOTRQ7X7Kname:dualstack.octodns-testing-1165866977.us-east-1.elb.amazonaws.com.type:AHealth Check OptionsSeehttps://github.com/octodns/octodns/blob/master/docs/dynamic_records.md#health-checksfor information on health checking for dynamic records. Route53Provider supports the following options:KeyDescriptionDefaultfailure_thresholdFailure threshold before state change, 1-106measure_latencyShow latency in AWS consoletruerequest_intervalHealthcheck interval [10|30] seconds10---octodns:healthcheck:host:my-host-namepath:/dns-health-checkport:443protocol:HTTPSroute53:healthcheck:failure_threshold:3measure_latency:falserequest_interval:30DevelopmentSee the/script/directory for some tools to help with the development process. They generally follow theScript to rule them allpattern. Most useful is./script/bootstrapwhich will create a venv and install both the runtime and development related requirements. It will also hook up a pre-commit hook that covers most of what's run by CI.