diff --git a/src/content/docs/infrastructure/amazon-integrations/get-started/aws-metric-stream-setup.mdx b/src/content/docs/infrastructure/amazon-integrations/get-started/aws-metric-stream-setup.mdx deleted file mode 100644 index b00f4532978..00000000000 --- a/src/content/docs/infrastructure/amazon-integrations/get-started/aws-metric-stream-setup.mdx +++ /dev/null @@ -1,269 +0,0 @@ ---- -title: Set up the Amazon CloudWatch Metric Streams integration -tags: - - Integrations - - Amazon integrations - - AWS integrations list -metaDescription: Learn how to gather all AWS metrics and custom namespaces to send them to New Relic. -redirects: - - /docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup - - /docs/infrastructure/amazon-integrations/connect/cloudwatch-metric-streams/aws-metric-stream-setup -freshnessValidatedDate: never ---- - -Amazon CloudWatch Metric Streams is an AWS service that lets customers create a real-time stream of metrics to a destination of their choice. You can set up a metric streams through this service, letting you view your AWS data in the New Relic platform. The AWS CloudWatch Metric Streams integration is our recommended solution for monitoring your AWS stack. - -## Collect data with Amazon CloudWatch Metric Streams [#collect-aws-metric-streams] - -This doc walks you through the three different methods to direct AWS metrics to New Relic: - - * Create a metric stream and direct AWS metrics with a CloudFormation template - * Direct your AWS metrics with AWS Console, API, or calls - * Migrate from API polling to the CloudWatch Metric Streams integration - -To stream CloudWatch metrics to New Relic: - -1. Check the [minimal permissions and mapping instructions](#permissions). -2. Create Kinesis Data Firehose and point it to New Relic. -3. Next, create a CloudWatch Metric Stream to send metrics to that Firehose you've just created. -4. Follow the [guided](#setup-cloudformation) or [manual](#manual-setup) setup instructions. -5. Validate [data reception](#validate-data). - -If applicable, read our documentation about [migrating from AWS polling integrations](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream#migrating-from-poll-integrations). - - - You can use Terraform to automate the process of enabling cloud integrations. Read how in the [Terraform official documentation site](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/cloud_integrations_guide). - - - -## New Relic and AWS accounts and regions mapping [#map-accounts-regions] - -* If you manage multiple AWS accounts, then each account needs to be connected to New Relic. -* If you manage multiple regions within those accounts, then each region needs to be configured with a different Kinesis Data Firehose pointing to New Relic. -* You will typically map one or many AWS accounts to a single New Relic account. - -## Guided setup using CloudFormation [#setup-cloudformation] - -First, you need to link each of your AWS accounts with your New Relic account. To do so, use either of these options: - -* Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**, click on **Add an AWS account**, then on **Use metric streams**, and follow the steps. -* [Automate this step with NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial/#link-aws-cloudwatch). - -Next, set up the metric stream using the [CloudFormation template](https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/MetricStreams_CloudFormation.yml&stackName=NewRelic-Metric-Stream¶m_NewRelicDatacenter=US) we provide in the last step of our UI. This template is provided as a base to set up the integration on a single region. You can customize and extend it to meet your requirements. - -### CloudFormation Template Parameters - -This table outlines the various parameters required for the CloudFormation template. Since the template will create new resources in your AWS account, we don't providing names of existing AWS resources here. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Name - - Description - - Constraints -
- New Relic Ingest License Key - - The associated with the account you wish to export metrics to. - - 40-character hexadecimal string -
- New Relic Datacenter - - Identification of the New Relic data center your metrics are exported to. (EU data center accounts have license keys prefixed with `eu0x`) - - Allowed values: `US`, `EU` -
- CloudWatch Metric Stream name - - Name of new CloudWatch Metric Stream (must be unique per AWS account in the same AWS Region) - - Must only container letters (uppercase and lowercase), numbers, and characters '\_', and '-' with max length of 255 total characters -
- Kinesis Data Firehose name - - Name of new Kinesis Firehose Delivery Stream (must be unique per AWS account in the same AWS Region) - - Must only container letters (uppercase and lowercase), numbers, and characters '.', '\_', and '-' with max length of 64 total characters -
- Firehose S3 backup bucket name - - Name of new S3 Bucket Destination for failed events (must be globally unique across all AWS accounts in all AWS Regions within a partition) - - Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) -
- Enrich metrics with resource metadata from AWS Config - - Enable and configure AWS Config to track resource changes. This allows you a complete monitoring New Relic experience. - - Allowed values: `true`, `false` -
- Config S3 backup bucket name - - Name of new S3 Bucket Destination for delivery channel configuration (must be globally unique across all AWS accounts in all AWS Regions within a partition) - - Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) -
- - - The provided CloudFormation template doesn't include any inclusion nor exclusion namespace filter in CloudWatch metric streams. Consider adapting the base template based on your business requirements. - - -## Manual setup using AWS Console, API, or calls [#manual-setup] - -1. **Create a Kinesis Data Firehose Delivery Stream** and configure the following destination parameters: - - * Source: Direct PUT or other sources - * Data transformation: Disabled - * Record format conversion: Disabled - * Destination: New Relic - * Ensure the following settings are defined: - * New Relic configuration (Destination Settings) - * HTTP endpoint URL - US Datacenter: `https://aws-api.newrelic.com/cloudwatch-metrics/v1` - * HTTP endpoint URL - EU Datacenter: `https://aws-api.eu01.nr-data.net/cloudwatch-metrics/v1` - * API key: Enter your - * Content encoding: `GZIP` - * Retry duration: `60` - * S3 backup mode: Failed data only - * S3 bucket: select a bucket or create a new one to store metrics that failed to be sent. - * New Relic buffer conditions - * Buffer size: `1 MB` - * Buffer interval: `60 (seconds)` - * Permissions IAM role: - * Create or update IAM role - -2. **Create the metric stream**. - - * Go to **CloudWatch service** in your AWS console and select the **Streams** option under the **Metrics** menu. - * Click **Create metric stream**. - * Determine the right configuration based on your use cases: - * Use inclusion and exclusion filters to select which services should push metrics to New Relic. - * Select your Kinesis Data Firehose. - * Define a meaningful name for the stream (for example, `newrelic-metric-stream)`. - * Change default output format to `Open Telemetry 0.7`. (JSON is not supported.) - * Confirm the creation of the metric stream. - - Alternatively, you can find instructions on the AWS documentation to create the CloudWatch metric stream using a CloudFormation template, API, or the CLI. - -3. **Add the new AWS account** in the **Metric streams** mode in the New Relic UI. - Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**, click on **Add an AWS account**, then on **Use metric streams**, and follow the steps. - -## Validate your data is received correctly [#validate-data] - - - - AWS CloudWatch metrics for global services, such AWS Billing, are only availble in the **us-east-1** region. Make sure there's an active CloudWatch metric stream configured in that region. - - -## Migrate to Metric Streams [#migrate] - -We recommend that existing customers migrate from API polling to Metric Streams using a CloudFormation template by following the instructions below. - - - - 1. Replicate the namespaces from polling into metric streams by going to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS > Migrate to AWS Cloudwatch metric streams**, and then configuring your AWS Metric Streams account. - 2. Download the customized CloudFormation template under the **Configure metric streams** step. This template contains the preconfigured namespaces that are based on your existing polling configuration. - 3. Add your account details to the downloaded template. - 4. In the AWS Console, upload your CloudFormation template by going to **Cloud Formation > Create Stack > Upload a template file**. - - - - 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS > Add an AWS account**, then add your AWS account. This step is required even if you've already linked your AWS account with polling integrations. - 2. Enable AWS CloudWatch Metric Stream and the AWS Kinesis Data Firehose in the final step of the **Add an AWS account** process. This pushes metrics to New Relic. AWS CloudWatch requires one stream per region, so repeat this step for any additional AWS regions you want to monitor. - 3. Ensure metrics are received from all connected regions and namespaces. This may take several minutes. - 4. Disable all unnecessary polling integrations in the previous AWS provider account. Remember that [some integrations still need to be enabled](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream#integrations-not-replaced-streams) because they aren't fully replaced by Metric Streams. - - - -### Query, dashboard, and alert considerations [#considerations] - -Our AWS Metric Streams integration uses the Metric API to push metrics in the [dimensional metric](/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics) format. - -Our poll-based AWS integration pushes metrics based on [events](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic) (for example, the `ComputeSample` event), and will be migrated to dimensional metrics in the future. - -To assist in this transition, we provide a mechanism (known as shimming) that transparently lets you write queries in any format. Then these queries are processed as expected based on the source that's available (metrics or events). This mechanism works both ways, from events to metrics, and vice versa. - - - Learn more about [the limitations](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations) of the query mechanism that allows customers to use event-based queries (samples) with the AWS CloudWatch Metric Stream integration (dimensional metric format). - - -Please consider the following when migrating from our poll-based integrations: - -* **Dashboards**: Custom that use poll-based AWS integration events will still work as expected. -* **Alerts**: Alert conditions that use poll-based AWS events will still work. We recommend adapting those to the dimensional metric format (using NRQL as source). -* **Entities**: Your list of monitored entities might show duplicated entities for up to 24 hours. -* **Attributes**: Poll-based AWS integrations prefix collected resource tags with `label.`, while the AWS CloudWatch Metric Streams integration prefixes collected resource tags with `tags.`. If both integrations are enabled for the same AWS account, resource tags will appear under both prefixes when using the Event format. diff --git a/src/install/aws-cloudwatch/appInfo.mdx b/src/install/aws-cloudwatch/appInfo.mdx index 79bcb52e2e0..c41bf811853 100644 --- a/src/install/aws-cloudwatch/appInfo.mdx +++ b/src/install/aws-cloudwatch/appInfo.mdx @@ -1,4 +1,4 @@ --- componentType: appInfoConfig -headingText: Choose how you want to set up the CloudWatch Metric Streams integration +headingText: Choose how to set up the CloudWatch Metric Streams integration --- diff --git a/src/install/aws-cloudwatch/cloudwatch-path/cloudformation.mdx b/src/install/aws-cloudwatch/cloudwatch-path/cloudformation.mdx index e040daf8e41..46341c2c97a 100644 --- a/src/install/aws-cloudwatch/cloudwatch-path/cloudformation.mdx +++ b/src/install/aws-cloudwatch/cloudwatch-path/cloudformation.mdx @@ -1,138 +1,130 @@ --- componentType: default optiontype: task -headingText: UPDATE +headingText: Integrate with CloudFormation --- -First, you need to link each of your AWS accounts with your New Relic account. To do so, use either of these options: - -* Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**, click on **Add an AWS account**, then on **Use metric streams**, and follow the steps. -* [Automate this step with NerdGraph](/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial/#link-aws-cloudwatch). - -Next, set up the metric stream using the [CloudFormation template](https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/MetricStreams_CloudFormation.yml&stackName=NewRelic-Metric-Stream¶m_NewRelicDatacenter=US) we provide in the last step of our UI. This template is provided as a base to set up the integration on a single region. You can customize and extend it to meet your requirements. - -### CloudFormation Template Parameters - -This table outlines the various parameters required for the CloudFormation template. Since the template will create new resources in your AWS account, we don't providing names of existing AWS resources here. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Name - - Description - - Constraints -
- New Relic Ingest License Key - - The associated with the account you wish to export metrics to. - - 40-character hexadecimal string -
- New Relic Datacenter - - Identification of the New Relic data center your metrics are exported to. (EU data center accounts have license keys prefixed with `eu0x`) - - Allowed values: `US`, `EU` -
- CloudWatch Metric Stream name - - Name of new CloudWatch Metric Stream (must be unique per AWS account in the same AWS Region) - - Must only container letters (uppercase and lowercase), numbers, and characters '\_', and '-' with max length of 255 total characters -
- Kinesis Data Firehose name - - Name of new Kinesis Firehose Delivery Stream (must be unique per AWS account in the same AWS Region) - - Must only container letters (uppercase and lowercase), numbers, and characters '.', '\_', and '-' with max length of 64 total characters -
- Firehose S3 backup bucket name - - Name of new S3 Bucket Destination for failed events (must be globally unique across all AWS accounts in all AWS Regions within a partition) - - Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) -
- Enrich metrics with resource metadata from AWS Config - - Enable and configure AWS Config to track resource changes. This allows you a complete monitoring New Relic experience. - - Allowed values: `true`, `false` -
- Config S3 backup bucket name - - Name of new S3 Bucket Destination for delivery channel configuration (must be globally unique across all AWS accounts in all AWS Regions within a partition) - - Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) -
- - - The provided CloudFormation template doesn't include any inclusion nor exclusion namespace filter in CloudWatch metric streams. Consider adapting the base template based on your business requirements. - +You can integrate your AWS account with New Relic using CloudFormation, which uses templates or stacks as blueprints for building AWS resources. This step directs you to our in-app guided install that walks you through setting up a CloudFormation template. + +1. Go to **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/marketplace/install-data-source?&begin=1729543416051&end=1729545216051&state=82dc8d6d-8fff-45b5-e43c-15847ac8b090)**, then click **Automate AWS with CloudFormation**. +1. Customize or extend the CloudFormation template parameters so they meet your requirements. This table provides some parameters to get you started: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Name + + Description + + Constraints +
+ New Relic Ingest License Key + + The associated with the account you wish to export metrics to. + + 40-character hexadecimal string +
+ New Relic Datacenter + + Identification of the New Relic data center your metrics are exported to. (EU data center accounts have license keys prefixed with `eu0x`) + + Allowed values: `US`, `EU` +
+ CloudWatch Metric Stream name + + Name of new CloudWatch Metric Stream (must be unique per AWS account in the same AWS Region) + + Must only container letters (uppercase and lowercase), numbers, and characters '\_', and '-' with max length of 255 total characters +
+ Kinesis Data Firehose name + + Name of new Kinesis Firehose Delivery Stream (must be unique per AWS account in the same AWS Region) + + Must only container letters (uppercase and lowercase), numbers, and characters '.', '\_', and '-' with max length of 64 total characters +
+ Firehose S3 backup bucket name + + Name of new S3 Bucket Destination for failed events (must be globally unique across all AWS accounts in all AWS Regions within a partition) + + Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) +
+ Enrich metrics with resource metadata from AWS Config + + Enable and configure AWS Config to track resource changes. This allows you a complete monitoring New Relic experience. + + Allowed values: `true`, `false` +
+ Config S3 backup bucket name + + Name of new S3 Bucket Destination for delivery channel configuration (must be globally unique across all AWS accounts in all AWS Regions within a partition) + + Must adhere to the [S3 bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) +
+ +Since the template will create new resources in your AWS account, we don't providing names of existing AWS resources here. diff --git a/src/install/aws-cloudwatch/create-metric-stream.mdx b/src/install/aws-cloudwatch/create-metric-stream.mdx deleted file mode 100644 index 8530b84ee50..00000000000 --- a/src/install/aws-cloudwatch/create-metric-stream.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -componentType: default -headingText: Choose your framework ---- - -To stream CloudWatch metrics to New Relic: - -Check the minimal permissions and mapping instructions. -Create Kinesis Data Firehose and point it to New Relic. -Next, create a CloudWatch Metric Stream to send metrics to that Firehose you've just created. -Follow the guided or manual setup instructions. -Validate data reception. -If applicable, read our documentation about migrating from AWS polling integrations. - diff --git a/src/install/aws-cloudwatch/default.mdx b/src/install/aws-cloudwatch/default.mdx index 7b433df24e3..47ce6aa59ce 100644 --- a/src/install/aws-cloudwatch/default.mdx +++ b/src/install/aws-cloudwatch/default.mdx @@ -1,6 +1,10 @@ --- componentType: default -headingText: Set up the AWS CloudWatch Metric Streams integration +headingText: Configure Firehose and CloudWatch Metric Streams --- -filler text for how this will swap out or whatever \ No newline at end of file +Once your permissions are set, you can set up the CloudWatch Metric Streams integration. We have a few different methods depending on your preference: + +* You can follow our in-app guided install, which directs you to the New Relic platform where you'll follow a guided install to create Cloudformation template for CloudWatch Metric Streams. You may want to return to this doc to review the CloudFormation template parameters. +* You can follow some manual procedures that lets you use AWS Console or APIs to create the resources you'll need yourself. +* If you're currently forwarding your data with API polling, we strongly recommend you work through the migration procedures in this doc. \ No newline at end of file diff --git a/src/install/aws-cloudwatch/firehose-permissions.mdx b/src/install/aws-cloudwatch/firehose-permissions.mdx deleted file mode 100644 index c8200eff702..00000000000 --- a/src/install/aws-cloudwatch/firehose-permissions.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -componentType: default -headingText: Confirm your permissions, then set up a metric stream ---- - -Minimal permissions and mapping instructions -To enrich CloudWatch metrics with additional service metadata and custom tags, any AWS role configured in New Relic must be granted the following minimal permissions: - -```json -config:BatchGetResourceConfig -config:ListDiscoveredResources -elasticache:DescribeCacheClusters -tag:GetResources -``` - -The New Relic UI currently recommends the ReadOnlyAccess policy over these individual items so that New Relic has proper permissions to collect service data that's not available in AWS CloudWatch Metric Streams. - -New Relic and AWS accounts and regions mapping -If you manage multiple AWS accounts, then each account needs to be connected to New Relic. -If you manage multiple regions within those accounts, then each region needs to be configured with a different Kinesis Data Firehose pointing to New Relic. -You will typically map one or many AWS accounts to a single New Relic account. diff --git a/src/install/aws-cloudwatch/intro.mdx b/src/install/aws-cloudwatch/intro.mdx index d32b6cf6bcb..74893b24494 100644 --- a/src/install/aws-cloudwatch/intro.mdx +++ b/src/install/aws-cloudwatch/intro.mdx @@ -3,4 +3,14 @@ headingText: Before we start componentType: default --- -fdsgjnlkasdjfgsldf \ No newline at end of file +Amazon CloudWatch Metric Streams is an AWS service that creates a real-time stream of metrics to a destination of your choice. To stream your AWS data to New Relic, you can create a custom Firehose that forwards AWS metrics to our CloudWatch Metric Streams integration. This lets you view your AWS data in the New Relic platform. + +A screenshot that shows an example dashboard of AWS data in New Relic + +
+ Once you forward your AWS data to New Relic, you can view your data in a dashboard. +
diff --git a/src/install/aws-cloudwatch/permissions.mdx b/src/install/aws-cloudwatch/permissions.mdx new file mode 100644 index 00000000000..05385cce56e --- /dev/null +++ b/src/install/aws-cloudwatch/permissions.mdx @@ -0,0 +1,18 @@ +--- +componentType: default +headingText: Set minimum permissions +--- + +Before you access the integration, you need to set certain permissions so New Relic can access your AWS data. At minimum, you need to create a `ReadOnlyAccess` policy and apply these minimum permissions to the AWS roles associated with New Relic: + + ```json + config:BatchGetResourceConfig + config:ListDiscoveredResources + elasticache:DescribeCacheClusters + tag:GetResources + ``` + +Depending on your set up, your configuration requirements may vary: + + * For users who manage multiple AWS accounts, [connect each account to a single New Relic account](/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account). + * For users who manage multiple regions within those accounts, you need to create a separate Kinesis Data Firehose that points to New Relic for each region. \ No newline at end of file diff --git a/src/install/aws-cloudwatch/validate-data.mdx b/src/install/aws-cloudwatch/validate-data.mdx index 3eed4192f57..660433485c3 100644 --- a/src/install/aws-cloudwatch/validate-data.mdx +++ b/src/install/aws-cloudwatch/validate-data.mdx @@ -1,6 +1,6 @@ --- componentType: default -headingText: UPDATE +headingText: Validate that your data appears in New Relic --- To confirm you're receiving data from the Metric Streams, follow these steps: diff --git a/src/install/config/aws-cloudwatch.yaml b/src/install/config/aws-cloudwatch.yaml index c06b58fcd22..528240ecf22 100644 --- a/src/install/config/aws-cloudwatch.yaml +++ b/src/install/config/aws-cloudwatch.yaml @@ -19,8 +19,7 @@ appInfo: steps: - filePath: 'src/install/aws-cloudwatch/appInfo.mdx' - - filePath: 'src/install/aws-cloudwatch/firehose-permissions.mdx' - - filePath: 'src/install/aws-cloudwatch/create-metric-stream.mdx' + - filePath: 'src/install/aws-cloudwatch/permissions.mdx' - filePath: 'src/install/aws-cloudwatch/default.mdx' overrides: - filePath: 'src/install/aws-cloudwatch/cloudwatch-path/cloudformation.mdx' diff --git a/src/nav/infrastructure.yml b/src/nav/infrastructure.yml index 44627d7184a..90cde0f046a 100644 --- a/src/nav/infrastructure.yml +++ b/src/nav/infrastructure.yml @@ -424,10 +424,12 @@ pages: pages: - title: Introduction to AWS integrations path: /docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations - - title: Install AWS CloudWatch Metric Streams integration - path: /docs/infrastructure/amazon-integrations/get-started/aws-metric-stream-setup + - title: Integrate New Relic with CloudWatch Metric Streams + path: /install/aws-cloudwatch - title: Connect AWS to New Relic pages: + - title: Set up AWS API Polling + path: /docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring - title: Install infra agent on EC2 instances path: /docs/infrastructure/amazon-integrations/connect/ec2-quickstart - title: Install EKS add-on @@ -436,8 +438,6 @@ pages: path: /docs/infrastructure/amazon-integrations/connect/connect-aws-govcloud-new-relic - title: Connect AWS with Systems Manager Distributor path: /docs/infrastructure/amazon-integrations/aws-integrations-list/aws-sys-dist - - title: Set up AWS API Polling - path: /docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring - title: Uninstall AWS integrations path: /docs/infrastructure/amazon-integrations/connect/uninstall-aws - title: Configure and query your AWS data diff --git a/static/images/infrastructure_screenshot-full_CloudWatch-Metric-Streams.webp b/static/images/infrastructure_screenshot-full_CloudWatch-Metric-Streams.webp new file mode 100644 index 00000000000..8997306567b Binary files /dev/null and b/static/images/infrastructure_screenshot-full_CloudWatch-Metric-Streams.webp differ