For a seamless integration of your AWS account with New Relic, integration via CloudFormation and CloudWatch metric stream is the recommended approach. If you can't use CloudFormation templates and don't want to use Terraform, follow this procedure to integrate manually from the AWS console.
Tip
- If you manage multiple AWS accounts, connect each account to a single New Relic account.
- If you manage multiple regions within those accounts, create a separate Kinesis Data Firehose for each region.
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: You'll need these keys to connect your AWS services to your New Relic account.
- Permissions to deploy new AWS resources and IAM roles: You'll need this permission for your AWS account.
- Permissions for cloud integrations: You'll need these permissions for your New Relic account.
Create a Kinesis Data Firehose delivery stream
In the AWS console, set the following destination parameters for the delivery stream:
- Source: Direct PUT or other sources
- Destination: New Relic
- Data transformation: Disabled
- Record format conversion: Disabled
- Ensure the following settings are defined:
- New Relic configuration (Destination Settings):
- HTTP endpoint URL:
- US Datacenter:
https://aws-api.newrelic.com/cloudwatch-metrics/v1 - EU Datacenter:
https://aws-api.eu01.nr-data.net/cloudwatch-metrics/v1 - JP Datacenter:
https://aws-api.jp.nr-data.net/cloudwatch-metrics/v1
- US Datacenter:
- API key: Enter your
- Content encoding:
GZIP - Retry duration:
60 - New Relic buffer conditions:
- Buffer size:
1 MB - Buffer interval:
60 (seconds)
- Buffer size:
- HTTP endpoint URL:
- S3 backup mode: Failed data only
- S3 backup bucket: Select a bucket or create a new one to store metrics that failed to be sent.
- Advanced settings:
- Service access: Provide permissions for IAM role:
Create or update IAM role
- Service access: Provide permissions for IAM role:
- New Relic configuration (Destination Settings):
Create a CloudWatch metric stream
- In the AWS console, go to CloudWatch service, select Streams under the Metrics menu, and click Create metric stream.
- To control which AWS services send metrics to New Relic, configure inclusion and exclusion filters.
- From the Firehose delivery stream list, select the stream you created, then enter a meaningful name for the metric stream, for example,
newrelic-metric-stream. - In the output format field, select
Open Telemetry 0.7orOpen Telemetry 1.0. JSON isn't supported.
Connect your AWS account to New Relic
In New Relic, go to Infrastructure > AWS.
Select the correct account.
Click Set up integration.
On each screen, fill in the fields that apply to you. For this integration, choose the following options:
- Choose Data type(s): Metrics
- Choose a setup method: Manually integrate your AWS account
On the Select services screen, toggle Show resources not supported by CloudWatch Metric Streams if needed, select the services you want to monitor, and continue.
On the Choose data integration type screen, choose from the following options:
- Real-time AWS monitoring (Recommended): This option is for services that support CloudWatch Metric Streams.
- API Polling: This option is for services not supported by CloudWatch Metric Streams.
From the Create role page to the Configure budgets policy page, follow the on-screen instructions and complete the steps in the AWS console.
Validate your data
To confirm you're receiving data from Metric Streams:
- In New Relic, go to one.newrelic.com > All capabilities > Infrastructure > AWS, search for your connected AWS account, and look for Stream accounts.
- In the account status dashboard, confirm that New Relic is receiving metric data, including errors and the number of namespaces and metrics ingested.
- To explore specific metrics, write queries for the sets of metrics you want to analyze.
It may take a few minutes for New Relic to detect new resources and synthesize them as entities.
Tip
AWS CloudWatch metrics for global services, such as AWS Billing, are only available in the us-east-1 region. Make sure there's an active CloudWatch metric stream configured in that region.
Related topics
Collect data from multiple AWS accounts
Learn how to collect data from multiple AWS accounts.
AWS integrations metrics
Explore and use metrics from CloudWatch Metric Stream.
AWS integrations via CloudFormation and CWMS
Integrate AWS services with New Relic using CloudFormation and CloudWatch Metric Streams.
AWS integrations via CloudFormation and API Polling
Integrate AWS services with New Relic using CloudFormation and API Polling.
AWS integrations via Terraform
Integrate AWS services with New Relic using Terraform.