feat(aws): added one more link to intro doc

newrelic · Sep 23, 2024 · 9ad81b3 · 9ad81b3
1 parent 3873c1a
commit 9ad81b3
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/...nfrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx b/...nfrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
@@ -103,7 +103,7 @@ Once installed and configured, you can access data from your AWS services direct
 
 ## Amazon CloudWatch Metric streams and API polling [#api-polling]
 
-We strongly recommend that you use the CloudWatch Metric Streams integration as it directly connects with the metric streams repository holding your AWS metric data. You may have a stack that requires instrumentation with our [API Polling integrations](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/), however. For example, these AWS services aren't currently supported by the CloudWatch Metric Streams integration:
+We strongly recommend that you use the [CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/connect/cloudwatch-metric-streams/aws-metric-stream-setup) as it directly connects with the metric streams repository holding your AWS metric data. You may have a stack that requires instrumentation with our [API Polling integrations](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/), however. For example, these AWS services aren't currently supported by the CloudWatch Metric Streams integration:
 
 * AWS CloudTrail
 * AWS Health
@@ -114,11 +114,11 @@ We strongly recommend that you use the CloudWatch Metric Streams integration as
 
 ## Integrations and AWS costs [#cloudwatch-billing]
 
-This section directs you to relevant AWS docs so you can understand how our integrations affect your AWS billing. 
+This section directs you to relevant AWS docs that explain how our integrations affect your AWS billing. 
 
 * The [AWS CloudWatch Pricing page](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html)defines AWS CloudWatch metric streams pricing based on the number of metric updates.
 * We sometimes use AWS Kinesis Data Firehose as the delivery method from AWS to New Relic, so we recommend reviewing the [AWS Firehose pricing page](https://aws.amazon.com/kinesis/data-firehose/pricing/).
-* When you optionally enable AWS Config to enrich CloudWatch metrics with resource metadata, you're charged based on the number of configuration items recorded. See the [AWS Config pricing page](https://aws.amazon.com/config/pricing/) for details.
+* When you enable AWS Config to enrich CloudWatch metrics with resource metadata, you're charged based on the number of configuration items recorded. See the [AWS Config pricing page](https://aws.amazon.com/config/pricing/) for details.
 * [AWS Resource Groups Tagging API](https://docs.aws.amazon.com/resourcegroupstagging/latest/APIReference/overview.html) enriches metrics with custom tags defined in the associated AWS resources. This affects both polling and metric streams.
 
 New Relic uses the Amazon CloudWatch API to obtain metrics from your AWS services when you use the API Polling integration instead of CloudWatch Metric Streams. Some situations may increase the number of calls to the CloudWatch API to exceed the <DNT>**1 million free**</DNT> limits granted by AWS and [increase your CloudWatch bill](/docs/infrastructure/amazon-integrations/troubleshooting/cloudwatch-billing-increase). This may happen when you: