Update no-data-metric-streams.mdx

src/content/docs/infrastructure/amazon-integrations/troubleshooting/no-data-metric-streams.mdx

@@ -23,7 +23,7 @@ If you are not seeing data in New Relic once the AWS CloudWatch Metric Stream ha
 
 1. Check that the Metric Stream is in a state of `Running` via the AWS console or API. Please refer to [AWS Troubleshooting docs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-metric-streams-troubleshoot.html) for additional details.
 2. Check the Metric Stream metrics under `AWS/CloudWatch/MetricStreams` namespace. You will see a count of metric updates and errors per Metric Streams. This indicates that the Metric Stream is successfully emitting data.
-3. If you see errors, confirm the IAM role specified in the Metric Streams configuration grants the CloudWatch service principal permissions to write.
+3. If you see errors, confirm the IAM role specified in the Metric Streams configuration grants the CloudWatch service principal permissions to write and targets the intended Firehose resource.
 4. Check the Monitoring tab of the Kinesis Data Firehose in the Kinesis console to see if the Firehose is successfully receiving data.
 5. You can enable CloudWatch error logging on your Kinesis Data Firehose to get more detailed information for debugging issues. Refer to Amazon Kinesis Data Firehose official documentation for more details.
 6. Confirm that you have configured your Kinesis Data Firehose with the correct destination details: