CODEWITHSUNDEEP
amazon-web-servicesaws-cloudformationamazon-elbnlb
Saif
Saif

Reputation: 3462

How does AWS run active health check if Health* properties are not specified for HTTP and TCP?

I have two target groups:

  ATargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      VpcId:
        Fn::ImportValue: !Join [ "", [ !FindInMap [ EnvironmentMap, !Ref Environment, VpcStackName ], "-VPCID" ] ]
      Port: 9001
      Protocol: TCP
      TargetType: ip
      TargetGroupAttributes:
        - Key: deregistration_delay.timeout_seconds
          Value: '30'
        - Key: preserve_client_ip.enabled
          Value: true

  BTargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      VpcId:
        Fn::ImportValue: !Join [ "", [ !FindInMap [ EnvironmentMap, !Ref Environment, VpcStackName ], "-VPCID" ] ]
      Port: 9002
      Protocol: TCP
      TargetType: ip
      TargetGroupAttributes:
        - Key: deregistration_delay.timeout_seconds
          Value: '30'
        - Key: preserve_client_ip.enabled
          Value: true

Both are forwarding traffic to the same containers. On port 9001 I server HTTP traffic. While 9002 servers raw TCP traffic.

How does AWS perform health checks on the registered targets if none of the Health* properties (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-targetgroup.html) are specified on any of the target groups in my cloudformation template?

Upvotes: 0

Views: 207

Answers (1)

azerELweed
azerELweed

Reputation: 115

Based on the link you shared, if the health check path isn't specified AWS will check with the default health check paths. To be sure about it, and judging on previous experience AWS WILL CHECK with its default health check paths so you better specify them if your applications have different paths.

Upvotes: 0

Related Questions