fixed links

Author: guywi-ms

articles/sentinel/connect-aws-configure-environment.md

@@ -1,5 +1,5 @@
 ---
-title: Set up your Amazon Web Services environment to collect AWS logs to Microsoft Sentinel
+title: Set up your Amazon Web Services (AWS) environment to collect AWS logs to Microsoft Sentinel
 description: Set up your Amazon Web Services environment to send AWS logs to Microsoft Sentinel using one of the Microsoft Sentinel AWS connectors.
 author: guywi-ms
 ms.author: guywild
@@ -11,7 +11,7 @@ ms.date: 05/28/2025
 
 ---
 
-# Set up your Amazon Web Services environment to collect AWS logs to Microsoft Sentinel
+# Set up your Amazon Web Services (AWS) environment to collect AWS logs to Microsoft Sentinel
 
 Amazon Web Services (AWS) connectors simplify the process of collecting logs from Amazon S3 (Simple Storage Service) and ingesting them into Microsoft Sentinel. The connectors provide tools to help you configure your AWS environment for Microsoft Sentinel log collection.
 
@@ -47,7 +47,7 @@ This diagram shows how to set up your AWS environment to send logs to Azure:
 
 ### Manual setup
 
-Although you can set up the AWS environment manually, as described below, we strongly recommend using the automated tools provided when you [deploy AWS connectors](#deploy-aws-connectors) instead.
+Although you can set up the AWS environment manually, as described below, we strongly recommend using the automated tools provided when you [deploy AWS connectors](#4-deploy-aws-connectors) instead.
 
 #### 1. Create an S3 bucket and SQS queue
 
@@ -117,7 +117,7 @@ Follow these instructions in the AWS documentation:<br>[Creating OpenID Connect
      ]
    }
    ```
-
+ 
    - `XXXXXXXXXXXX` is your AWS Account ID.
    - `XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX` is your Microsoft Sentinel workspace ID.
 

articles/sentinel/connect-aws.md

@@ -40,7 +40,7 @@ This tab explains how to configure the AWS S3 connector using one of two methods
     - **Amazon VPC**: .csv file in GZIP format with headers; delimiter: space.
     - **Amazon GuardDuty**: json-line and GZIP formats.
     - **AWS CloudTrail**: .json file in a GZIP format.
-    - **CloudWatch**: .csv file in a GZIP format without a header. If you need to convert your logs to this format, you can use this [CloudWatch lambda function](cloudwatch-lambda-function.yml).
+    - **CloudWatch**: .csv file in a GZIP format without a header. If you need to convert your logs to this format, you can use this [CloudWatch lambda function](#send-formatted-cloudwatch-events-to-s3-using-a-lambda-function-optional).
 
 
 ## Automatic setup
@@ -148,7 +148,7 @@ Learn how to [troubleshoot Amazon Web Services S3 connector issues](aws-s3-troub
 This tab explains how to configure the AWS CloudTrail connector. The process of setting it up has two parts: the AWS side and the Microsoft Sentinel side. Each side's process produces information used by the other side. This two-way authentication creates secure communication.
 
 > [!NOTE]
-> AWS CloudTrail has [built-in limitations](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/WhatIsCloudTrail-Limits.html) in its LookupEvents API. It allows no more than two transactions per second (TPS) per account, and each query can return a maximum of 50 records. Consequently, if a single tenant constantly generates more than 100 records per second in one region, backlogs and delays in data ingestion will result.
+> AWS CloudTrail has [built-in limitations](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/WhatIsCloudTrail-Limits.html) in its LookupEvents API. It allows no more than two transactions per second (TPS) per account, and each query can return a maximum of 50 records. If a single tenant constantly generates more than 100 records per second in one region, backlogs and delays in data ingestion will result.
 >
 > Currently, you can only connect your AWS Commercial CloudTrail to Microsoft Sentinel and not AWS GovCloud CloudTrail.
 

redirects/.openpublishing.redirection.sentinel.json

@@ -2219,6 +2219,11 @@
             "source_path_from_root": "/articles/sentinel/data-connectors/awake-security.md",
             "redirect_url": "/previous-versions/azure/sentinel/data-connectors/awake-security-via-legacy-agent",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/sentinel/cloudwatch-lambda-function.md",
+            "redirect_url": "/azure/sentinel/connect-aws#send-formatted-cloudwatch-events-to-s3-using-a-lambda-function-optional",
+            "redirect_document_id": false
         }
     ]
 }