public class GetHealthCheckStatusRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
GetHealthCheckStatus operation.
To retrieve the health check status, send a GET request
to the 2013-04-01/healthcheck/health check ID/status
resource. You can use this call to get a health check's current
status.
NOOP| Constructor and Description |
|---|
GetHealthCheckStatusRequest() |
| Modifier and Type | Method and Description |
|---|---|
GetHealthCheckStatusRequest |
clone() |
boolean |
equals(Object obj) |
String |
getHealthCheckId()
If you want Amazon Route 53 to return this resource record set in
response to a DNS query only when a health check is passing, include
the
HealthCheckId element and specify the ID of the
applicable health check. |
int |
hashCode() |
void |
setHealthCheckId(String healthCheckId)
If you want Amazon Route 53 to return this resource record set in
response to a DNS query only when a health check is passing, include
the
HealthCheckId element and specify the ID of the
applicable health check. |
String |
toString()
Returns a string representation of this object; useful for testing and
debugging.
|
GetHealthCheckStatusRequest |
withHealthCheckId(String healthCheckId)
If you want Amazon Route 53 to return this resource record set in
response to a DNS query only when a health check is passing, include
the
HealthCheckId element and specify the ID of the
applicable health check. |
copyBaseTo, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic String getHealthCheckId()
HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
Constraints:
Length: 0 - 64
HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
public void setHealthCheckId(String healthCheckId)
HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
Constraints:
Length: 0 - 64
healthCheckId - If you want Amazon Route 53 to return this resource record set in
response to a DNS query only when a health check is passing, include
the HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
public GetHealthCheckStatusRequest withHealthCheckId(String healthCheckId)
HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Length: 0 - 64
healthCheckId - If you want Amazon Route 53 to return this resource record set in
response to a DNS query only when a health check is passing, include
the HealthCheckId element and specify the ID of the
applicable health check. Amazon Route 53 determines whether a resource record set is healthy by periodically sending a request to the endpoint that is specified in the health check. If that endpoint returns an HTTP status code of 2xx or 3xx, the endpoint is healthy. If the endpoint returns an HTTP status code of 400 or greater, or if the endpoint doesn't respond for a certain amount of time, Amazon Route 53 considers the endpoint unhealthy and also considers the resource record set unhealthy.
The HealthCheckId element is
only useful when Amazon Route 53 is choosing between two or more
resource record sets to respond to a DNS query, and you want Amazon
Route 53 to base the choice in part on the status of a health check.
Configuring health checks only makes sense in the following
configurations:
You
set EvaluateTargetHealth to true for the
resource record sets in an alias, weighted alias, latency alias,
geolocation alias, or failover alias resource record set, and you
specify health check IDs for all of the resource record sets that are
referenced by the alias resource record sets. For more information
about this configuration, see EvaluateTargetHealth.
Amazon
Route 53 doesn't check the health of the endpoint specified in the
resource record set, for example, the endpoint specified by the IP
address in the Value element. When you add a
HealthCheckId element to a resource record set, Amazon
Route 53 checks the health of the endpoint that you specified in the
health check.
For geolocation resource record sets, if
an endpoint is unhealthy, Amazon Route 53 looks for a resource record
set for the larger, associated geographic region. For example, suppose
you have resource record sets for a state in the United States, for
the United States, for North America, and for all locations. If the
endpoint for the state resource record set is unhealthy, Amazon Route
53 checks the resource record sets for the United States, for North
America, and for all locations (a resource record set for which the
value of CountryCode is *), in that order, until it finds
a resource record set for which the endpoint is healthy.
If your
health checks specify the endpoint only by domain name, 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-1-www.example.com), not the name
of the resource record sets (example.com). FullyQualifiedDomainName matches the name of the resource
record sets and then associate the health check with those resource
record sets, health check results will be unpredictable.
public String toString()
toString in class ObjectObject.toString()public GetHealthCheckStatusRequest clone()
clone in class AmazonWebServiceRequestCopyright © 2015. All rights reserved.