CODEWITHSUNDEEP
amazon-web-servicesamazon-ecsrtmpaws-fargateaws-elb
Charles
Charles

Reputation: 685

AWS ECS (rtmp) target group unhealthy

I have read the post about how to expose multiple ports in AWS ECS (fargate) load balancer. And I have opened port 80 (HTTP) and 1935 (RTMP) in load balancer and they are also exposed in docker and target definition.

When I describe the service, I could see two target group there.

{
    "services": [
        {
            "serviceArn": "arn:aws:ecs:ap-southeast-2:549825492835:service/race365/race365-ecs-service",
            "serviceName": "race365-ecs-service",
            "clusterArn": "arn:aws:ecs:ap-southeast-2:549825492735:cluster/CLUSTER-NAME",
            "loadBalancers": [
                {
                    "targetGroupArn": "arn:aws:elasticloadbalancing:ap-southeast-2:549825492835:targetgroup/au-http-elb-target-group/0380b91961061a95",
                    "containerName": "website",
                    "containerPort": 80
                },
                {
                    "targetGroupArn": "arn:aws:elasticloadbalancing:ap-southeast-2:549825492835:targetgroup/au-rtmp-elb-target-group/a238b344a3edc138",
                    "containerName": "website",
                    "containerPort": 1935
                }
            ],
            "serviceRegistries": [],
            "status": "ACTIVE",
            "desiredCount": 1,

But the cluster service deployment failed. I checked the target group I created (the rtmp one), and I found that the healthy check also failed.

In (rtmp) target group health check setting page, the protocol is http/https, no rtmp. And I created that target group is for my nginx stream.

How to make rtmp working under AWS ECS (fargate) load balancer?

Please help. Any idea is appreciated.

Thanks.

Upvotes: 0

Views: 106

Answers (0)

Related Questions