Prios

docs/shipping/AWS/aws-api-gateway.md

@@ -1,7 +1,7 @@
 ---
 id: AWS-API-Gateway
 title: AWS API Gateway
-overview: This integration creates a Kinesis Data Firehose delivery stream that links to your Amazon MQ metrics stream and then sends the metrics to your Logz.io account. It also creates a Lambda function that adds AWS namespaces to the metric stream, and a Lambda function that collects and ships the resources' tags.
+overview: This integration creates a Kinesis Data Firehose delivery stream that links to your Amazon API Gateway metrics stream and then sends the metrics to your Logz.io account. It also creates a Lambda function that adds AWS namespaces to the metric stream, and a Lambda function that collects and ships the resources' tags.
 product: ['metrics']
 os: []
 filters: ['AWS', 'Access Management', 'Most Popular']
@@ -14,6 +14,92 @@ metrics_alerts: []
 drop_filter: []
 ---
 
+## Logs
+
+
+:::note
+For a much easier and more efficient way to collect and send telemetry, consider using the [Logz.io telemetry collector](https://app.logz.io/#/dashboard/send-your-data/agent/new).
+:::
+
+
+## Configure AWS to forward logs to Logz.io
+
+This integration uses Fluentd in a Docker container to forward logs from your Amazon Elastic Container Service (ECS) cluster to Logz.io.
+
+:::note
+This integration refers to an EC2-based cluster. For Fargate-based cluster see [our Fargate documentation](https://docs.logz.io/shipping/log-sources/fargate.html).
+:::
+
+
+:::caution Important
+Fluentd will fetch all existing logs, as it is not able to ignore older logs.
+:::
+
+### 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` | [![Deploy to AWS](https://dytvr9ot2sszz.cloudfront.net/logz-docs/lights/LightS-button.png)](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create/template?templateURL=https://logzio-aws-integrations-us-east-1.s3.amazonaws.com/logzio-aws-ecs/1.0.0/auto-deployment.json&stackName=logzio-aws-ecs-auto-deployment) |
+
+:::note
+If your region is not on the list, let us know in the [repo's issues](https://github.com/logzio/logzio-aws-ecs/issues), or reach out to Logz.io support team!
+:::
+
+
+####### In screen **Step 1 Specify template**:
+
+Keep the defaults and click **Next**.
+
+![Screen_1](https://dytvr9ot2sszz.cloudfront.net/logz-docs/ecs/screen_01.png)
+
+####### 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**.
+
+![Screen_2](https://dytvr9ot2sszz.cloudfront.net/logz-docs/ecs/screen_02.png)
+
+####### 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](https://app.logz.io/#/dashboard/osd).
+
+
+## Metrics
+
 
 :::note
 For a much easier and more efficient way to collect and send metrics, consider using the [Logz.io telemetry collector](https://app.logz.io/#/dashboard/send-your-data/agent/new).