• EnglishEspañol日本語한국어Português
  • Log inStart now

FedRAMP-compliant endpoints

New Relic is FedRAMP Authorized Moderate for accounts that meet specific criteria. As a cloud service provider, we are committed to ensuring our compliance with FedRAMP's requirements for the confidentiality, integrity, and availability of your data. Please ensure that you comply with the requirements for using our FedRAMP environment, then use our FedRAMP-compliant endpoints to get your data into New Relic via your agent configuration or API.

Customer FedRAMP obligations

New Relic customers must meet all of the following requirements for our FedRAMP environment:

  1. New Relic-approved customers: Our FedRAMP-Moderate authorized environment is only available for New Relic-approved customers. For more information, contact your New Relic account representative.
  2. Subscription level: Customer must have a current and valid subscription for our Enterprise edition with the Data Plus option, or have an alternative New Relic-approved subscription.
  3. Authorized New Relic endpoints: Customer must configure their applicable agents to send their data only to our FedRAMP-designated endpoints.
  4. Authorized services and features: Customer must use only FedRAMP audited and authorized New Relic services and features.

FedRAMP inheritance

A customer can have FedRAMP and non-FedRAMP enabled accounts as required by their business needs. To add accounts, talk to your New Relic account representative.

Note: If FedRAMP is enabled on a parent account (the recommended configuration), then all its child accounts are FedRAMP. In this configuration, newly created child accounts are FedRAMP by default. FedRAMP cannot be “removed” from child accounts when the parent is FedRAMP. This option ensures compliance by default.

Overview of FedRAMP-compliant endpoints

There are multiple ways to get data into New Relic, including:

This document provides information on FedRAMP-compliant endpoints in New Relic. For more information about our security accreditation for the Federal Risk and Authorization Management Program (FedRAMP), see our data encryption documentation. For further information on New Relic networks, domains, and ports, see our networking documentation.


If a service's endpoint is not listed in this document and the service is not found in our list of services not in scope, then the service's standard endpoint already meets FedRAMP compliance requirements as is, without the need for a distinct FedRAMP endpoint.

Agent and ingest API endpoints

To send FedRAMP-compliant data with our agents, integrations, and APIs, adjust their configuration settings to use the relevant FedRAMP endpoint. Below this table are some more details about implementation for specific New Relic solutions.


FedRAMP endpoint

Purpose and notes



AWS Metric Streams ingest



Browser ingest Recommended browser endpoint.



Ingest for AWS VPC Flow Logs and RDS Enhanced.



APM agent ingest



Infrastructure agent ingest



Event API ingest



Our Log API, used by various agents and integrations.


gov-metric-api.newrelic.com gov-metric-api.newrelic.com/prometheus/

Our Metric API for dimensional metrics, used by various agents and integrations.



Mobile agent ingest



Mobile agent crash report ingest


gov-otlp.nr-data.net:4318 gov-otlp.nr-data.net:4317 gov-otlp.nr-data.net:443

OpenTelemetry ingest. Configure using the quick start guide with your account license key in the api-key header.



Trace API ingest



IAST Validator Service URL
(Requires secure WebSocket connection)

APM agents

To ensure FedRAMP compliance, all APM agent configurations must report to gov-collector.newrelic.com rather than the default. Depending on the agent, you can either use code-based configuration or an environment variable to enable the FedRAMP-compliant endpoint.


Code or environment variable


In code:

app, err = newrelic.NewApplication(
newrelic.ConfigAppName("App Name"),
func(cfg *newrelic.Config) {
cfg.Host = "gov-collector.newrelic.com"

Environment variable: NEW_RELIC_HOST


In newrelic.yml:

common: &default_settings
host: gov-collector.newrelic.com

Or set a system property of:


Environment variable: NEW_RELIC_HOST


In your XML config next to the :

<service licenseKey="YOUR_LICENSE_KEY"

Environment variable: NEW_RELIC_HOST


In newrelic.js:

host: 'gov-collector.newrelic.com'

Environment variable: NEW_RELIC_HOST


In newrelic.ini:

newrelic.daemon.collector_host = gov-collector.newrelic.com

Environment variable: none


In newrelic.ini:

host = gov-collector.newrelic.com

Environment variable: NEW_RELIC_HOST


In newrelic.yml:

common: &default_settings
host: gov-collector.newrelic.com

Environment variable: NEW_RELIC_HOST

Elixir (open source agent)

In config.exs:

config :new_relic_agent,
host: "gov-collector.newrelic.com"

Environment variable: NEW_RELIC_HOST

Infrastructure monitoring

If you have infrastructure agent version 1.15.0 or higher, simply enable the FedRAMP configuration option. This enables FedRAMP compliancy for data reported by the infrastructure agent.

This also enables FedRAMP compliancy for any on-host integrations that work with the infrastructure agent to report data.

Browser monitoring agent

Browser monitoring agents will automatically update your account information to use the correct endpoints.

Mobile monitoring agents

To ensure FedRAMP compliance when using our mobile monitoring agents, all agent configurations must report to gov-mobile-collector.newrelic.com rather than the default. You must use code-based configuration. Environment variables are not available.

Framework-specific configurations:


Code or environment variable


In code:


Environment variable: none


In code:

[NewRelic startWithApplicationToken:@"{APP_TOKEN}"

Environment variable: none

Data-ingest APIs

Follow these instructions as applicable to set the FedRAMP endpoint for a specific API or the integration that uses the API.


To ensure FedRAMP compliance when using the OpenTelemetry API, only send data to https://gov-otlp.nr-data.net with the appropriate port chosen from the OTLP integration support matrix. See that page for more details on FedRAMP compliance with OTLP.


Do NOT send data to the US OTLP API endpoint of https://otlp.nr-data.net:4317.

Metric API

To ensure FedRAMP compliance when using the Metric API, do not send metric data to the default Metric API endpoint of https://metric-api.newrelic.com/metric/v1. Instead, send metric data to https://gov-metric-api.newrelic.com/metric/v1.

The Metric API can be used directly, but it's mainly used by various New Relic tools. Follow these instructions as applicable to edit the configuration for setting the FedRAMP endpoint.

Telemetry integrations for metric data

Here are instructions for our open source telemetry integrations that report metric data:

Open-source telemetry integration



Use the overrideUri configuration on GitHub.


Use the metric-ingest-url configuration. See the Kamon documentation to override endpoints.


Override the public String uri() method on your NewRelicRegistryConfig to return the new endpoint. See the example in GitHub.

Prometheus OpenMetrics

If you're using our nri-prometheus helm chart, you can change the endpoint in your values.yml file, like in this example on GitHub.

If you're using the nri-bundle chart, you need to nest this value under the nri-prometheus key to propagate it to the sub-chart.

Prometheus remote write integration

Replace https://metric-api.newrelic.com/prometheus/v1 with the FedRAMP-compliant endpoint https://gov-metric-api.newrelic.com/prometheus/v1 in the url configuration parameter in your Prometheus YML file.

Telemetry SDKs for metric data

Here are instructions for our Telemetry SDKs that report metric data:

Telemetry SDK for APM agents



Use the MetricsURLOverride configuration found on GitHub.


In the MetricBatchSender section, configure the endpoint. See the example on GitHub.


Use the MetricUrlOverride configuration found on GitHub.


Edit the METRIC_HOST = 'metric-api.newrelic.com' configuration found on GitHub.


Edit the HOST = "metric-api.newrelic.com" configuration found on GitHub.

Event API

To ensure FedRAMP compliance for the Event API, all traffic reporting to insights-collector.newrelic.com must instead report to gov-insights-collector.newrelic.com.

The Event API endpoint is configurable for the following Telemetry SDKs. The Telemetry SDKs are used by our open-source telemetry integrations.



Java Telemetry SDK

In code:

SenderConfiguration configuration = SenderConfiguration
EventBatchSender eventBatchSender = EventBatchSender.create(configuration);

Python Telemetry SDK

In code:

event_client = EventClient(host="gov-insights-collector.newrelic.com")

For more information, see our Telemetry API documentation in GitHub.


To ensure FedRAMP compliance for data sent via the Log API, the solution for almost all of our log forwarders is to replace the https://log-api.newrelic.com/log/v1 endpoint with https://gov-log-api.newrelic.com/log/v1. Or, to use the Log API directly, edit the Log API endpoint configuration.

Here are details on changing the endpoint for our log forwarders. If a log forwarder is not listed, FedRAMP endpoint configuration is not available.

Log forwarder


AWS Firelens

Add the endpoint property to the options field of the logConfiguration, similar to the EU account endpoint change shown in the Firelens endpoint configuration instructions.


Use our Fluentbit endpoint configuration found on GitHub.


Use our Fluentd endpoint instructions.

Infrastructure agent

See the FedRAMP configuration instructions for infrastructure monitoring.


Our Kubernetes integration logs are based on Fluentbit's output plugin. Use the Helm chart endpoint instructions found on GitHub.


Use our Logstash endpoint configuration.


For configuring syslog clients, see our documentation about TCP endpoint configuration.

Trace API

To ensure FedRAMP compliance for data sent via the Trace API (including telemetry integrations that use this API), replace the https://trace-api.newrelic.com/trace/v1 endpoint with https://gov-trace-api.newrelic.com/trace/v1.

Notes about FedRAMP compliance for other trace data:

  • Trace data is reported by some of our agents for APM, infrastructure monitoring, browser monitoring, and mobile monitoring. To enable FedRAMP compliance for trace data, follow the procedures for the applicable agent.
  • To enable FedRAMP compliance for Infinite Tracing, create a new FedRAMP-compliant trace observer in Infinite Tracing settings.
Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.