PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` # Generated by default/object.tt package Paws::ServiceDiscovery::HealthCheckCustomConfig; use Moose; has FailureThreshold => (is => 'ro', isa => 'Int'); 1; ### main pod documentation begin ### =head1 NAME Paws::ServiceDiscovery::HealthCheckCustomConfig =head1 USAGE This class represents one of two things: =head3 Arguments in a call to a service Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object. As an example, if Att1 is expected to be a Paws::ServiceDiscovery::HealthCheckCustomConfig object: $service_obj->Method(Att1 => { FailureThreshold => $value, ..., FailureThreshold => $value }); =head3 Results returned from an API call Use accessors for each attribute. If Att1 is expected to be an Paws::ServiceDiscovery::HealthCheckCustomConfig object: $result = $service_obj->Method(...); $result->Att1->FailureThreshold =head1 DESCRIPTION A complex type that contains information about an optional custom health check. A custom health check, which requires that you use a third-party health checker to evaluate the health of your resources, is useful in the following circumstances: =over =item * You can't use a health check that's defined by C because the resource isn't available over the internet. For example, you can use a custom health check when the instance is in an Amazon VPC. (To check the health of resources in a VPC, the health checker must also be in the VPC.) =item * You want to use a third-party health checker regardless of where your resources are located. =back If you specify a health check configuration, you can specify either C or C but not both. To change the status of a custom health check, submit an C request. Cloud Map doesn't monitor the status of the resource, it just keeps a record of the status specified in the most recent C request. Here's how custom health checks work: =over =item 1. You create a service. =item 2. You register an instance. =item 3. You configure a third-party health checker to monitor the resource that's associated with the new instance. Cloud Map doesn't check the health of the resource directly. =item 4. The third-party health-checker determines that the resource is unhealthy and notifies your application. =item 5. Your application submits an C request. =item 6. Cloud Map waits for 30 seconds. =item 7. If another C request doesn't arrive during that time to change the status back to healthy, Cloud Map stops routing traffic to the resource. =back =head1 ATTRIBUTES =head2 FailureThreshold => Int This parameter is no longer supported and is always set to 1. Cloud Map waits for approximately 30 seconds after receiving an C request before changing the status of the service instance. The number of 30-second intervals that you want Cloud Map to wait after receiving an C request before it changes the health status of a service instance. Sending a second or subsequent C request with the same value before 30 seconds has passed doesn't accelerate the change. Cloud Map still waits C<30> seconds after the first request to make the change. =head1 SEE ALSO This class forms part of L, describing an object used in L =head1 BUGS and CONTRIBUTIONS The source code is located here: L Please report bugs to: L =cut