From 905386002f171c22b514f014ca00c365f2e82d70 Mon Sep 17 00:00:00 2001 From: Doron Bargo <62555360+Doron-Bargo@users.noreply.github.com> Date: Mon, 4 Sep 2023 13:55:59 +0300 Subject: [PATCH] Update aws-s3-bucket.md --- docs/shipping/AWS/aws-s3-bucket.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/shipping/AWS/aws-s3-bucket.md b/docs/shipping/AWS/aws-s3-bucket.md index 520baa0b..16cc3c99 100644 --- a/docs/shipping/AWS/aws-s3-bucket.md +++ b/docs/shipping/AWS/aws-s3-bucket.md @@ -14,6 +14,10 @@ metrics_alerts: [] drop_filter: [] --- +These instructions support collecting logs and metrics from S3 bucket +* [Collect logs from S3 Bucket](#logs) +* [Collect S3 metrics](#metrics) + ## Logs Some AWS services can be configured to ship their logs to an S3 bucket, where Logz.io can fetch those logs directly. @@ -41,10 +45,10 @@ Please keep these notes in mind when configuring logging. ### Which shipping method is right for you -* If your data is organized in alphabetical order, you should opt for the S3 fetcher. Logz.io operates this fetcher on our end, directly accessing your S3 to retrieve the data. +* If your data is organized in alphabetical order, you should opt for the [S3 fetcher](#shipping-logs-via-s3-fetcher). Logz.io operates this fetcher on our end, directly accessing your S3 to retrieve the data. -* If your data is not organized in alphabetical order, use the S3 hook. This approach requires deploying a Lambda function within your environment to manage the process. +* If your data is not organized in alphabetical order, use the [S3 hook](#shipping-logs-via-s3-hook). This approach requires deploying a Lambda function within your environment to manage the process. ### Shipping logs via S3 Fetcher @@ -663,4 +667,4 @@ Give your data some time to get from your system to ours, then log in to your Lo -{@include: ../../_include/metric-shipping/generic-dashboard.html} \ No newline at end of file +{@include: ../../_include/metric-shipping/generic-dashboard.html}