replace asciidocalypse elastic-serverless-forwarder links

Author: colleenmcginnis

docset.yml

@@ -25,6 +25,7 @@ cross_links:
   - ecs-logging-python
   - ecs-logging-ruby
   - eland
+  - elastic-serverless-forwarder
   - elasticsearch
   - elasticsearch-java
   - elasticsearch-js

manage-data/ingest/tools.md

@@ -51,7 +51,7 @@ Depending on the type of data you want to ingest, you have a number of methods a
 | {{beats}} | Use {{beats}} data shippers to send operational data to Elasticsearch directly or through Logstash. | [{{beats}} (Serverless)](asciidocalypse://docs/beats/docs/reference/index.md) <br> [What are {{beats}}?](asciidocalypse://docs/beats/docs/reference/index.md) <br> [{{beats}} and {{agent}} capabilities](/manage-data/ingest/tools.md)|
 | APM | Collect detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more. | [Application performance monitoring (APM)](/solutions/observability/apps/application-performance-monitoring-apm.md) |
 | Application logs | Ingest application logs using Filebeat, {{agent}}, or the APM agent, or reformat application logs into Elastic Common Schema (ECS) logs and then ingest them using Filebeat or {{agent}}.  | [Stream application logs](/solutions/observability/logs/stream-application-logs.md) <br> [ECS formatted application logs](/solutions/observability/logs/ecs-formatted-application-logs.md) |
-| Elastic Serverless forwarder for AWS | Ship logs from your AWS environment to cloud-hosted, self-managed Elastic environments, or {{ls}}. | [Elastic Serverless Forwarder](asciidocalypse://docs/elastic-serverless-forwarder/docs/reference/index.md) |
+| Elastic Serverless forwarder for AWS | Ship logs from your AWS environment to cloud-hosted, self-managed Elastic environments, or {{ls}}. | [Elastic Serverless Forwarder](elastic-serverless-forwarder://reference/index.md) |
 | Connectors | Use connectors to extract data from an original data source and sync it to an {{es}} index. | [Ingest content with Elastic connectors
 ](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/index.md) <br> [Connector clients](asciidocalypse://docs/elasticsearch/docs/reference/ingestion-tools/search-connectors/index.md) |
 | Web crawler | Discover, extract, and index searchable content from websites and knowledge bases using the web crawler. | [Elastic Open Web Crawler](https://github.com/elastic/crawler#readme) |

solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-serverless-forwarder.md

@@ -9,7 +9,7 @@ mapped_pages:
 # Monitor Amazon Web Services (AWS) with Elastic Serverless Forwarder [monitor-aws-esf]
 
 
-The Elastic Serverless Forwarder (ESF) is an Amazon Web Services (AWS) Lambda function that ships logs from your AWS environment to Elastic. Elastic Serverless Forwarder is published in the AWS Serverless Application Repository (SAR). For more information on ESF, check the [Elastic Serverless Forwarder Guide](asciidocalypse://docs/elastic-serverless-forwarder/docs/reference/index.md).
+The Elastic Serverless Forwarder (ESF) is an Amazon Web Services (AWS) Lambda function that ships logs from your AWS environment to Elastic. Elastic Serverless Forwarder is published in the AWS Serverless Application Repository (SAR). For more information on ESF, check the [Elastic Serverless Forwarder Guide](elastic-serverless-forwarder://reference/index.md).
 
 
 ## What you’ll learn [aws-esf-what-you-learn]

troubleshoot/deployments/esf/elastic-serverless-forwarder.md

@@ -18,7 +18,7 @@ You can view the status of deployment actions and get additional information on
 2. You can view the **Deployment history** here and refresh the page for updates as the application deploys. It should take around 5 minutes to deploy — if the deployment fails for any reason, the create events will be rolled back, and you will be able to see an explanation for which event failed.
 
 ::::{note}
-For example, if you don’t increase the visibility timeout for an SQS queue as described in [Amazon S3 (via SQS event notifications)](asciidocalypse://docs/elastic-serverless-forwarder/docs/reference/index.md#aws-serverless-forwarder-inputs-s3), you will see a `CREATE_FAILED`**Status** for the event, and the **Status reason** provides additional detail.
+For example, if you don’t increase the visibility timeout for an SQS queue as described in [Amazon S3 (via SQS event notifications)](elastic-serverless-forwarder://reference/index.md#aws-serverless-forwarder-inputs-s3), you will see a `CREATE_FAILED`**Status** for the event, and the **Status reason** provides additional detail.
 ::::