Update note with link for context (#19397)

* Update note with link for context

* Apply suggestions from code review

content/en/logs/guide/send-aws-services-logs-with-the-datadog-lambda-function.md

@@ -69,7 +69,7 @@ Datadog can automatically configure triggers on the Datadog Forwarder Lambda fun
 | Redshift Logs                   | S3             |
 | S3 Access Logs                  | S3             |
 
-**Note**: `SubscriptionFilter` is not created automatically.
+**Note**: [Subscription filters][48] are not created automatically by the DatadogForwarder. Create them directly on a Log Group.
 
 1. If you haven't already, set up the [Datadog log collection AWS Lambda function][1].
 2. Ensure the policy of the IAM role used for [Datadog-AWS integration][43] has the following permissions. Information on how these permissions are used can be found in the descriptions below:
@@ -292,3 +292,4 @@ You can also exclude or send only those logs that match a specific pattern by us
 [45]: https://app.datadoghq.com/logs
 [46]: https://github.com/DataDog/datadog-serverless-functions/tree/master/aws/logs_monitoring#log-scrubbing-optional
 [47]: https://github.com/DataDog/datadog-serverless-functions/tree/master/aws/logs_monitoring#log-filtering-optional
+[48]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/SubscriptionFilters