Interface HealthCheckSource.Builder

  • Method Details

    • healthCheckSourceId

      HealthCheckSource.Builder healthCheckSourceId(String healthCheckSourceId)

      The ID of the health check source. Route 53 assigns this ID when it creates the source.

      Parameters:
      healthCheckSourceId - The ID of the health check source. Route 53 assigns this ID when it creates the source.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • healthCheckSourceStatus

      HealthCheckSource.Builder healthCheckSourceStatus(String healthCheckSourceStatus)

      The current status of the health check source. The health check source status can have one of the following values:

      • CREATE_PENDING - Route 53 accepted the request to create the source and hasn't started creating it. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_IN_PROGRESS - Route 53 is creating the source. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_COMPLETED - The source is ready to use.

      • CREATE_FAILED - Route 53 couldn't create the source. StatusReasonCode and StatusReason explain why.

      • DELETE_PENDING - Route 53 accepted the request to delete the source and hasn't started deleting it.

      • DELETE_IN_PROGRESS - Route 53 is deleting the source.

      • DELETE_COMPLETED - Route 53 has deleted the source. You can't retrieve a health check source in this status: GetHealthCheckSource returns NoSuchHealthCheckSource.

      • DELETE_FAILED - Route 53 couldn't delete the source. StatusReasonCode and StatusReason explain why.

      If the status is CREATE_FAILED, fix the cause that StatusReasonCode indicates, and then either retry CreateHealthCheckSource with the same CallerReference and settings, or delete the source and create a new one. If the status is DELETE_FAILED, retry the DeleteHealthCheckSource request.

      Parameters:
      healthCheckSourceStatus - The current status of the health check source. The health check source status can have one of the following values:

      • CREATE_PENDING - Route 53 accepted the request to create the source and hasn't started creating it. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_IN_PROGRESS - Route 53 is creating the source. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_COMPLETED - The source is ready to use.

      • CREATE_FAILED - Route 53 couldn't create the source. StatusReasonCode and StatusReason explain why.

      • DELETE_PENDING - Route 53 accepted the request to delete the source and hasn't started deleting it.

      • DELETE_IN_PROGRESS - Route 53 is deleting the source.

      • DELETE_COMPLETED - Route 53 has deleted the source. You can't retrieve a health check source in this status: GetHealthCheckSource returns NoSuchHealthCheckSource.

      • DELETE_FAILED - Route 53 couldn't delete the source. StatusReasonCode and StatusReason explain why.

      If the status is CREATE_FAILED, fix the cause that StatusReasonCode indicates, and then either retry CreateHealthCheckSource with the same CallerReference and settings, or delete the source and create a new one. If the status is DELETE_FAILED, retry the DeleteHealthCheckSource request.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • healthCheckSourceStatus

      HealthCheckSource.Builder healthCheckSourceStatus(HealthCheckSourceStatus healthCheckSourceStatus)

      The current status of the health check source. The health check source status can have one of the following values:

      • CREATE_PENDING - Route 53 accepted the request to create the source and hasn't started creating it. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_IN_PROGRESS - Route 53 is creating the source. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_COMPLETED - The source is ready to use.

      • CREATE_FAILED - Route 53 couldn't create the source. StatusReasonCode and StatusReason explain why.

      • DELETE_PENDING - Route 53 accepted the request to delete the source and hasn't started deleting it.

      • DELETE_IN_PROGRESS - Route 53 is deleting the source.

      • DELETE_COMPLETED - Route 53 has deleted the source. You can't retrieve a health check source in this status: GetHealthCheckSource returns NoSuchHealthCheckSource.

      • DELETE_FAILED - Route 53 couldn't delete the source. StatusReasonCode and StatusReason explain why.

      If the status is CREATE_FAILED, fix the cause that StatusReasonCode indicates, and then either retry CreateHealthCheckSource with the same CallerReference and settings, or delete the source and create a new one. If the status is DELETE_FAILED, retry the DeleteHealthCheckSource request.

      Parameters:
      healthCheckSourceStatus - The current status of the health check source. The health check source status can have one of the following values:

      • CREATE_PENDING - Route 53 accepted the request to create the source and hasn't started creating it. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_IN_PROGRESS - Route 53 is creating the source. You can't use the source in a health check until its status is CREATE_COMPLETED.

      • CREATE_COMPLETED - The source is ready to use.

      • CREATE_FAILED - Route 53 couldn't create the source. StatusReasonCode and StatusReason explain why.

      • DELETE_PENDING - Route 53 accepted the request to delete the source and hasn't started deleting it.

      • DELETE_IN_PROGRESS - Route 53 is deleting the source.

      • DELETE_COMPLETED - Route 53 has deleted the source. You can't retrieve a health check source in this status: GetHealthCheckSource returns NoSuchHealthCheckSource.

      • DELETE_FAILED - Route 53 couldn't delete the source. StatusReasonCode and StatusReason explain why.

      If the status is CREATE_FAILED, fix the cause that StatusReasonCode indicates, and then either retry CreateHealthCheckSource with the same CallerReference and settings, or delete the source and create a new one. If the status is DELETE_FAILED, retry the DeleteHealthCheckSource request.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • healthCheckSourceConfig

      HealthCheckSource.Builder healthCheckSourceConfig(HealthCheckSourceConfig healthCheckSourceConfig)

      The virtual private cloud (VPC), subnets, and security groups for the health check source.

      Parameters:
      healthCheckSourceConfig - The virtual private cloud (VPC), subnets, and security groups for the health check source.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • healthCheckSourceConfig

      default HealthCheckSource.Builder healthCheckSourceConfig(Consumer<HealthCheckSourceConfig.Builder> healthCheckSourceConfig)

      The virtual private cloud (VPC), subnets, and security groups for the health check source.

      This is a convenience method that creates an instance of the HealthCheckSourceConfig.Builder avoiding the need to create one manually via HealthCheckSourceConfig.builder().

      When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to healthCheckSourceConfig(HealthCheckSourceConfig).

      Parameters:
      healthCheckSourceConfig - a consumer that will call methods on HealthCheckSourceConfig.Builder
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • statusReasonCode

      HealthCheckSource.Builder statusReasonCode(String statusReasonCode)

      A code that indicates why the health check source has a status of CREATE_FAILED or DELETE_FAILED. Route 53 returns this member only when the status is one of those values. The code can have one of the following values:

      • INSUFFICIENT_SUBNET_IPS - One of the specified subnets doesn't have enough free private IP addresses. Check the available IP addresses in each subnet, and delete network interfaces that you don't need.

      • EC2_LIMIT_EXCEEDED - Your account reached an Amazon virtual private cloud (VPC) quota for network interfaces or security groups. Delete network interfaces that you don't need, specify fewer security groups, or request a quota increase.

      • INVALID_SUBNET - One of the specified subnets doesn't exist or isn't valid, or an AvailabilityZoneId doesn't match the Availability Zone of its subnet. Check that each subnet ID is correct, that the subnet exists, and that each AvailabilityZoneId matches its subnet.

      • INVALID_SECURITY_GROUP - One of the specified security groups doesn't exist or isn't valid. Check that each security group ID is correct and that the security group exists.

      • INVALID_CONFIGURATION - The combination of VPC, subnets, and security groups isn't valid. Check that VpcId is correct and exists, that each subnet is in that VPC, and that the security groups for each subnet are in the same VPC as that subnet.

      • SLR_MISSING_OR_NOT_ASSUMABLE - Route 53 couldn't assume its service-linked role in your account. In IAM, check that the service-linked role for Route 53 private endpoint health checks exists and that no deletion task for it is in progress.

      • INTERNAL_ERROR - Route 53 encountered an internal error. Contact Amazon Web Services Support and provide the health check source ID.

      Parameters:
      statusReasonCode - A code that indicates why the health check source has a status of CREATE_FAILED or DELETE_FAILED. Route 53 returns this member only when the status is one of those values. The code can have one of the following values:

      • INSUFFICIENT_SUBNET_IPS - One of the specified subnets doesn't have enough free private IP addresses. Check the available IP addresses in each subnet, and delete network interfaces that you don't need.

      • EC2_LIMIT_EXCEEDED - Your account reached an Amazon virtual private cloud (VPC) quota for network interfaces or security groups. Delete network interfaces that you don't need, specify fewer security groups, or request a quota increase.

      • INVALID_SUBNET - One of the specified subnets doesn't exist or isn't valid, or an AvailabilityZoneId doesn't match the Availability Zone of its subnet. Check that each subnet ID is correct, that the subnet exists, and that each AvailabilityZoneId matches its subnet.

      • INVALID_SECURITY_GROUP - One of the specified security groups doesn't exist or isn't valid. Check that each security group ID is correct and that the security group exists.

      • INVALID_CONFIGURATION - The combination of VPC, subnets, and security groups isn't valid. Check that VpcId is correct and exists, that each subnet is in that VPC, and that the security groups for each subnet are in the same VPC as that subnet.

      • SLR_MISSING_OR_NOT_ASSUMABLE - Route 53 couldn't assume its service-linked role in your account. In IAM, check that the service-linked role for Route 53 private endpoint health checks exists and that no deletion task for it is in progress.

      • INTERNAL_ERROR - Route 53 encountered an internal error. Contact Amazon Web Services Support and provide the health check source ID.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • statusReasonCode

      A code that indicates why the health check source has a status of CREATE_FAILED or DELETE_FAILED. Route 53 returns this member only when the status is one of those values. The code can have one of the following values:

      • INSUFFICIENT_SUBNET_IPS - One of the specified subnets doesn't have enough free private IP addresses. Check the available IP addresses in each subnet, and delete network interfaces that you don't need.

      • EC2_LIMIT_EXCEEDED - Your account reached an Amazon virtual private cloud (VPC) quota for network interfaces or security groups. Delete network interfaces that you don't need, specify fewer security groups, or request a quota increase.

      • INVALID_SUBNET - One of the specified subnets doesn't exist or isn't valid, or an AvailabilityZoneId doesn't match the Availability Zone of its subnet. Check that each subnet ID is correct, that the subnet exists, and that each AvailabilityZoneId matches its subnet.

      • INVALID_SECURITY_GROUP - One of the specified security groups doesn't exist or isn't valid. Check that each security group ID is correct and that the security group exists.

      • INVALID_CONFIGURATION - The combination of VPC, subnets, and security groups isn't valid. Check that VpcId is correct and exists, that each subnet is in that VPC, and that the security groups for each subnet are in the same VPC as that subnet.

      • SLR_MISSING_OR_NOT_ASSUMABLE - Route 53 couldn't assume its service-linked role in your account. In IAM, check that the service-linked role for Route 53 private endpoint health checks exists and that no deletion task for it is in progress.

      • INTERNAL_ERROR - Route 53 encountered an internal error. Contact Amazon Web Services Support and provide the health check source ID.

      Parameters:
      statusReasonCode - A code that indicates why the health check source has a status of CREATE_FAILED or DELETE_FAILED. Route 53 returns this member only when the status is one of those values. The code can have one of the following values:

      • INSUFFICIENT_SUBNET_IPS - One of the specified subnets doesn't have enough free private IP addresses. Check the available IP addresses in each subnet, and delete network interfaces that you don't need.

      • EC2_LIMIT_EXCEEDED - Your account reached an Amazon virtual private cloud (VPC) quota for network interfaces or security groups. Delete network interfaces that you don't need, specify fewer security groups, or request a quota increase.

      • INVALID_SUBNET - One of the specified subnets doesn't exist or isn't valid, or an AvailabilityZoneId doesn't match the Availability Zone of its subnet. Check that each subnet ID is correct, that the subnet exists, and that each AvailabilityZoneId matches its subnet.

      • INVALID_SECURITY_GROUP - One of the specified security groups doesn't exist or isn't valid. Check that each security group ID is correct and that the security group exists.

      • INVALID_CONFIGURATION - The combination of VPC, subnets, and security groups isn't valid. Check that VpcId is correct and exists, that each subnet is in that VPC, and that the security groups for each subnet are in the same VPC as that subnet.

      • SLR_MISSING_OR_NOT_ASSUMABLE - Route 53 couldn't assume its service-linked role in your account. In IAM, check that the service-linked role for Route 53 private endpoint health checks exists and that no deletion task for it is in progress.

      • INTERNAL_ERROR - Route 53 encountered an internal error. Contact Amazon Web Services Support and provide the health check source ID.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • statusReason

      HealthCheckSource.Builder statusReason(String statusReason)

      A description of why the health check source has a status of CREATE_FAILED or DELETE_FAILED, and what you can do about it. The text corresponds to the value of StatusReasonCode. Route 53 returns this member only when StatusReasonCode is present.

      Parameters:
      statusReason - A description of why the health check source has a status of CREATE_FAILED or DELETE_FAILED, and what you can do about it. The text corresponds to the value of StatusReasonCode. Route 53 returns this member only when StatusReasonCode is present.
      Returns:
      Returns a reference to this object so that method calls can be chained together.