Qodex.ai

Create Target Group

GET {{aws_elastic_load_balancing_base_url}}/?HealthCheckEnabled&HealthCheckIntervalSeconds&HealthCheckPath&HealthCheckPort&HealthCheckProtocol&HealthCheckTimeoutSeconds&HealthyThresholdCount&Matcher&Name&Port&Protocol&TargetType&UnhealthyThresholdCount&VpcId&Action=CreateTargetGroup&Version=2015-12-01

Request Params

KeyDatatypeRequiredDescription
HealthCheckEnablednullIndicates whether health checks are enabled. If the target type is lambda, health checks are disabled by default but can be enabled. If the target type is instance or ip, health checks are always enabled and cannot be disabled.
HealthCheckIntervalSecondsnullThe approximate amount of time, in seconds, between health checks of an individual target. For HTTP and HTTPS health checks, the range is 5–300 seconds. For TCP health checks, the supported values are 10 and 30 seconds. If the target type is instance or ip, the default is 30 seconds. If the target type is lambda, the default is 35 seconds.
HealthCheckPathnull[HTTP/HTTPS health checks] The ping path that is the destination on the targets for health checks. The default is /.
HealthCheckPortnullThe port the load balancer uses when performing health checks on targets. The default is traffic-port, which is the port on which each target receives traffic from the load balancer.
HealthCheckProtocolnullThe protocol the load balancer uses when performing health checks on targets. For Application Load Balancers, the default is HTTP. For Network Load Balancers, the default is TCP. The TCP protocol is supported for health checks only if the protocol of the target group is TCP, TLS, UDP, or TCP_UDP. The TLS, UDP, and TCP_UDP protocols are not supported for health checks.
HealthCheckTimeoutSecondsnullThe amount of time, in seconds, during which no response from a target means a failed health check. For target groups with a protocol of HTTP or HTTPS, the default is 5 seconds. For target groups with a protocol of TCP or TLS, this value must be 6 seconds for HTTP health checks and 10 seconds for TCP and HTTPS health checks. If the target type is lambda, the default is 30 seconds.
HealthyThresholdCountnullThe number of consecutive health checks successes required before considering an unhealthy target healthy. For target groups with a protocol of HTTP or HTTPS, the default is 5. For target groups with a protocol of TCP or TLS, the default is 3. If the target type is lambda, the default is 5.
Matchernull[HTTP/HTTPS health checks] The HTTP codes to use when checking for a successful response from a target.
NamenullThe name of the target group.
PortnullThe port on which the targets receive traffic. This port is used unless you specify a port override when registering the target. If the target is a Lambda function, this parameter does not apply.
ProtocolnullThe protocol to use for routing traffic to the targets. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocols are TCP, TLS, UDP, or TCP_UDP. A TCP_UDP listener must be associated with a TCP_UDP target group. If the target is a Lambda function, this parameter does not apply.
TargetTypenullThe type of target that you must specify when registering targets with this target group. You can't specify targets for a target group using more than one target type.
UnhealthyThresholdCountnullThe number of consecutive health check failures required before considering a target unhealthy. For target groups with a protocol of HTTP or HTTPS, the default is 2. For target groups with a protocol of TCP or TLS, this value must be the same as the healthy threshold count. If the target type is lambda, the default is 2.
VpcIdnullThe identifier of the virtual private cloud (VPC). If the target is a Lambda function, this parameter does not apply. Otherwise, this parameter is required.
Actionstring