Merge pull request #4069 from mkrichevsky/patch-4

update lambda cloud monitoring documentation

src/content/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration.mdx

@@ -25,14 +25,14 @@ Lambda functions are pieces of custom code that run when a certain event happens
 
 New Relic's AWS Lambda integration reports data such as invocation counts, error counts, function timers, and other [metrics](#metrics) and [inventory data](#inventory). You can view your Lambda data in pre-built dashboards and also create custom queries and charts in [New Relic One](/docs/infrastructure/integrations-getting-started/getting-started/use-integration-data-new-relic-insights).
 
-<Callout variant="important">
-  New Relic offers a [Lambda monitoring feature that's more in-depth than this integration](/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/introduction-new-relic-monitoring-aws-lambda).
-</Callout>
-
 ## Activate integration [#activate]
 
 To enable this integration follow standard procedures to [Connect AWS services to New Relic](/docs/infrastructure/infrastructure-integrations/getting-started/connect-aws-integrations-infrastructure).
 
+<Callout variant="important">
+  If you use custom keys to encrypt environment variables, you might start seeing KMS decryption errors in Cloudtrail console. This is because the API that is used to fetch lambdas always tries to retrieve environment variables information as part of its response. New Relic doesn't receive or store this information.
+</Callout>
+
 ## Configuration and polling [#polling]
 
 You can change the polling frequency and filter data using [configuration options](/docs/integrations/new-relic-integrations/getting-started/configure-polling-frequency-data-collection-cloud-integrations).