* A complex type that contains information about the health check. *
* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class HealthCheckConfig implements Serializable, Cloneable { /** *
* The IPv4 or IPv6 IP address of the endpoint that you want Amazon Route 53 to perform health checks on. If you
* don't specify a value for IPAddress, Route 53 sends a DNS request to resolve the domain name that
* you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in RFC
* 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with your
* EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP address of
* your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create health * checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*
* The port on the endpoint that you want Amazon Route 53 to perform health checks on. *
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
*/ private String type; /** *
* The path, if any, that you want Amazon Route 53 to request when performing health checks. The path can be any
* value for which your endpoint will return an HTTP status code of 2xx or 3xx when the endpoint is healthy, for
* example, the file /docs/route53-health-check.html. You can also include query string parameters, for example,
* /welcome.html?language=jp&login=y.
*
* Amazon Route 53 behavior depends on whether you specify a value for IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP health
* checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53 to perform
* health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for Type,
* Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at the
* interval that you specify for RequestInterval. Using an IPv4 address that DNS returns, Route 53 then
* checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to the
* endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to specify
* the endpoint only by FullyQualifiedDomainName, we recommend that you create a separate health check
* for each endpoint. For example, create a health check for each HTTP server that is serving content for
* www.example.com. For the value of FullyQualifiedDomainName, specify the domain name of the server
* (such as us-east-2-www.example.com), not the name of the resource record sets (www.example.com).
*
* In this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and you then associate the health check with those resource record
* sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value for
* IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
*
* If the value of Type is HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you want
* Amazon Route 53 to search for in the response body from the specified resource. If the string appears in the
* response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*
* The number of seconds between the time that Amazon Route 53 gets a response from your endpoint and the time that * it sends the next health check request. Each Route 53 health checker makes requests at this interval. *
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30 seconds.
*
* The number of consecutive health checks that an endpoint must pass or fail for Amazon Route 53 to change the * current status of the endpoint from unhealthy to healthy or vice versa. For more information, see How * Amazon Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*
* Specify whether you want Amazon Route 53 to measure the latency between health checkers in multiple Amazon Web * Services regions and your endpoint, and to display CloudWatch latency graphs on the Health Checks page in * the Route 53 console. *
*
* You can't change the value of MeasureLatency after you create a health check.
*
* Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider a * health check unhealthy when it otherwise would be considered healthy. *
*/ private Boolean inverted; /** ** Stops Route 53 from performing health checks. When you disable a health check, here's what happens: *
** Health checks that check the health of endpoints: Route 53 stops submitting requests to your application, * server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding CloudWatch * metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. If you * configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you want to stop * routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. *
*/ private Boolean disabled; /** *
* The number of child health checks that are associated with a CALCULATED health check that Amazon
* Route 53 must consider healthy for the CALCULATED health check to be considered healthy. To specify
* the child health checks that you want to associate with a CALCULATED health check, use the ChildHealthChecks element.
*
* Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this health * check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
* (CALCULATED Health Checks Only) A complex type that contains one ChildHealthCheck element for each
* health check that you want to associate with a CALCULATED health check.
*
* Specify whether you want Amazon Route 53 to send the value of FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to respond to
* HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the client_hello
* message. If you don't enable SNI, the status of the health check will be SSL alert handshake_failure
* . A health check can also have that status for other reasons. If SNI is enabled and you're still getting the
* error, check the SSL/TLS configuration on your endpoint and confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the endpoint
* responds to the client_hello message with a certificate that does not include the domain name that
* you specified in FullyQualifiedDomainName, a health checker will retry the handshake. In the second
* attempt, the health checker will omit FullyQualifiedDomainName from the client_hello
* message.
*
* A complex type that contains one Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
*
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions * that are listed under Valid Values. *
** If you update a health check to remove a region that has been performing health checks, Route 53 will briefly * continue to perform checks from that region to ensure that some health checkers are always checking the endpoint * (for example, if you replace three regions with four different regions). *
*/ private com.amazonaws.internal.SdkInternalList* A complex type that identifies the CloudWatch alarm that you want Amazon Route 53 health checkers to use to * determine whether the specified health check is healthy. *
*/ private AlarmIdentifier alarmIdentifier; /** ** When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want * Amazon Route 53 to assign to the health check: *
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. *
** For more information about Route 53 Application Recovery Controller, see Route 53 Application * Recovery Controller Developer Guide.. *
*/ private String routingControlArn; /** *
* The IPv4 or IPv6 IP address of the endpoint that you want Amazon Route 53 to perform health checks on. If you
* don't specify a value for IPAddress, Route 53 sends a DNS request to resolve the domain name that
* you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in RFC
* 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with your
* EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP address of
* your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create health * checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*
IPAddress, Route 53 sends a DNS request to resolve the domain
* name that you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in
* RFC 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with
* your EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP
* address of your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create * health checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address * Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*/
public void setIPAddress(String iPAddress) {
this.iPAddress = iPAddress;
}
/**
*
* The IPv4 or IPv6 IP address of the endpoint that you want Amazon Route 53 to perform health checks on. If you
* don't specify a value for IPAddress, Route 53 sends a DNS request to resolve the domain name that
* you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in RFC
* 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with your
* EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP address of
* your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create health * checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*
IPAddress, Route 53 sends a DNS request to resolve the domain
* name that you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in
* RFC 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with
* your EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the
* IP address of your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create * health checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address * Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*/
public String getIPAddress() {
return this.iPAddress;
}
/**
*
* The IPv4 or IPv6 IP address of the endpoint that you want Amazon Route 53 to perform health checks on. If you
* don't specify a value for IPAddress, Route 53 sends a DNS request to resolve the domain name that
* you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in RFC
* 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with your
* EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP address of
* your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create health * checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
*
IPAddress, Route 53 sends a DNS request to resolve the domain
* name that you specify in FullyQualifiedDomainName at the interval that you specify in
* RequestInterval. Using an IP address returned by DNS, Route 53 then checks the health of the
* endpoint.
*
* Use one of the following formats for the value of IPAddress:
*
* IPv4 address: four values between 0 and 255, separated by periods (.), for example,
* 192.0.2.44.
*
* IPv6 address: eight groups of four hexadecimal values, separated by colons (:), for example,
* 2001:0db8:85a3:0000:0000:abcd:0001:2345. You can also shorten IPv6 addresses as described in
* RFC 5952, for example, 2001:db8:85a3::abcd:1:2345.
*
* If the endpoint is an EC2 instance, we recommend that you create an Elastic IP address, associate it with
* your EC2 instance, and specify the Elastic IP address for IPAddress. This ensures that the IP
* address of your instance will never change.
*
* For more information, see FullyQualifiedDomainName. *
** Constraints: Route 53 can't check the health of endpoints for which the IP address is in local, private, * non-routable, or multicast ranges. For more information about IP addresses for which you can't create * health checks, see the following documents: *
** RFC 6598, IANA-Reserved IPv4 Prefix for Shared Address * Space *
*
* When the value of Type is CALCULATED or CLOUDWATCH_METRIC, omit
* IPAddress.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withIPAddress(String iPAddress) {
setIPAddress(iPAddress);
return this;
}
/**
*
* The port on the endpoint that you want Amazon Route 53 to perform health checks on. *
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* The port on the endpoint that you want Amazon Route 53 to perform health checks on. *
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* The port on the endpoint that you want Amazon Route 53 to perform health checks on. *
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* Don't specify a value for Port when you specify a value for Type of
* CLOUDWATCH_METRIC or CALCULATED.
*
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
* * @param type * The type of health check that you want to create, which indicates how Amazon Route 53 determines whether * an endpoint is healthy.
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request * and waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS * request and waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0
* or later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTP request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the
* alarm is OK, the health check is considered healthy. If the state is ALARM, the
* health check is considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the
* state is OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the
* number of health checks that Route 53 health checkers consider to be healthy and compares that number with
* the value of HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller
* routing control. If the routing control state is ON, the health check is considered healthy.
* If the state is OFF, the health check is considered unhealthy.
*
* For more information, see How Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. * @see HealthCheckType */ public void setType(String type) { this.type = type; } /** *
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
* * @return The type of health check that you want to create, which indicates how Amazon Route 53 determines whether * an endpoint is healthy.
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP * request and waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS * request and waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0
* or later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTP request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that
* you specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the
* alarm is OK, the health check is considered healthy. If the state is ALARM, the
* health check is considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the
* state is OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the
* number of health checks that Route 53 health checkers consider to be healthy and compares that number
* with the value of HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller
* routing control. If the routing control state is ON, the health check is considered healthy.
* If the state is OFF, the health check is considered unhealthy.
*
* For more information, see How Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer * Guide. * @see HealthCheckType */ public String getType() { return this.type; } /** *
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
* * @param type * The type of health check that you want to create, which indicates how Amazon Route 53 determines whether * an endpoint is healthy.
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request * and waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS * request and waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0
* or later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTP request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the
* alarm is OK, the health check is considered healthy. If the state is ALARM, the
* health check is considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the
* state is OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the
* number of health checks that Route 53 health checkers consider to be healthy and compares that number with
* the value of HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller
* routing control. If the routing control state is ON, the health check is considered healthy.
* If the state is OFF, the health check is considered unhealthy.
*
* For more information, see How Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. * @return Returns a reference to this object so that method calls can be chained together. * @see HealthCheckType */ public HealthCheckConfig withType(String type) { setType(type); return this; } /** *
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
* * @param type * The type of health check that you want to create, which indicates how Amazon Route 53 determines whether * an endpoint is healthy.
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request * and waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS * request and waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0
* or later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTP request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the
* alarm is OK, the health check is considered healthy. If the state is ALARM, the
* health check is considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the
* state is OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the
* number of health checks that Route 53 health checkers consider to be healthy and compares that number with
* the value of HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller
* routing control. If the routing control state is ON, the health check is considered healthy.
* If the state is OFF, the health check is considered unhealthy.
*
* For more information, see How Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. * @see HealthCheckType */ public void setType(HealthCheckType type) { withType(type); } /** *
* The type of health check that you want to create, which indicates how Amazon Route 53 determines whether an * endpoint is healthy. *
*
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request and * waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS request and * waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0 or
* later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP
* request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the alarm is
* OK, the health check is considered healthy. If the state is ALARM, the health check is
* considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the state is
* OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the number
* of health checks that Route 53 health checkers consider to be healthy and compares that number with the value of
* HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller routing
* control. If the routing control state is ON, the health check is considered healthy. If the state is
* OFF, the health check is considered unhealthy.
*
* For more information, see How * Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
* * @param type * The type of health check that you want to create, which indicates how Amazon Route 53 determines whether * an endpoint is healthy.
* You can't change the value of Type after you create a health check.
*
* You can create the following types of health checks: *
** HTTP: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTP request * and waits for an HTTP status code of 200 or greater and less than 400. *
** HTTPS: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an HTTPS * request and waits for an HTTP status code of 200 or greater and less than 400. *
*
* If you specify HTTPS for the value of Type, the endpoint must support TLS v1.0
* or later.
*
* HTTP_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTP request and searches the first 5,120 bytes of the response body for the string that you specify in
* SearchString.
*
* HTTPS_STR_MATCH: Route 53 tries to establish a TCP connection. If successful, Route 53 submits an
* HTTPS request and searches the first 5,120 bytes of the response body for the string that you
* specify in SearchString.
*
* TCP: Route 53 tries to establish a TCP connection. *
*
* CLOUDWATCH_METRIC: The health check is associated with a CloudWatch alarm. If the state of the
* alarm is OK, the health check is considered healthy. If the state is ALARM, the
* health check is considered unhealthy. If CloudWatch doesn't have sufficient data to determine whether the
* state is OK or ALARM, the health check status depends on the setting for
* InsufficientDataHealthStatus: Healthy, Unhealthy, or
* LastKnownStatus.
*
* CALCULATED: For health checks that monitor the status of other health checks, Route 53 adds up the
* number of health checks that Route 53 health checkers consider to be healthy and compares that number with
* the value of HealthThreshold.
*
* RECOVERY_CONTROL: The health check is assocated with a Route53 Application Recovery Controller
* routing control. If the routing control state is ON, the health check is considered healthy.
* If the state is OFF, the health check is considered unhealthy.
*
* For more information, see How Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. * @return Returns a reference to this object so that method calls can be chained together. * @see HealthCheckType */ public HealthCheckConfig withType(HealthCheckType type) { this.type = type.toString(); return this; } /** *
* The path, if any, that you want Amazon Route 53 to request when performing health checks. The path can be any
* value for which your endpoint will return an HTTP status code of 2xx or 3xx when the endpoint is healthy, for
* example, the file /docs/route53-health-check.html. You can also include query string parameters, for example,
* /welcome.html?language=jp&login=y.
*
/welcome.html?language=jp&login=y.
*/
public void setResourcePath(String resourcePath) {
this.resourcePath = resourcePath;
}
/**
*
* The path, if any, that you want Amazon Route 53 to request when performing health checks. The path can be any
* value for which your endpoint will return an HTTP status code of 2xx or 3xx when the endpoint is healthy, for
* example, the file /docs/route53-health-check.html. You can also include query string parameters, for example,
* /welcome.html?language=jp&login=y.
*
/welcome.html?language=jp&login=y.
*/
public String getResourcePath() {
return this.resourcePath;
}
/**
*
* The path, if any, that you want Amazon Route 53 to request when performing health checks. The path can be any
* value for which your endpoint will return an HTTP status code of 2xx or 3xx when the endpoint is healthy, for
* example, the file /docs/route53-health-check.html. You can also include query string parameters, for example,
* /welcome.html?language=jp&login=y.
*
/welcome.html?language=jp&login=y.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withResourcePath(String resourcePath) {
setResourcePath(resourcePath);
return this;
}
/**
*
* Amazon Route 53 behavior depends on whether you specify a value for IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP health
* checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53 to perform
* health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for Type,
* Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at the
* interval that you specify for RequestInterval. Using an IPv4 address that DNS returns, Route 53 then
* checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to the
* endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to specify
* the endpoint only by FullyQualifiedDomainName, we recommend that you create a separate health check
* for each endpoint. For example, create a health check for each HTTP server that is serving content for
* www.example.com. For the value of FullyQualifiedDomainName, specify the domain name of the server
* (such as us-east-2-www.example.com), not the name of the resource record sets (www.example.com).
*
* In this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and you then associate the health check with those resource record
* sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value for
* IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
*
IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP
* health checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53
* to perform health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for
* Type, Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the
* Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at
* the interval that you specify for RequestInterval. Using an IPv4 address that DNS returns,
* Route 53 then checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to
* the endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to
* specify the endpoint only by FullyQualifiedDomainName, we recommend that you create a
* separate health check for each endpoint. For example, create a health check for each HTTP server that is
* serving content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-2-www.example.com), not the name of the resource record sets
* (www.example.com).
*
* In this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and you then associate
* the health check with those resource record sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value
* for IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
*/
public void setFullyQualifiedDomainName(String fullyQualifiedDomainName) {
this.fullyQualifiedDomainName = fullyQualifiedDomainName;
}
/**
*
* Amazon Route 53 behavior depends on whether you specify a value for IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP health
* checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53 to perform
* health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for Type,
* Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at the
* interval that you specify for RequestInterval. Using an IPv4 address that DNS returns, Route 53 then
* checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to the
* endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to specify
* the endpoint only by FullyQualifiedDomainName, we recommend that you create a separate health check
* for each endpoint. For example, create a health check for each HTTP server that is serving content for
* www.example.com. For the value of FullyQualifiedDomainName, specify the domain name of the server
* (such as us-east-2-www.example.com), not the name of the resource record sets (www.example.com).
*
* In this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and you then associate the health check with those resource record
* sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value for
* IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
*
IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP
* health checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53
* to perform health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for
* Type, Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the
* Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at
* the interval that you specify for RequestInterval. Using an IPv4 address that DNS returns,
* Route 53 then checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to
* the endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to
* specify the endpoint only by FullyQualifiedDomainName, we recommend that you create a
* separate health check for each endpoint. For example, create a health check for each HTTP server that is
* serving content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-2-www.example.com), not the name of the resource record sets
* (www.example.com).
*
* In this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and you then associate
* the health check with those resource record sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS, HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a
* value for IPAddress. If the value of Type is TCP, Route 53 doesn't
* pass a Host header.
*/
public String getFullyQualifiedDomainName() {
return this.fullyQualifiedDomainName;
}
/**
*
* Amazon Route 53 behavior depends on whether you specify a value for IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP health
* checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53 to perform
* health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for Type,
* Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at the
* interval that you specify for RequestInterval. Using an IPv4 address that DNS returns, Route 53 then
* checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to the
* endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to specify
* the endpoint only by FullyQualifiedDomainName, we recommend that you create a separate health check
* for each endpoint. For example, create a health check for each HTTP server that is serving content for
* www.example.com. For the value of FullyQualifiedDomainName, specify the domain name of the server
* (such as us-east-2-www.example.com), not the name of the resource record sets (www.example.com).
*
* In this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and you then associate the health check with those resource record
* sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value for
* IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
*
IPAddress.
*
* If you specify a value for IPAddress:
*
* Amazon Route 53 sends health check requests to the specified IPv4 or IPv6 address and passes the value of
* FullyQualifiedDomainName in the Host header for all health checks except TCP
* health checks. This is typically the fully qualified DNS name of the endpoint on which you want Route 53
* to perform health checks.
*
* When Route 53 checks the health of an endpoint, here is how it constructs the Host header:
*
* If you specify a value of 80 for Port and HTTP or
* HTTP_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify a value of 443 for Port and HTTPS or
* HTTPS_STR_MATCH for Type, Route 53 passes the value of
* FullyQualifiedDomainName to the endpoint in the Host header.
*
* If you specify another value for Port and any value except TCP for
* Type, Route 53 passes FullyQualifiedDomainName:Port to the endpoint in the
* Host header.
*
* If you don't specify a value for FullyQualifiedDomainName, Route 53 substitutes the value of
* IPAddress in the Host header in each of the preceding cases.
*
* If you don't specify a value for IPAddress:
*
* Route 53 sends a DNS request to the domain that you specify for FullyQualifiedDomainName at
* the interval that you specify for RequestInterval. Using an IPv4 address that DNS returns,
* Route 53 then checks the health of the endpoint.
*
* If you don't specify a value for IPAddress, Route 53 uses only IPv4 to send health checks to
* the endpoint. If there's no resource record set with a type of A for the name that you specify for
* FullyQualifiedDomainName, the health check fails with a "DNS resolution failed" error.
*
* If you want to check the health of weighted, latency, or failover resource record sets and you choose to
* specify the endpoint only by FullyQualifiedDomainName, we recommend that you create a
* separate health check for each endpoint. For example, create a health check for each HTTP server that is
* serving content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-2-www.example.com), not the name of the resource record sets
* (www.example.com).
*
* In this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and you then associate
* the health check with those resource record sets, health check results will be unpredictable.
*
* In addition, if the value that you specify for Type is HTTP, HTTPS,
* HTTP_STR_MATCH, or HTTPS_STR_MATCH, Route 53 passes the value of
* FullyQualifiedDomainName in the Host header, as it does when you specify a value
* for IPAddress. If the value of Type is TCP, Route 53 doesn't pass a
* Host header.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withFullyQualifiedDomainName(String fullyQualifiedDomainName) {
setFullyQualifiedDomainName(fullyQualifiedDomainName);
return this;
}
/**
*
* If the value of Type is HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you want
* Amazon Route 53 to search for in the response body from the specified resource. If the string appears in the
* response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*
HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you
* want Amazon Route 53 to search for in the response body from the specified resource. If the string appears
* in the response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*/
public void setSearchString(String searchString) {
this.searchString = searchString;
}
/**
*
* If the value of Type is HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you want
* Amazon Route 53 to search for in the response body from the specified resource. If the string appears in the
* response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*
HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you
* want Amazon Route 53 to search for in the response body from the specified resource. If the string
* appears in the response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*/
public String getSearchString() {
return this.searchString;
}
/**
*
* If the value of Type is HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you want
* Amazon Route 53 to search for in the response body from the specified resource. If the string appears in the
* response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
*
HTTP_STR_MATCH or HTTPS_STR_MATCH, the string that you
* want Amazon Route 53 to search for in the response body from the specified resource. If the string appears
* in the response body, Route 53 considers the resource healthy.
*
* Route 53 considers case when searching for SearchString in the response body.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withSearchString(String searchString) {
setSearchString(searchString);
return this;
}
/**
*
* The number of seconds between the time that Amazon Route 53 gets a response from your endpoint and the time that * it sends the next health check request. Each Route 53 health checker makes requests at this interval. *
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30 seconds.
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30
* seconds.
*/
public void setRequestInterval(Integer requestInterval) {
this.requestInterval = requestInterval;
}
/**
*
* The number of seconds between the time that Amazon Route 53 gets a response from your endpoint and the time that * it sends the next health check request. Each Route 53 health checker makes requests at this interval. *
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30 seconds.
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30
* seconds.
*/
public Integer getRequestInterval() {
return this.requestInterval;
}
/**
*
* The number of seconds between the time that Amazon Route 53 gets a response from your endpoint and the time that * it sends the next health check request. Each Route 53 health checker makes requests at this interval. *
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30 seconds.
*
* You can't change the value of RequestInterval after you create a health check.
*
* If you don't specify a value for RequestInterval, the default value is 30
* seconds.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withRequestInterval(Integer requestInterval) {
setRequestInterval(requestInterval);
return this;
}
/**
*
* The number of consecutive health checks that an endpoint must pass or fail for Amazon Route 53 to change the * current status of the endpoint from unhealthy to healthy or vice versa. For more information, see How * Amazon Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*/
public void setFailureThreshold(Integer failureThreshold) {
this.failureThreshold = failureThreshold;
}
/**
*
* The number of consecutive health checks that an endpoint must pass or fail for Amazon Route 53 to change the * current status of the endpoint from unhealthy to healthy or vice versa. For more information, see How * Amazon Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*/
public Integer getFailureThreshold() {
return this.failureThreshold;
}
/**
*
* The number of consecutive health checks that an endpoint must pass or fail for Amazon Route 53 to change the * current status of the endpoint from unhealthy to healthy or vice versa. For more information, see How * Amazon Route 53 Determines Whether an Endpoint Is Healthy in the Amazon Route 53 Developer Guide. *
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
*
* If you don't specify a value for FailureThreshold, the default value is three health checks.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withFailureThreshold(Integer failureThreshold) {
setFailureThreshold(failureThreshold);
return this;
}
/**
*
* Specify whether you want Amazon Route 53 to measure the latency between health checkers in multiple Amazon Web * Services regions and your endpoint, and to display CloudWatch latency graphs on the Health Checks page in * the Route 53 console. *
*
* You can't change the value of MeasureLatency after you create a health check.
*
* You can't change the value of MeasureLatency after you create a health check.
*
* Specify whether you want Amazon Route 53 to measure the latency between health checkers in multiple Amazon Web * Services regions and your endpoint, and to display CloudWatch latency graphs on the Health Checks page in * the Route 53 console. *
*
* You can't change the value of MeasureLatency after you create a health check.
*
* You can't change the value of MeasureLatency after you create a health check.
*
* Specify whether you want Amazon Route 53 to measure the latency between health checkers in multiple Amazon Web * Services regions and your endpoint, and to display CloudWatch latency graphs on the Health Checks page in * the Route 53 console. *
*
* You can't change the value of MeasureLatency after you create a health check.
*
* You can't change the value of MeasureLatency after you create a health check.
*
* Specify whether you want Amazon Route 53 to measure the latency between health checkers in multiple Amazon Web * Services regions and your endpoint, and to display CloudWatch latency graphs on the Health Checks page in * the Route 53 console. *
*
* You can't change the value of MeasureLatency after you create a health check.
*
* You can't change the value of MeasureLatency after you create a health check.
*
* Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider a * health check unhealthy when it otherwise would be considered healthy. *
* * @param inverted * Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider * a health check unhealthy when it otherwise would be considered healthy. */ public void setInverted(Boolean inverted) { this.inverted = inverted; } /** ** Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider a * health check unhealthy when it otherwise would be considered healthy. *
* * @return Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider * a health check unhealthy when it otherwise would be considered healthy. */ public Boolean getInverted() { return this.inverted; } /** ** Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider a * health check unhealthy when it otherwise would be considered healthy. *
* * @param inverted * Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider * a health check unhealthy when it otherwise would be considered healthy. * @return Returns a reference to this object so that method calls can be chained together. */ public HealthCheckConfig withInverted(Boolean inverted) { setInverted(inverted); return this; } /** ** Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider a * health check unhealthy when it otherwise would be considered healthy. *
* * @return Specify whether you want Amazon Route 53 to invert the status of a health check, for example, to consider * a health check unhealthy when it otherwise would be considered healthy. */ public Boolean isInverted() { return this.inverted; } /** ** Stops Route 53 from performing health checks. When you disable a health check, here's what happens: *
** Health checks that check the health of endpoints: Route 53 stops submitting requests to your application, * server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding CloudWatch * metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. If you * configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you want to stop * routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. *
* * @param disabled * Stops Route 53 from performing health checks. When you disable a health check, here's what happens: ** Health checks that check the health of endpoints: Route 53 stops submitting requests to your * application, server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding * CloudWatch metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. * If you configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you * want to stop routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. */ public void setDisabled(Boolean disabled) { this.disabled = disabled; } /** *
* Stops Route 53 from performing health checks. When you disable a health check, here's what happens: *
** Health checks that check the health of endpoints: Route 53 stops submitting requests to your application, * server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding CloudWatch * metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. If you * configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you want to stop * routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. *
* * @return Stops Route 53 from performing health checks. When you disable a health check, here's what happens: ** Health checks that check the health of endpoints: Route 53 stops submitting requests to your * application, server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding * CloudWatch metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. * If you configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If * you want to stop routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. */ public Boolean getDisabled() { return this.disabled; } /** *
* Stops Route 53 from performing health checks. When you disable a health check, here's what happens: *
** Health checks that check the health of endpoints: Route 53 stops submitting requests to your application, * server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding CloudWatch * metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. If you * configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you want to stop * routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. *
* * @param disabled * Stops Route 53 from performing health checks. When you disable a health check, here's what happens: ** Health checks that check the health of endpoints: Route 53 stops submitting requests to your * application, server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding * CloudWatch metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. * If you configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you * want to stop routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. * @return Returns a reference to this object so that method calls can be chained together. */ public HealthCheckConfig withDisabled(Boolean disabled) { setDisabled(disabled); return this; } /** *
* Stops Route 53 from performing health checks. When you disable a health check, here's what happens: *
** Health checks that check the health of endpoints: Route 53 stops submitting requests to your application, * server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding CloudWatch * metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. If you * configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If you want to stop * routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. *
* * @return Stops Route 53 from performing health checks. When you disable a health check, here's what happens: ** Health checks that check the health of endpoints: Route 53 stops submitting requests to your * application, server, or other resource. *
** Calculated health checks: Route 53 stops aggregating the status of the referenced health checks. *
** Health checks that monitor CloudWatch alarms: Route 53 stops monitoring the corresponding * CloudWatch metrics. *
** After you disable a health check, Route 53 considers the status of the health check to always be healthy. * If you configured DNS failover, Route 53 continues to route traffic to the corresponding resources. If * you want to stop routing traffic to a resource, change the value of Inverted. *
** Charges for a health check still apply when the health check is disabled. For more information, see Amazon Route 53 Pricing. */ public Boolean isDisabled() { return this.disabled; } /** *
* The number of child health checks that are associated with a CALCULATED health check that Amazon
* Route 53 must consider healthy for the CALCULATED health check to be considered healthy. To specify
* the child health checks that you want to associate with a CALCULATED health check, use the ChildHealthChecks element.
*
* Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this health * check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
CALCULATED health check that
* Amazon Route 53 must consider healthy for the CALCULATED health check to be considered
* healthy. To specify the child health checks that you want to associate with a CALCULATED
* health check, use the ChildHealthChecks element.
* * Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this * health check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
* The number of child health checks that are associated with a CALCULATED health check that Amazon
* Route 53 must consider healthy for the CALCULATED health check to be considered healthy. To specify
* the child health checks that you want to associate with a CALCULATED health check, use the ChildHealthChecks element.
*
* Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this health * check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
CALCULATED health check that
* Amazon Route 53 must consider healthy for the CALCULATED health check to be considered
* healthy. To specify the child health checks that you want to associate with a CALCULATED
* health check, use the ChildHealthChecks element.
* * Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this * health check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
* The number of child health checks that are associated with a CALCULATED health check that Amazon
* Route 53 must consider healthy for the CALCULATED health check to be considered healthy. To specify
* the child health checks that you want to associate with a CALCULATED health check, use the ChildHealthChecks element.
*
* Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this health * check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
CALCULATED health check that
* Amazon Route 53 must consider healthy for the CALCULATED health check to be considered
* healthy. To specify the child health checks that you want to associate with a CALCULATED
* health check, use the ChildHealthChecks element.
* * Note the following: *
** If you specify a number greater than the number of child health checks, Route 53 always considers this * health check to be unhealthy. *
*
* If you specify 0, Route 53 always considers this health check to be healthy.
*
* (CALCULATED Health Checks Only) A complex type that contains one ChildHealthCheck element for each
* health check that you want to associate with a CALCULATED health check.
*
ChildHealthCheck element
* for each health check that you want to associate with a CALCULATED health check.
*/
public java.util.List
* (CALCULATED Health Checks Only) A complex type that contains one ChildHealthCheck element for each
* health check that you want to associate with a CALCULATED health check.
*
ChildHealthCheck element for
* each health check that you want to associate with a CALCULATED health check.
*/
public void setChildHealthChecks(java.util.Collection
* (CALCULATED Health Checks Only) A complex type that contains one ChildHealthCheck element for each
* health check that you want to associate with a CALCULATED health check.
*
* NOTE: This method appends the values to the existing list (if any). Use * {@link #setChildHealthChecks(java.util.Collection)} or {@link #withChildHealthChecks(java.util.Collection)} if * you want to override the existing values. *
* * @param childHealthChecks * (CALCULATED Health Checks Only) A complex type that contains oneChildHealthCheck element for
* each health check that you want to associate with a CALCULATED health check.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withChildHealthChecks(String... childHealthChecks) {
if (this.childHealthChecks == null) {
setChildHealthChecks(new com.amazonaws.internal.SdkInternalList
* (CALCULATED Health Checks Only) A complex type that contains one ChildHealthCheck element for each
* health check that you want to associate with a CALCULATED health check.
*
ChildHealthCheck element for
* each health check that you want to associate with a CALCULATED health check.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withChildHealthChecks(java.util.Collection
* Specify whether you want Amazon Route 53 to send the value of FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to respond to
* HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the client_hello
* message. If you don't enable SNI, the status of the health check will be SSL alert handshake_failure
* . A health check can also have that status for other reasons. If SNI is enabled and you're still getting the
* error, check the SSL/TLS configuration on your endpoint and confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the endpoint
* responds to the client_hello message with a certificate that does not include the domain name that
* you specified in FullyQualifiedDomainName, a health checker will retry the handshake. In the second
* attempt, the health checker will omit FullyQualifiedDomainName from the client_hello
* message.
*
FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to
* respond to HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the
* client_hello message. If you don't enable SNI, the status of the health check will be
* SSL alert handshake_failure. A health check can also have that status for other reasons. If
* SNI is enabled and you're still getting the error, check the SSL/TLS configuration on your endpoint and
* confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the
* endpoint responds to the client_hello message with a certificate that does not include the
* domain name that you specified in FullyQualifiedDomainName, a health checker will retry the
* handshake. In the second attempt, the health checker will omit FullyQualifiedDomainName from
* the client_hello message.
*/
public void setEnableSNI(Boolean enableSNI) {
this.enableSNI = enableSNI;
}
/**
*
* Specify whether you want Amazon Route 53 to send the value of FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to respond to
* HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the client_hello
* message. If you don't enable SNI, the status of the health check will be SSL alert handshake_failure
* . A health check can also have that status for other reasons. If SNI is enabled and you're still getting the
* error, check the SSL/TLS configuration on your endpoint and confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the endpoint
* responds to the client_hello message with a certificate that does not include the domain name that
* you specified in FullyQualifiedDomainName, a health checker will retry the handshake. In the second
* attempt, the health checker will omit FullyQualifiedDomainName from the client_hello
* message.
*
FullyQualifiedDomainName to
* the endpoint in the client_hello message during TLS negotiation. This allows the endpoint to
* respond to HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the
* client_hello message. If you don't enable SNI, the status of the health check will be
* SSL alert handshake_failure. A health check can also have that status for other reasons. If
* SNI is enabled and you're still getting the error, check the SSL/TLS configuration on your endpoint and
* confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the
* endpoint responds to the client_hello message with a certificate that does not include the
* domain name that you specified in FullyQualifiedDomainName, a health checker will retry the
* handshake. In the second attempt, the health checker will omit FullyQualifiedDomainName from
* the client_hello message.
*/
public Boolean getEnableSNI() {
return this.enableSNI;
}
/**
*
* Specify whether you want Amazon Route 53 to send the value of FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to respond to
* HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the client_hello
* message. If you don't enable SNI, the status of the health check will be SSL alert handshake_failure
* . A health check can also have that status for other reasons. If SNI is enabled and you're still getting the
* error, check the SSL/TLS configuration on your endpoint and confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the endpoint
* responds to the client_hello message with a certificate that does not include the domain name that
* you specified in FullyQualifiedDomainName, a health checker will retry the handshake. In the second
* attempt, the health checker will omit FullyQualifiedDomainName from the client_hello
* message.
*
FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to
* respond to HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the
* client_hello message. If you don't enable SNI, the status of the health check will be
* SSL alert handshake_failure. A health check can also have that status for other reasons. If
* SNI is enabled and you're still getting the error, check the SSL/TLS configuration on your endpoint and
* confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the
* endpoint responds to the client_hello message with a certificate that does not include the
* domain name that you specified in FullyQualifiedDomainName, a health checker will retry the
* handshake. In the second attempt, the health checker will omit FullyQualifiedDomainName from
* the client_hello message.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public HealthCheckConfig withEnableSNI(Boolean enableSNI) {
setEnableSNI(enableSNI);
return this;
}
/**
*
* Specify whether you want Amazon Route 53 to send the value of FullyQualifiedDomainName to the
* endpoint in the client_hello message during TLS negotiation. This allows the endpoint to respond to
* HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the client_hello
* message. If you don't enable SNI, the status of the health check will be SSL alert handshake_failure
* . A health check can also have that status for other reasons. If SNI is enabled and you're still getting the
* error, check the SSL/TLS configuration on your endpoint and confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the endpoint
* responds to the client_hello message with a certificate that does not include the domain name that
* you specified in FullyQualifiedDomainName, a health checker will retry the handshake. In the second
* attempt, the health checker will omit FullyQualifiedDomainName from the client_hello
* message.
*
FullyQualifiedDomainName to
* the endpoint in the client_hello message during TLS negotiation. This allows the endpoint to
* respond to HTTPS health check requests with the applicable SSL/TLS certificate.
*
* Some endpoints require that HTTPS requests include the host name in the
* client_hello message. If you don't enable SNI, the status of the health check will be
* SSL alert handshake_failure. A health check can also have that status for other reasons. If
* SNI is enabled and you're still getting the error, check the SSL/TLS configuration on your endpoint and
* confirm that your certificate is valid.
*
* The SSL/TLS certificate on your endpoint includes a domain name in the Common Name field and
* possibly several more in the Subject Alternative Names field. One of the domain names in the
* certificate should match the value that you specify for FullyQualifiedDomainName. If the
* endpoint responds to the client_hello message with a certificate that does not include the
* domain name that you specified in FullyQualifiedDomainName, a health checker will retry the
* handshake. In the second attempt, the health checker will omit FullyQualifiedDomainName from
* the client_hello message.
*/
public Boolean isEnableSNI() {
return this.enableSNI;
}
/**
*
* A complex type that contains one Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
*
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions * that are listed under Valid Values. *
** If you update a health check to remove a region that has been performing health checks, Route 53 will briefly * continue to perform checks from that region to ensure that some health checkers are always checking the endpoint * (for example, if you replace three regions with four different regions). *
* * @return A complex type that contains oneRegion element for each region from which you want Amazon
* Route 53 health checkers to check the specified endpoint.
* * If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the * regions that are listed under Valid Values. *
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will
* briefly continue to perform checks from that region to ensure that some health checkers are always
* checking the endpoint (for example, if you replace three regions with four different regions).
* @see HealthCheckRegion
*/
public java.util.List
* A complex type that contains one
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions
* that are listed under Valid Values.
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will briefly
* continue to perform checks from that region to ensure that some health checkers are always checking the endpoint
* (for example, if you replace three regions with four different regions).
* Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
* Region element for each region from which you want Amazon
* Route 53 health checkers to check the specified endpoint.
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the * regions that are listed under Valid Values. *
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will
* briefly continue to perform checks from that region to ensure that some health checkers are always
* checking the endpoint (for example, if you replace three regions with four different regions).
* @see HealthCheckRegion
*/
public void setRegions(java.util.Collection
* A complex type that contains one
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions
* that are listed under Valid Values.
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will briefly
* continue to perform checks from that region to ensure that some health checkers are always checking the endpoint
* (for example, if you replace three regions with four different regions).
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setRegions(java.util.Collection)} or {@link #withRegions(java.util.Collection)} if you want to override
* the existing values.
* Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
* Region element for each region from which you want Amazon
* Route 53 health checkers to check the specified endpoint.
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the * regions that are listed under Valid Values. *
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will
* briefly continue to perform checks from that region to ensure that some health checkers are always
* checking the endpoint (for example, if you replace three regions with four different regions).
* @return Returns a reference to this object so that method calls can be chained together.
* @see HealthCheckRegion
*/
public HealthCheckConfig withRegions(String... regions) {
if (this.regions == null) {
setRegions(new com.amazonaws.internal.SdkInternalList
* A complex type that contains one
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions
* that are listed under Valid Values.
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will briefly
* continue to perform checks from that region to ensure that some health checkers are always checking the endpoint
* (for example, if you replace three regions with four different regions).
* Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
* Region element for each region from which you want Amazon
* Route 53 health checkers to check the specified endpoint.
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the * regions that are listed under Valid Values. *
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will
* briefly continue to perform checks from that region to ensure that some health checkers are always
* checking the endpoint (for example, if you replace three regions with four different regions).
* @return Returns a reference to this object so that method calls can be chained together.
* @see HealthCheckRegion
*/
public HealthCheckConfig withRegions(java.util.Collection
* A complex type that contains one
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the regions
* that are listed under Valid Values.
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will briefly
* continue to perform checks from that region to ensure that some health checkers are always checking the endpoint
* (for example, if you replace three regions with four different regions).
* Region element for each region from which you want Amazon Route 53
* health checkers to check the specified endpoint.
* Region element for each region from which you want Amazon
* Route 53 health checkers to check the specified endpoint.
* If you don't specify any regions, Route 53 health checkers automatically performs checks from all of the * regions that are listed under Valid Values. *
*
* If you update a health check to remove a region that has been performing health checks, Route 53 will
* briefly continue to perform checks from that region to ensure that some health checkers are always
* checking the endpoint (for example, if you replace three regions with four different regions).
* @return Returns a reference to this object so that method calls can be chained together.
* @see HealthCheckRegion
*/
public HealthCheckConfig withRegions(HealthCheckRegion... regions) {
com.amazonaws.internal.SdkInternalList
* A complex type that identifies the CloudWatch alarm that you want Amazon Route 53 health checkers to use to
* determine whether the specified health check is healthy.
*
* A complex type that identifies the CloudWatch alarm that you want Amazon Route 53 health checkers to use to
* determine whether the specified health check is healthy.
*
* A complex type that identifies the CloudWatch alarm that you want Amazon Route 53 health checkers to use to
* determine whether the specified health check is healthy.
*
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want
* Amazon Route 53 to assign to the health check:
*
*
*
*
*
*
* @param insufficientDataHealthStatus
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you
* want Amazon Route 53 to assign to the health check:Healthy: Route 53 considers the health check to be healthy.
* Unhealthy: Route 53 considers the health check to be unhealthy.
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that
* CloudWatch had sufficient data to determine the alarm state. For new health checks that have no last known
* status, the default status for the health check is healthy.
*
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want * Amazon Route 53 to assign to the health check: *
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that
* CloudWatch had sufficient data to determine the alarm state. For new health checks that have no last
* known status, the default status for the health check is healthy.
*
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want * Amazon Route 53 to assign to the health check: *
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that
* CloudWatch had sufficient data to determine the alarm state. For new health checks that have no last known
* status, the default status for the health check is healthy.
*
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want * Amazon Route 53 to assign to the health check: *
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that
* CloudWatch had sufficient data to determine the alarm state. For new health checks that have no last known
* status, the default status for the health check is healthy.
*
* When CloudWatch has insufficient data about the metric to determine the alarm state, the status that you want * Amazon Route 53 to assign to the health check: *
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that CloudWatch had
* sufficient data to determine the alarm state. For new health checks that have no last known status, the default
* status for the health check is healthy.
*
* Healthy: Route 53 considers the health check to be healthy.
*
* Unhealthy: Route 53 considers the health check to be unhealthy.
*
* LastKnownStatus: Route 53 uses the status of the health check from the last time that
* CloudWatch had sufficient data to determine the alarm state. For new health checks that have no last known
* status, the default status for the health check is healthy.
*
* The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. *
** For more information about Route 53 Application Recovery Controller, see Route 53 Application * Recovery Controller Developer Guide.. *
* * @param routingControlArn * The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. ** For more information about Route 53 Application Recovery Controller, see Route 53 * Application Recovery Controller Developer Guide.. */ public void setRoutingControlArn(String routingControlArn) { this.routingControlArn = routingControlArn; } /** *
* The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. *
** For more information about Route 53 Application Recovery Controller, see Route 53 Application * Recovery Controller Developer Guide.. *
* * @return The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. ** For more information about Route 53 Application Recovery Controller, see Route 53 * Application Recovery Controller Developer Guide.. */ public String getRoutingControlArn() { return this.routingControlArn; } /** *
* The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. *
** For more information about Route 53 Application Recovery Controller, see Route 53 Application * Recovery Controller Developer Guide.. *
* * @param routingControlArn * The Amazon Resource Name (ARN) for the Route 53 Application Recovery Controller routing control. ** For more information about Route 53 Application Recovery Controller, see Route 53 * Application Recovery Controller Developer Guide.. * @return Returns a reference to this object so that method calls can be chained together. */ public HealthCheckConfig withRoutingControlArn(String routingControlArn) { setRoutingControlArn(routingControlArn); return this; } /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. * * @return A string representation of this object. * * @see java.lang.Object#toString() */ @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("{"); if (getIPAddress() != null) sb.append("IPAddress: ").append(getIPAddress()).append(","); if (getPort() != null) sb.append("Port: ").append(getPort()).append(","); if (getType() != null) sb.append("Type: ").append(getType()).append(","); if (getResourcePath() != null) sb.append("ResourcePath: ").append(getResourcePath()).append(","); if (getFullyQualifiedDomainName() != null) sb.append("FullyQualifiedDomainName: ").append(getFullyQualifiedDomainName()).append(","); if (getSearchString() != null) sb.append("SearchString: ").append(getSearchString()).append(","); if (getRequestInterval() != null) sb.append("RequestInterval: ").append(getRequestInterval()).append(","); if (getFailureThreshold() != null) sb.append("FailureThreshold: ").append(getFailureThreshold()).append(","); if (getMeasureLatency() != null) sb.append("MeasureLatency: ").append(getMeasureLatency()).append(","); if (getInverted() != null) sb.append("Inverted: ").append(getInverted()).append(","); if (getDisabled() != null) sb.append("Disabled: ").append(getDisabled()).append(","); if (getHealthThreshold() != null) sb.append("HealthThreshold: ").append(getHealthThreshold()).append(","); if (getChildHealthChecks() != null) sb.append("ChildHealthChecks: ").append(getChildHealthChecks()).append(","); if (getEnableSNI() != null) sb.append("EnableSNI: ").append(getEnableSNI()).append(","); if (getRegions() != null) sb.append("Regions: ").append(getRegions()).append(","); if (getAlarmIdentifier() != null) sb.append("AlarmIdentifier: ").append(getAlarmIdentifier()).append(","); if (getInsufficientDataHealthStatus() != null) sb.append("InsufficientDataHealthStatus: ").append(getInsufficientDataHealthStatus()).append(","); if (getRoutingControlArn() != null) sb.append("RoutingControlArn: ").append(getRoutingControlArn()); sb.append("}"); return sb.toString(); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (obj instanceof HealthCheckConfig == false) return false; HealthCheckConfig other = (HealthCheckConfig) obj; if (other.getIPAddress() == null ^ this.getIPAddress() == null) return false; if (other.getIPAddress() != null && other.getIPAddress().equals(this.getIPAddress()) == false) return false; if (other.getPort() == null ^ this.getPort() == null) return false; if (other.getPort() != null && other.getPort().equals(this.getPort()) == false) return false; if (other.getType() == null ^ this.getType() == null) return false; if (other.getType() != null && other.getType().equals(this.getType()) == false) return false; if (other.getResourcePath() == null ^ this.getResourcePath() == null) return false; if (other.getResourcePath() != null && other.getResourcePath().equals(this.getResourcePath()) == false) return false; if (other.getFullyQualifiedDomainName() == null ^ this.getFullyQualifiedDomainName() == null) return false; if (other.getFullyQualifiedDomainName() != null && other.getFullyQualifiedDomainName().equals(this.getFullyQualifiedDomainName()) == false) return false; if (other.getSearchString() == null ^ this.getSearchString() == null) return false; if (other.getSearchString() != null && other.getSearchString().equals(this.getSearchString()) == false) return false; if (other.getRequestInterval() == null ^ this.getRequestInterval() == null) return false; if (other.getRequestInterval() != null && other.getRequestInterval().equals(this.getRequestInterval()) == false) return false; if (other.getFailureThreshold() == null ^ this.getFailureThreshold() == null) return false; if (other.getFailureThreshold() != null && other.getFailureThreshold().equals(this.getFailureThreshold()) == false) return false; if (other.getMeasureLatency() == null ^ this.getMeasureLatency() == null) return false; if (other.getMeasureLatency() != null && other.getMeasureLatency().equals(this.getMeasureLatency()) == false) return false; if (other.getInverted() == null ^ this.getInverted() == null) return false; if (other.getInverted() != null && other.getInverted().equals(this.getInverted()) == false) return false; if (other.getDisabled() == null ^ this.getDisabled() == null) return false; if (other.getDisabled() != null && other.getDisabled().equals(this.getDisabled()) == false) return false; if (other.getHealthThreshold() == null ^ this.getHealthThreshold() == null) return false; if (other.getHealthThreshold() != null && other.getHealthThreshold().equals(this.getHealthThreshold()) == false) return false; if (other.getChildHealthChecks() == null ^ this.getChildHealthChecks() == null) return false; if (other.getChildHealthChecks() != null && other.getChildHealthChecks().equals(this.getChildHealthChecks()) == false) return false; if (other.getEnableSNI() == null ^ this.getEnableSNI() == null) return false; if (other.getEnableSNI() != null && other.getEnableSNI().equals(this.getEnableSNI()) == false) return false; if (other.getRegions() == null ^ this.getRegions() == null) return false; if (other.getRegions() != null && other.getRegions().equals(this.getRegions()) == false) return false; if (other.getAlarmIdentifier() == null ^ this.getAlarmIdentifier() == null) return false; if (other.getAlarmIdentifier() != null && other.getAlarmIdentifier().equals(this.getAlarmIdentifier()) == false) return false; if (other.getInsufficientDataHealthStatus() == null ^ this.getInsufficientDataHealthStatus() == null) return false; if (other.getInsufficientDataHealthStatus() != null && other.getInsufficientDataHealthStatus().equals(this.getInsufficientDataHealthStatus()) == false) return false; if (other.getRoutingControlArn() == null ^ this.getRoutingControlArn() == null) return false; if (other.getRoutingControlArn() != null && other.getRoutingControlArn().equals(this.getRoutingControlArn()) == false) return false; return true; } @Override public int hashCode() { final int prime = 31; int hashCode = 1; hashCode = prime * hashCode + ((getIPAddress() == null) ? 0 : getIPAddress().hashCode()); hashCode = prime * hashCode + ((getPort() == null) ? 0 : getPort().hashCode()); hashCode = prime * hashCode + ((getType() == null) ? 0 : getType().hashCode()); hashCode = prime * hashCode + ((getResourcePath() == null) ? 0 : getResourcePath().hashCode()); hashCode = prime * hashCode + ((getFullyQualifiedDomainName() == null) ? 0 : getFullyQualifiedDomainName().hashCode()); hashCode = prime * hashCode + ((getSearchString() == null) ? 0 : getSearchString().hashCode()); hashCode = prime * hashCode + ((getRequestInterval() == null) ? 0 : getRequestInterval().hashCode()); hashCode = prime * hashCode + ((getFailureThreshold() == null) ? 0 : getFailureThreshold().hashCode()); hashCode = prime * hashCode + ((getMeasureLatency() == null) ? 0 : getMeasureLatency().hashCode()); hashCode = prime * hashCode + ((getInverted() == null) ? 0 : getInverted().hashCode()); hashCode = prime * hashCode + ((getDisabled() == null) ? 0 : getDisabled().hashCode()); hashCode = prime * hashCode + ((getHealthThreshold() == null) ? 0 : getHealthThreshold().hashCode()); hashCode = prime * hashCode + ((getChildHealthChecks() == null) ? 0 : getChildHealthChecks().hashCode()); hashCode = prime * hashCode + ((getEnableSNI() == null) ? 0 : getEnableSNI().hashCode()); hashCode = prime * hashCode + ((getRegions() == null) ? 0 : getRegions().hashCode()); hashCode = prime * hashCode + ((getAlarmIdentifier() == null) ? 0 : getAlarmIdentifier().hashCode()); hashCode = prime * hashCode + ((getInsufficientDataHealthStatus() == null) ? 0 : getInsufficientDataHealthStatus().hashCode()); hashCode = prime * hashCode + ((getRoutingControlArn() == null) ? 0 : getRoutingControlArn().hashCode()); return hashCode; } @Override public HealthCheckConfig clone() { try { return (HealthCheckConfig) super.clone(); } catch (CloneNotSupportedException e) { throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e); } } }