# AWS EKS Fargate logs

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Faws%2Famazon-eks-fargate-logs.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Faws%2Famazon-eks-fargate-logs.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Seamleslly collect and send your `EKS Fargate` cluster logs straight to Coralogix.

Amazon EKS on Fargate offers a built-in log router based on Fluent Bit. Using the side-car pattern, all logs captured by the container will be sent to Fluent Bit and Coralogix.

## General[​](#general "Direct link to General")

**Private Key** – Your [Send Your Data - API Key](https://coralogix.com/docs/docs/user-guides/account-management/api-keys/send-your-data-api-key/.md) is a unique token that represents your company

**Application Name** – The name of your main application or the environment of the application

**SubSystem Name** – Your application probably has multiple subsystems. For example: Backend servers, Middleware, Frontend servers, etc. in order to help you examine the data you need, inserting the subsystem parameter is vital.

## Configuration[​](#configuration "Direct link to Configuration")

To enable the built-in log router AWS provides, create a kubernetes manifest file named coralogix-logger.yaml with the FluentBit configMap named `aws-logging` in the `aws-observability` namespace.

```
kind: Namespace

apiVersion: v1

metadata:

  name: aws-observability

  labels:

    aws-observability: enabled

---

kind: ConfigMap

apiVersion: v1

metadata:

  name: aws-logging

  namespace: aws-observability

data:

  filters.conf: |

    [FILTER]

        Name parser

        Match *

        Key_name log

        Parser crio



    [FILTER]

        Name             kubernetes

        Match            kube.*

        Merge_Log           On

        Buffer_Size         0

        Kube_Meta_Cache_TTL 300s

        Keep_Log Off

        Merge_Log_Key log_obj

        K8S-Logging.Parser On

        K8S-Logging.Exclude On

        Annotations Off

  output.conf: |

    [OUTPUT]

        Name  kinesis_firehose

        Match *

        region <AWS_Region>

        delivery_stream <Delivery_Stream_Name>

  parsers.conf: |

    [PARSER]

        Name crio

        Format Regex

        Regex ^(?<time>[^ ]+) (?<stream>stdout|stderr) (?<logtag>P|F) (?<log>.*)$

        Time_Key    time

        Time_Format %Y-%m-%dT%H:%M:%S.%L%z

        Time_Keep true
```

Note: change the `<Delivery_stream_Name>` to your kinesis delivery stream name and `<AWS_Region>` to the delivery stream region.

Then apply the manifest file to your EKS cluster

```
kubectl apply -f coralogix-logger.yaml
```

Now we need to add to the pod execution role a policy that allows pods to send record to firehose.

Go to AWS EKS -> Clusters -> 'Your-cluster' -> Compute -> 'Your-Fargate-Profile' -> Pod execution role

```
{

    "Version": "2012-10-17",

    "Statement": [

        {

            "Effect": "Allow",

            "Action": [

                "firehose:PutRecord",

                "firehose:PutRecordBatch"

            ],

            "Resource": [

                "<firehose_ARN>"

            ]

        }

    ]

}
```

Note: Each fargate profile has a different execution role so apply this step to all your profiles.

To apply all these changes the pods have to restart.

That's it all logs will be sent to your firehose delivery stream.

Note: don't forget to follow our guide on [Configuring firehose](https://coralogix.com/docs/docs/integrations/aws/amazon-data-firehose/send-logs-using-amazon-data-firehose/.md) to make sure you have your firehose configured correctly.