Skip to content

[KTLO(AWS revamping)]: Independent procedures for metrics integration types #21679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Sep 19, 2025
Merged

[KTLO(AWS revamping)]: Independent procedures for metrics integration types #21679

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ae3af15
[KTLO(AWS revamping)]: Independent procedures for integration types
sujitnewrelic Sep 11, 2025
21b4082
feedback
sujitnewrelic Sep 18, 2025
3fa93d3
feedback incorporation from SME
sujitnewrelic Sep 19, 2025
c9e8657
added related topics.
sujitnewrelic Sep 19, 2025
576f0c4
removing orphans
sujitnewrelic Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 58 additions & 0 deletions .../docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: Integrate manually from AWS console
tags:
- Integrate manually
- Manual integration
- AWS metric integration
- Amazon integrations
- AWS integrations
translate:
metaDescription: Integrate New Relic with AWS services manually from the AWS console.
redirects:

freshnessValidatedDate: never
---

For seamless integration of your AWS account with New Relic, [Integration via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) is the most recommended approach. If you cannot use CloudFormation templates and do not prefer to use Terraform, refer to the following procedure to integrate manually from the AWS console.

## Prerequisites [#prerequisites]

Before you begin integrating your AWS account with New Relic, ensure that you meet the following prerequisites:
* **A New Relic [Ingest - license key and a User key](https://one.newrelic.com/api-keys)**: You'll need these keys to connect your AWS services to your New Relic account.
* **[Permissions](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** to deploy new AWS resources and **[IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: You’ll need this permission for your AWS account.
* **[Permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** for cloud integrations: You’ll need these permissions for your New Relic account.

## Integration steps [#integration-steps]

To integrate your AWS account with New Relic, follow these steps:

1. Navigate to [<DNT>**Infrastructure > AWS**</DNT>](https://one.newrelic.com/infra/infrastructure/cloud-aws).
2. Select the correct account.
3. Click <DNT>**Set up integration**</DNT>.
4. Follow the instructions on each screen, and fill in the fields that apply to you. For this integration, choose the following options in the given screens:

1. <DNT>**Choose Data type(s)**</DNT>: <DNT>Metrics</DNT>
2. <DNT>**Choose a setup method**</DNT>: <DNT>Manually integrate your AWS account</DNT>

5. On the <DNT>**Select services**</DNT> screen, if needed, use the <DNT>**Show resources not supported by CloudWatch Metric Streams**</DNT> toggle, select the services you want to monitor, and then continue.

7. On the <DNT>**Choose data integration type**</DNT> screen, choose from the following integration options:
* **Real-time AWS monitoring (Recommended)**: This option is for the services that support CloudWatch Metric Streams.
* **API Polling**: This option is suitable for services not supported by CloudWatch Metric Streams.

8. From the <DNT>**Create role**</DNT> page to <DNT>**Configure budgets policy**</DNT> page, follow the on-screen instructions and perform the steps in AWS console.
9. After creating the policy in AWS console, switch to the New Relic platform and continue with the guided integration till you see your AWS data in New Relic.

## Related topics [#related-topics]

<DocTiles>
<DocTile title="Collect data from multiple AWS accounts" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account/" >Learn how to collect data from multiple AWS accounts.</DocTile>
<DocTile title="AWS integrations metrics" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-integrations-metrics/" >Explore and use metrics from CloudWatch Metric Stream.</DocTile>
<DocTile title="AWS integrations via CloudFormation and CWMS" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms" >Integrate AWS services with New Relic using CloudFormation and CloudWatch Metric Streams.</DocTile>
<DocTile title="AWS integrations via CloudFormation and API Polling" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling" >Integrate AWS services with New Relic using CloudFormation and API Polling.</DocTile>
<DocTile title="AWS integrations via Terraform" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform" >Integrate AWS services with New Relic using Terraform.</DocTile>
</DocTiles>




108 changes: 108 additions & 0 deletions ...n-integrations/aws-integration-for-metrics/migrate-from-api-polling-to-cwms.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,108 @@
---
title: Migrate from API Polling to CloudWatch Metric Streams
tags:
- API polling to CWMS migration
translate:
metaDescription: Migrate your New Relic and AWS services integration type from API Polling to CloudWatch Metric Streams.
redirects:

freshnessValidatedDate: never
---

For seamless integration of your AWS account with New Relic, [Integration via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) is the most recommended approach. However, if you have already integrated your AWS account with New Relic using API Polling, refer to the following procedure to migrate from API Polling to CloudWatch Metric Streams.

## Prerequisites [#prerequisites]

Before you begin integrating your AWS account with New Relic, ensure that you meet the following prerequisites:
* **A New Relic [Ingest - license key and a User key](https://one.newrelic.com/api-keys)**: You'll need these keys to connect your AWS services to your New Relic account.
* **[Permissions](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html)** to deploy new AWS resources and **[IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**: You’ll need this permission for your AWS account.
* **[Permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** for cloud integrations: You’ll need these permissions for your New Relic account.
* 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.

<Steps>
<Step>
## Migrate to the CloudWatch Metric Streams integration [#migrate]

You can migrate from API polling by creating a CloudFormation template, or by re-adding your AWS account and following our in-app guided install procedures. We recommend that you use the CloudFormation template method, as it's the most efficient way to migrate. These integrations are not supported by CloudWatch Metric Streams and can't be migrated to our integration:

* AWS CloudTrail
* AWS Health
* AWS Trusted Advisor
* AWS X-Ray

If you use these integrations, you still need to use the API polling method.

<CollapserGroup>
<Collapser
id="with-template"
title="Migrate with CloudFormation template (Recommended)"
>

The CloudFormation template allows you to update a template with preconfigured namespaces based on your polling configuration.

1. Go to **[one.newrelic.com > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**, then click **<DNT>Migrate to CloudWatch Metric stream</DNT>**.
1. Follow the procedures. You'll download the template, then replicate the namespaces from API polling. Be sure to add your account details to the downloaded template.
1. From AWS Console, go to <DNT>**Cloud Formation > Create Stack > Upload a template file**</DNT>. Upload your updated CloudFormation template.

</Collapser>
<Collapser
id="without-template"
title="Migrate without CloudFormation template"
>

If you don't want to use the CloudFormation method, you need to re-add your AWS account even if you've already linked your AWS account with polling integrations. These procedures may have you leave this doc, but remember to return to disable your polling integrations.

1. Go to <DNT>**[one.newrelic.com > All capabilities >Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**</DNT>, then click <DNT>**Add AWS account**</DNT>. Choose your method.
1. Follow the AWS Console steps from the [AWS Console flow](/install/aws-cloudwatch/?task=console) in this doc.
1. [Disable all unnecessary polling integrations](/docs/infrastructure/amazon-integrations/connect/uninstall-aws/) in the previous AWS provider account.

When disabling, keep in mind that [some integrations are not supported by CloudWatch Metric Streams](/docs/infrastructure/amazon-integrations/connect/connect-aws-new-relic-infrastructure-monitoring/).
</Collapser>
</CollapserGroup>

Our CloudWatch 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 API polling method, on the other hand, pushes metrics based on [events](/docs/data-apis/understand-data/new-relic-data-types/#events-new-relic).

* To assist in the transition, we provide a shimming mechanism that transparently lets you write queries in any format. These queries are processed as expected based on the source that's available, either from events to metrics or metrics to events.
* We recommend reviewing [some limitations](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql/#known-limitations) about the shimming mechanism that lets you use event-based queries with the CloudWatch Metric Stream integration.

After migrating, some of New Relic features that depend on your API polling data may behave differently:

* <DNT>**Dashboards**</DNT>: Custom dashboards that use poll-based AWS integration events will still work as expected.
* <DNT>**Alerts**</DNT>: Alert conditions that use poll-based AWS events will still work. We recommend adapting those to the dimensional metric format that uses NRQL as source.
* <DNT>**Entities**</DNT>: Your list of monitored entities might show duplicated entities for up to 24 hours.
* <DNT>**Attributes**</DNT>: 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.
</Step>

<Step>
## Validate that your data [#validate-data]

To confirm you're receiving data from the Metric Streams, follow these steps:

1. Go to <DNT>**[one.newrelic.com > All capabilities > Infrastructure > AWS](https://one.newrelic.com/infra/infrastructure/cloud-aws)**</DNT>. Search for the AWS account you've connected to New Relic. <DNT>**Stream**</DNT> accounts.
2. Check the account status dashboard and confirm that New Relic receives the metric data. This may include errors and number of namespaces and metrics ingested.
3. Explore your data by writing queries for specific sets of metrics.

It may take a few minutes for New Relic to detect new resources and synthesize them as entities.

<Callout variant="tip">
AWS CloudWatch metrics for global services, such AWS Billing, are only available in the <DNT>**us-east-1**</DNT> region. Make sure there's an active CloudWatch metric stream configured in that region.
</Callout>
</Step>

</Steps>

## Related topics [#related-topics]

<DocTiles>
<DocTile title="Collect data from multiple AWS accounts" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account/" >Learn how to collect data from multiple AWS accounts.</DocTile>
<DocTile title="AWS integrations metrics" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-integrations-metrics/" >Explore and use metrics from CloudWatch Metric Stream.</DocTile>
<DocTile title="AWS integrations via CloudFormation and CWMS" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms" >Integrate AWS services with New Relic using CloudFormation and CloudWatch Metric Streams.</DocTile>
<DocTile title="AWS integrations via CloudFormation and API Polling" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling" >Integrate AWS services with New Relic using CloudFormation and API Polling.</DocTile>
<DocTile title="AWS integrations via Terraform" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform" >Integrate AWS services with New Relic using Terraform.</DocTile>
<DocTile title="Manual integrations from AWS console" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual" >Manually integrate AWS services with New Relic from AWS console.</DocTile>
</DocTiles>




53 changes: 53 additions & 0 deletions ...cs/infrastructure/amazon-integrations/aws-integration-for-metrics/terraform.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
title: Integrate with Terraform
tags:
- Integrate with Terraform
- AWS metric integration
- Amazon integrations
- AWS integrations
translate:
metaDescription: Integrate New Relic with AWS services using Terraform.
redirects:

freshnessValidatedDate: never
---

For seamless integration of your AWS account with New Relic, [Integration via CloudFormation and CloudWatch metric stream](/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation) is the most recommended approach. If you are already managing your AWS accounts and services using Terraform, you might prefer the following integration method because New Relic offers an AWS Cloud Integrations module that simplifies setting up the integration.

## Prerequisites [#prerequisites]

Before you begin integrating your AWS account with New Relic, ensure that you meet the following prerequisites:
* **[Permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure)** for cloud integrations: You’ll need these permissions for your New Relic account.
* The New Relic account ID and region that you want to link to AWS.

## Integration steps [#integration-steps]

To integrate your AWS account with New Relic, follow these steps:

1. Navigate to [<DNT>**Infrastructure > AWS**</DNT>](https://one.newrelic.com/infra/infrastructure/cloud-aws).
2. Select the correct account.
3. Click <DNT>**Set up integration**</DNT>.
4. Follow the instructions on each screen, and fill in the fields that apply to you. For this integration, choose the following options in the given screens:

1. <DNT>**Choose Data type(s)**</DNT>: <DNT>Metrics</DNT>
2. <DNT>**Choose a setup method**</DNT>: <DNT>Automate with Terraform</DNT>

5. On the <DNT>**Select services**</DNT> screen, if needed, use the <DNT>**Show resources not supported by CloudWatch Metric Streams**</DNT> toggle, select the services you want to monitor, and then continue.

7. From the <DNT>**Terraform**</DNT> screen, open the documentation that guides how to connect your New Relic account with the Terraform provider account.

8. After a successful integration, you can see your AWS data in New Relic.

## Related topics [#related-topics]

<DocTiles>
<DocTile title="Collect data from multiple AWS accounts" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-multi-account/" >Learn how to collect data from multiple AWS accounts.</DocTile>
<DocTile title="AWS integrations metrics" path="/docs/infrastructure/amazon-integrations/manage-aws-data/aws-integrations-metrics/" >Explore and use metrics from CloudWatch Metric Stream.</DocTile>
<DocTile title="AWS integrations via CloudFormation and CWMS" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-cwms" >Integrate AWS services with New Relic using CloudFormation and CloudWatch Metric Streams.</DocTile>
<DocTile title="AWS integrations via CloudFormation and API Polling" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/via-cloudformation-and-api-polling" >Integrate AWS services with New Relic using CloudFormation and API Polling.</DocTile>
<DocTile title="Manual integrations from AWS console" path="/docs/infrastructure/amazon-integrations/aws-integration-for-metrics/manual" >Manually integrate AWS services with New Relic from AWS console.</DocTile>
</DocTiles>




Loading
Loading