Add cross-links to useful docs and a note

Author: vishaangelova

manage-data/ingest/ingesting-data-from-applications/ingest-logs-from-python-application-using-filebeat.md

@@ -123,19 +123,19 @@ In this step, you’ll create a Python script that generates logs in JSON format
 
 ## Prepare your connection and authentication details [ec-authentication-details]
 
-To connect to your {{ech}} deployment, stream data, and issue queries, you have to specify the connection details using your deployment's [Cloud ID](/deploy-manage/deploy/elastic-cloud/find-cloud-id.md), and you have to authenticate using either _basic authentication_ or an _API key_.
+To connect to your {{ech}} deployment, stream data, and issue queries, you have to specify the connection details using your deployment's Cloud ID, and you have to authenticate using either _basic authentication_ or an _API key_.
 
 ### Cloud ID
 
-To find the Cloud ID of your deployment, go to the {{kib}} main menu, then select **Management** → **Integrations** → **Connection details**. Note that the Cloud ID value is in the format `deployment-name:hash`. Save this value to use it later.
+To find the [Cloud ID]([Cloud ID](/deploy-manage/deploy/elastic-cloud/find-cloud-id.md)) of your deployment, go to the {{kib}} main menu, then select **Management** → **Integrations** → **Connection details**. Note that the Cloud ID value is in the format `deployment-name:hash`. Save this value to use it later.
 
 ### Basic authentication
 
 To authenticate and send data to {{ech}}, you can use the username and password you saved when you created your deployment. We use this method to set up the Filebeat connection in the [Configure Filebeat to access {{ech}}](#ec-configure-access) section.
 
 ### API key
 
-You can also generate an _API key_ through the {{ech}} console, and configure Filebeat to use the new key to connect securely to your deployment. API keys are the preferred method for connecting to production environments.
+You can also generate an [API key](/deploy-manage/api-keys.md) through the {{ech}} console, and configure Filebeat to use the new key to connect securely to your deployment. API keys are the preferred method for connecting to production environments.
 
 To create an API key for Filebeat:
 
@@ -206,6 +206,10 @@ cloud.auth: username:password <2>
 1. Uncomment the `cloud.id` line, and add the deployment’s Cloud ID as the key's value. Note that the `cloud.id` value is in the format `deployment-name:hash`. Find your Cloud ID by going to the {{kib}} main menu, and selecting **Management** → **Integrations** → **Connection details**.
 2. Uncomment the `cloud.auth` line, and add the username and password for your deployment in the format `username:password`. For example, `cloud.auth: elastic:57ugj782kvkwmSKg8uVe`.
 
+::::{note}
+As an alternative to configuring the connection using [cloud.id and cloud.auth](beats://reference/beats/filebeat/configure-cloud-id.md), you can specify the {{es}} URL and authentication details directly in the [{{es}} output](beats://reference/beats/filebeat/elasticsearch-output.md). This is useful when connecting to a different deployment type, such as a self-managed cluster.
+::::
+
 #### Configure an API key [ec-configure-api-key]
 
 To use an _API key_ to authenticate, leave the comment on the `cloud.auth` line as Filebeat will use an API key instead of the deployment credentials to authenticate.