RecordSetOptions Struct
Options for a RecordSet.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import * as cdk from 'aws-cdk-lib';
import { aws_route53 as route53 } from 'aws-cdk-lib';
declare const cidrRoutingConfig: route53.CidrRoutingConfig;
declare const geoLocation: route53.GeoLocation;
declare const healthCheck: route53.HealthCheck;
declare const hostedZone: route53.HostedZone;
const recordSetOptions: route53.RecordSetOptions = {
zone: hostedZone,
// the properties below are optional
cidrRoutingConfig: cidrRoutingConfig,
comment: 'comment',
deleteExisting: false,
failover: route53.Failover.PRIMARY,
geoLocation: geoLocation,
healthCheck: healthCheck,
multiValueAnswer: false,
recordName: 'recordName',
region: 'region',
setIdentifier: 'setIdentifier',
ttl: cdk.Duration.minutes(30),
weight: 123,
};
Properties
cidrRoutingConfigCidrRoutingConfigcidr_routing_configCidrRoutingConfigcidrRoutingConfigCidrRoutingConfigCidrRoutingConfigCidrRoutingConfigCidrRoutingConfigCidrRoutingConfig#Default: No CIDR routing configured
A LocationName with an asterisk “*” can be used to create a default CIDR record. CollectionId is still required for default record.
Default: no comment
deleteExistingbooleandelete_existingbooldeleteExistingBooleanDeleteExistingboolDeleteExisting*bool= falsedeprecated#notes
This allows you to deploy a new record set while minimizing the downtime because the new record set will be created immediately after the existing one is deleted. It also avoids "manual" actions to delete existing record sets.
N.B.: this feature is dangerous, use with caution! It can only be used safely when
deleteExistingis set totrueas soon as the resource is added to the stack. Changing an existing Record Set'sdeleteExistingproperty fromfalse -> trueafter deployment will delete the record!
Default: No failover configuration
notes
To configure failover, you add the Failover element to two resource record sets. For one resource record set, you specify PRIMARY as the value for Failover; for the other resource record set, you specify SECONDARY.
You must also include the HealthCheckId element for PRIMARY configurations.
geoLocationGeoLocationgeo_locationGeoLocationgeoLocationGeoLocationGeoLocationGeoLocationGeoLocationGeoLocation#healthCheckIHealthCheckhealth_checkIHealthCheckhealthCheckIHealthCheckHealthCheckIHealthCheckHealthCheckIHealthCheck#Default: No health check configured
Route53 will return this record set in response to DNS queries only if the health check is passing.
multiValueAnswerbooleanmulti_value_answerboolmultiValueAnswerBooleanMultiValueAnswerboolMultiValueAnswer*bool= false#Default: zone root
For example, if you want to create a record for acme.example.com, specify "acme".
You can also specify the fully qualified domain name which terminates with a ".". For example, "acme.example.com.".
Default: Do not set latency based routing
notes
The resource typically is an AWS resource, such as an EC2 instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource record sets, Route 53 selects the latency resource record set that has the lowest latency between the end user and the associated Amazon EC2 Region. Route 53 then returns the value that is associated with the selected resource record set.
Default: Auto generated string
It can only be set when either weight or geoLocation is defined.
This parameter must be between 1 and 128 characters in length.
Default: Do not set weighted routing
notes
Route 53 calculates the sum of the weights for the resource record sets that have the same combination of DNS name and type. Route 53 then responds to queries based on the ratio of a resource's weight to the total.
This value can be a number between 0 and 255.