Creates a new health check.
route53_create_health_check(CallerReference, HealthCheckConfig)[required] A unique string that identifies the request and that allows you to retry
a failed CreateHealthCheck request without the risk of creating two
identical health checks:
If you send a CreateHealthCheck request with the same
CallerReference and settings as a previous request, and if the
health check doesn\'t exist, Amazon Route 53 creates the health
check. If the health check does exist, Route 53 returns the settings
for the existing health check.
If you send a CreateHealthCheck request with the same
CallerReference as a deleted health check, regardless of the
settings, Route 53 returns a HealthCheckAlreadyExists error.
If you send a CreateHealthCheck request with the same
CallerReference as an existing health check but with different
settings, Route 53 returns a HealthCheckAlreadyExists error.
If you send a CreateHealthCheck request with a unique
CallerReference but settings identical to an existing health
check, Route 53 creates the health check.
[required] A complex type that contains settings for a new health check.
svc$create_health_check(
CallerReference = "string",
HealthCheckConfig = list(
IPAddress = "string",
Port = 123,
Type = "HTTP"|"HTTPS"|"HTTP_STR_MATCH"|"HTTPS_STR_MATCH"|"TCP"|"CALCULATED"|"CLOUDWATCH_METRIC",
ResourcePath = "string",
FullyQualifiedDomainName = "string",
SearchString = "string",
RequestInterval = 123,
FailureThreshold = 123,
MeasureLatency = TRUE|FALSE,
Inverted = TRUE|FALSE,
Disabled = TRUE|FALSE,
HealthThreshold = 123,
ChildHealthChecks = list(
"string"
),
EnableSNI = TRUE|FALSE,
Regions = list(
"us-east-1"|"us-west-1"|"us-west-2"|"eu-west-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-northeast-1"|"sa-east-1"
),
AlarmIdentifier = list(
Region = "us-east-1"|"us-east-2"|"us-west-1"|"us-west-2"|"ca-central-1"|"eu-central-1"|"eu-west-1"|"eu-west-2"|"eu-west-3"|"ap-east-1"|"me-south-1"|"ap-south-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-northeast-1"|"ap-northeast-2"|"ap-northeast-3"|"eu-north-1"|"sa-east-1"|"cn-northwest-1"|"cn-north-1"|"af-south-1"|"eu-south-1"|"us-gov-west-1"|"us-gov-east-1"|"us-iso-east-1"|"us-isob-east-1",
Name = "string"
),
InsufficientDataHealthStatus = "Healthy"|"Unhealthy"|"LastKnownStatus"
)
)
For information about adding health checks to resource record sets, see HealthCheckId in ChangeResourceRecordSets.
ELB Load Balancers
If you\'re registering EC2 instances with an Elastic Load Balancing (ELB) load balancer, do not create Amazon Route 53 health checks for the EC2 instances. When you register an EC2 instance with a load balancer, you configure settings for an ELB health check, which performs a similar function to a Route 53 health check.
Private Hosted Zones
You can associate health checks with failover resource record sets in a private hosted zone. Note the following:
Route 53 health checkers are outside the VPC. To check the health of an endpoint within a VPC by IP address, you must assign a public IP address to the instance in the VPC.
You can configure a health checker to check the health of an external resource that the instance relies on, such as a database server.
You can create a CloudWatch metric, associate an alarm with the
metric, and then create a health check that is based on the state of
the alarm. For example, you might create a CloudWatch metric that
checks the status of the Amazon EC2 StatusCheckFailed metric, add
an alarm to the metric, and then create a health check that is based
on the state of the alarm. For information about creating CloudWatch
metrics and alarms by using the CloudWatch console, see the Amazon CloudWatch User Guide.