Ship Elastic Container Service logs

• Overview
• Manual deployment (AWS Classic Console)
• Automated CloudFormation deployment

This integration uses Fluentd in a Docker container to forward logs from your Amazon Elastic Container Service (ECS) cluster to Logz.io.

This integration refers to an EC2-based cluster. For Fargate-based cluster see our Fargate documentation.

Fluentd will fetch all existing logs, as it is not able to ignore older logs.

Manual deployment (AWS Classic Console)

Download the task definition JSON

wget https://raw.githubusercontent.com/logzio/logzio-aws-ecs/master/task-definition.json

Configure the task

In your prefered text editor, open the JSON you downloaded in the previous step and replace the following:

Paramater	Details
<<LOG-SHIPPING-TOKEN>>	Required. Your Logz.io account token. Replace with the token of the account you want to ship to.
<<LISTENER-HOST>>	Required. Your Logz.io listener URL. Replace with your region’s listener URL.

Advanced settings (optional)

Since the Docker image is based on Logz.io’s fluentd-docker-logs image, any of the environment variables mentioned here can be added to the task definition JSON.

Add your task definition

1. In your Amazon ECS Classic Console menu, go to Task Definitions and click on Create new Task Definition.

2. In the Step 1: Select launch type compatibility screen, choose EC2 and click Next step.

3. In the Step 2: Configure task and container definitions screen, scroll down and click on the Configure via JSON button.

4. In the text-box, delete the existing text and paste your configured task definition JSON. Press Save, then press Create.

Run the task

1. After the task creation, click on the Actions button, then choose Run Task.

2. In the Run Task screen, choose EC2 as your Launch type.

3. Choose the cluster you want to ship logs from.

4. For Placement Templates, choose One Task Per Host.

5. Click on Run Task.

Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Open Search Dashboards.

Automated CloudFormation deployment

Configure and create your stack

Click the button that matches your AWS region, then follow the instructions below:

AWS Region	Launch button
us-east-1

If your region is not on the list, let us know in the repo’s issues, or reach out to Logz.io support team!

In screen Step 1 Specify template:

Keep the defaults and click Next.

In screen Step 2 Specify stack details:

1. For Stack name you can either keep the default, or change the stack name.

2. For LogzioListener - choose your Logz.io listener from the list.

3. For LogzioToken - insert your Logz.io logs shipping token.

4. Click Next.

In screen Step 3 Configure stack options (Optional):

If you want to, you can add your custom tags, or not. Click on Next.

In screen Step 4 Review:

Scroll down and click on Create stack.

Give your stack a few moments to launch.

Run the task

1. Go to your AWS ECS page, and on the left menu, click on Task Definitions, then choose the task you just created.

2. Click on the Actions button, then choose Run Task.

3. In the Run Task screen, choose EC2 as your Launch type.

4. Choose the cluster you want to ship logs from.

5. For Placement Templates choose One Task Per Host.

6. Click on Run Task.

Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Open Search Dashboards.