service "service-name" port 80 is unhealthy in target-group "target-group" due to (reason Health checks failed with these codes: [502]).

Can you confirm cpu/mem requirements of containers?Increasing CPU limit of task if it is possible.

Hmm..It seems its not resource issue. So my additional question is as follows.

· Can't you find containers launch successfuly from container logs? · Where 172.31.33.49 comes from? Tasks IP?Doesn't it change when task recreated?When I wrote cdk code about fargate I used service.attachToApplicationTargetGroup to specify target so specifying ip address is not needed.

// Target Group
const targetGroup = new elbv2.ApplicationTargetGroup(this, 'TargetGroup', {
      vpc,
      port: 80,
      protocol: elbv2.ApplicationProtocol.HTTP,
      targetType: elbv2.TargetType.IP,
      healthCheck: {
        path: '/',
        interval: Duration.seconds(60),
        healthyHttpCodes: '200'
      },
    })

 listener.addTargetGroups('TargetGroup', {
   targetGroups: [targetGroup],
 })

const service = new ecs.Ec2Service(this, 'Service', {
      cluster,
      taskDefinition,
      securityGroups: [securityGroupAPP],
    })
    service.attachToApplicationTargetGroup(targetGroup)
  }