# Logstash container crashing on AWS Fargate

**URL:** <https://discuss.elastic.co/t/logstash-container-crashing-on-aws-fargate/338940>\
**Category:** Logstash\
**Created:** [July 21, 2023, 10:27am UTC](https://discuss.elastic.co/t/logstash-container-crashing-on-aws-fargate/338940 "2023-07-21T10:27:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amine1979](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Amine1979](https://discuss.elastic.co/u/Amine1979)\
**Post date:** [July 21, 2023, 10:27am UTC](https://discuss.elastic.co/t/logstash-container-crashing-on-aws-fargate/338940/1 "2023-07-21T10:27:30Z")

</div>

Hello,  
Im using Below DockerFile and taskdefinition to deploy Logstash container on AWS Fargate.  
Issue : Locally it works fine, logstash server start listening on 5044  
On Fargate, container crashs with this message /  
error: open /usr/share/logstash/config/logstash.yml: no such file or directory

DockerFile  
FROM [docker.elastic.co/logstash/logstash:8.7.1](http://docker.elastic.co/logstash/logstash:8.7.1)

TaskDefinition.json

```auto
{
    "taskDefinitionArn": "",
    "containerDefinitions": [
        {
            "name": "xxx",
            "image": "",
            "cpu": 4096,
            "memory": 8192,
            "portMappings": [
                {
                    "containerPort": 5044,
                    "hostPort": 5044,
                    "protocol": "tcp"
                }
            ],
            "essential": true,
            "environment": [],
            "mountPoints": [
                {
                    "sourceVolume": "service-storage",
                    "containerPath": "/usr/share/logstash"
                }
            ],
            "volumesFrom": [],
            "logConfiguration": {
                "logDriver": "awslogs",
                "options": {
                    "awslogs-group": "xxx",
                    "awslogs-region": "eu-central-1",
                    "awslogs-stream-prefix": "ecs"
                }
            }
        }
    ],
    "family": "xxx",
    "taskRoleArn": "",
    "executionRoleArn": "",
    "networkMode": "awsvpc",
    "revision": 2,
    "volumes": [
        {
            "name": "service-storage",
            "host": {}
        }
    ],
    "status": "ACTIVE",
    "requiresAttributes": [
        {
            "name": "com.amazonaws.ecs.capability.logging-driver.awslogs"
        },
        {
            "name": "ecs.capability.execution-role-awslogs"
        },
        {
            "name": "com.amazonaws.ecs.capability.ecr-auth"
        },
        {
            "name": "com.amazonaws.ecs.capability.docker-remote-api.1.19"
        },
        {
            "name": "com.amazonaws.ecs.capability.task-iam-role"
        },
        {
            "name": "ecs.capability.execution-role-ecr-pull"
        },
        {
            "name": "ecs.capability.extensible-ephemeral-storage"
        },
        {
            "name": "com.amazonaws.ecs.capability.docker-remote-api.1.18"
        },
        {
            "name": "ecs.capability.task-eni"
        }
    ],
    "placementConstraints": [],
    "compatibilities": [
        "EC2",
        "FARGATE"
    ],
    "requiresCompatibilities": [
        "FARGATE"
    ],
    "cpu": "4096",
    "memory": "8192",
    "ephemeralStorage": {
        "sizeInGiB": 21
    },
    "runtimePlatform": {
        "cpuArchitecture": "X86_64",
        "operatingSystemFamily": "LINUX"
    },
    "registeredAt": "2023-07-18T21:22:58.495Z",
    "registeredBy": "xxx",
    "tags": [
        {
            "key": "Name",
            "value": "xxx"
        }
    ]
}

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 18, 2023, 10:27am UTC](https://discuss.elastic.co/t/logstash-container-crashing-on-aws-fargate/338940/2 "2023-08-18T10:27:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.