ECS Service Registers EC2 Instance more than desired In my ECS cluster using EC2 launch type

I had a previous problem with deploying my app on ECS using EC2 launch type and It Is now partially solved , I have deleted the entire cluster and created a new one again , and I have configured an ALB balancer and attached it to the service (I.e. this was not set up before) , I was using a t3.medium Instance which come with 2 vCPUs, 4GB Memory , I have set the Task Size to 1 vCPU and Memory to 3 GB (I.e. new revision of my task definition) and as I was planning to only run 1 container, In the Resource allocation limits section of the container, I set the CPU to 1 vCPU and Memory soft limit and hard limit to 1 and 3 respectively and It worked but another problem popped up. Initially while I was creating the new cluster , I didn't specify the min capacity I left It blank and I specified max capacity to 1 and then created the service. The problem Is In cloudformation, the service creation fail , but I in the cluster under services I can see that 1 task Is running and 1 task Is In provisioning status.

1-I don't understand why ECS Is trying to provision 2 tasks while I already specified In the task definition that I only need 1 task.

2-I can see In the ECS cluster infrastructure section , two container Instances registered one In active status and the other Is In draining status. why Is this happening ?

3-How the cloudformation stack for the ECS Service failed , while I have 1 task running on one Container Instance ?

Note:

1- I have suspended the ASG process and returned It back , but before I suspended the ASG process , It had the same behavior.

Task Definition :

{
    "family": "abc",
    "containerDefinitions": [
        {
            "name": "abc-container",
            "image": "<xyz>.dkr.ecr.<region>.amazonaws.com/abc-app:latest",
            "cpu": 1024,
            "memoryReservation": 1024,
            "portMappings": [
                {
                    "name": "abc",
                    "containerPort": 8080,
                    "hostPort": 8080,
                    "protocol": "tcp",
                    "appProtocol": "http"
                }
            ],
            "essential": true,
            "environment": [
                {
                    "name": "MYSQL_DATABASE",
                    "value": "..."
                },
                {
                    "name": "MYSQL_USERNAME",
                    "value": "..."
                },
                {
                    "name": "MYSQL_PASSWORD",
                    "value": "..."
                },
                {
                    "name": "MYSQL_PORT",
                    "value": "..."
                },
                {
                    "name": "MYSQL_HOST",
                    "value": "..."
                }
            ],
            "environmentFiles": [],
            "mountPoints": [],
            "volumesFrom": [],
            "ulimits": [],
            "logConfiguration": {
                "logDriver": "awslogs",
                "options": {
                    "awslogs-create-group": "true",
                    "awslogs-group": "/ecs/my-app",
                    "awslogs-region": "<region>",
                    "awslogs-stream-prefix": "ecs"
                },
                "secretOptions": []
            },
            "systemControls": []
        }
    ],
    "taskRoleArn": "arn:aws:iam::<xyz>:role/ecsTaskExecutionRole",
    "executionRoleArn": "arn:aws:iam::<xyz>:role/ecsTaskExecutionRole",
    "networkMode": "awsvpc",
    "requiresCompatibilities": [
        "EC2"
    ],
    "cpu": "1024",
    "memory": "3072",
    "runtimePlatform": {
        "cpuArchitecture": "X86_64",
        "operatingSystemFamily": "LINUX"
    }
}

2- My related question https://repost.aws/questions/QUrrt5HgwfS4SvAyf1bXiNlw/unable-to-register-a-container-instance-with-ecs