--- title: FedRAMP-compliant endpoints source: https://docs.newrelic.com/docs/security/security-privacy/compliance/fedramp-compliant-endpoints --- New Relic is [FedRAMP Authorized Moderate](https://marketplace.fedramp.gov/products/F1607057910) for accounts that meet specific criteria. As a cloud service provider, we are committed to ensuring our compliance with [FedRAMP's requirements](https://www.fedramp.gov/understanding-baselines-and-impact-levels/) 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 [#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](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-plus), 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](#overview). 4. **Authorized services and features**: Customer must use only FedRAMP audited and authorized New Relic [services and features](https://docs.newrelic.com/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp/#not-scope). ## FedRAMP inheritance [#inheritance] A customer can have FedRAMP and non-FedRAMP enabled accounts as required by their business needs. To [add accounts](https://docs.newrelic.com/docs/accounts/accounts-billing/account-structure/new-relic-account-structure), 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 [#overview] There are multiple ways to get data into New Relic, including: - [Agent settings](#agents) for our [APM agents](#apm-endpoints), [infrastructure agent](#infrastructure-endpoints), [browser monitoring agent](#browser-endpoints), and [mobile monitoring agent](#mobile-endpoints) - [Data-ingest APIs](#data-ingest-apis) for our Metric API, Event API, Log API, and Trace API, as well as the integrations that use those APIs 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](https://docs.newrelic.com/docs/security/new-relic-security/compliance/data-encryption) documentation. For further information on New Relic networks, domains, and ports, see our [networking](https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/networks) documentation. > #### ⚠️ IMPORTANT > > 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](https://docs.newrelic.com/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp-moderate), 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 [#agents] 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. | Endpoint | FedRAMP endpoint | Purpose and notes | | ------------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | aws-api.newrelic.com | gov-aws-api.newrelic.com | [AWS Metric Streams ingest](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) | | bam.nr-data.net | gov-bam.nr-data.net | [Browser ingest](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring/) Recommended browser endpoint. | | cloud-collector.newrelic.com | gov-cloud-collector.newrelic.com/ | Ingest for [AWS VPC Flow Logs](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration/) and [RDS Enhanced](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rds-enhanced-monitoring-integration/). | | collector.newrelic.com | gov-collector.newrelic.com | APM agent ingest | | infra-api.newrelic.com | gov-infra-api.newrelic.com | [Infrastructure agent ingest](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/) | | insights-collector.newrelic.com | gov-insights-collector.newrelic.com | [Event API ingest](https://docs.newrelic.com/docs/data-apis/ingest-apis/event-api/introduction-event-api/) | | log-api.newrelic.com | gov-log-api.newrelic.com | Our [Log API](https://docs.newrelic.com/docs/logs/log-api/introduction-log-api/), used by various agents and integrations. | | metric-api.newrelic.com | gov-metric-api.newrelic.com gov-metric-api.newrelic.com/prometheus/ | Our [Metric API](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/introduction-metric-api/) for dimensional metrics, used by various agents and integrations. | | mobile-collector.newrelic.com | gov-mobile-collector.newrelic.com | [Mobile agent ingest](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/) | | mobile-crash.newrelic.com | gov-mobile-crash.newrelic.com | [Mobile agent crash report ingest](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report/) | | otlp.nr-data.net | gov-otlp.nr-data.net:4318 gov-otlp.nr-data.net:4317 gov-otlp.nr-data.net:443 | [OpenTelemetry ingest](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction/). Configure using the [quick start guide](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/opentelemetry-get-started-intro/) with your account license key in the `api-key` header. | | trace-api.newrelic.com | gov-trace-api.newrelic.com | [Trace API ingest](https://docs.newrelic.com/docs/distributed-tracing/trace-api/introduction-trace-api) | | csec.nr-data.net | csec-gov.nr-data.net | IAST Validator Service URL (Requires secure WebSocket connection) | ### APM agents [#apm-endpoints] To ensure FedRAMP compliance, all [APM agent configurations](https://docs.newrelic.com/docs/using-new-relic/cross-product-functions/install-configure/configure-new-relic-agents/) 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. | Language | Code or environment variable | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Go | In code: ````go app, err = newrelic.NewApplication( newrelic.ConfigAppName("App Name"), newrelic.ConfigLicense(os.Getenv("NEW_RELIC_LICENSE_KEY")), func(cfg *newrelic.Config) { cfg.Host = "gov-collector.newrelic.com" }, ) ``` Environment variable: `NEW_RELIC_HOST` ```` | | Java | In `newrelic.yml`: ````yml common: &default_settings host: gov-collector.newrelic.com ``` Or set a system property of: ``` newrelic.config.host ``` Environment variable: `NEW_RELIC_HOST` ```` | | .NET | In your XML config next to the license key: ````xml ``` Environment variable: `NEW_RELIC_HOST` ```` | | Node.js | In `newrelic.js`: ````js host: 'gov-collector.newrelic.com' ``` Environment variable: `NEW_RELIC_HOST` ```` | | PHP | In `newrelic.ini`: ````ini newrelic.daemon.collector_host = gov-collector.newrelic.com ``` Environment variable: none ```` | | Python | In `newrelic.ini`: ````ini [newrelic] host = gov-collector.newrelic.com ``` Environment variable: `NEW_RELIC_HOST` ```` | | Ruby | In `newrelic.yml`: ````yml common: &default_settings host: gov-collector.newrelic.com ``` Environment variable: `NEW_RELIC_HOST` ```` | | Elixir (open source agent) | In `config.exs`: ````elixir config :new_relic_agent, host: "gov-collector.newrelic.com" ``` Environment variable: `NEW_RELIC_HOST` ```` | ### Infrastructure monitoring [#infrastructure-endpoints] If you have infrastructure agent version [1.15.0 or higher](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1150), simply enable the [FedRAMP configuration option](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings#fedramp). This enables FedRAMP compliancy for data reported by the infrastructure agent. This also enables FedRAMP compliancy for any [on-host integrations](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list) that work with the infrastructure agent to report data. **Infrastructure agent versions below 1.15.0** If you have an infrastructure agent version below 1.15.0, you must change three of the endpoints used for reporting. To set these endpoints, you can change your YAML configuration or use environment variables. | YAML config field | Endpoint URL | | --------------------- | ------------------------------------------------------------------ | | `collector_url` | ```` https://gov-infra-api.newrelic.com ``` ```` | | `identity_url` | ```` https://gov-identity-api.newrelic.com ``` ```` | | `command_channel_url` | ```` https://gov-infrastructure-command-api.newrelic.com ``` ```` | To edit environment variables, use these values: | Environment variable | Endpoint URL | | -------------------------- | ------------------------------------------------------------------ | | `NRIA_COLLECTOR_URL` | ```` https://gov-infra-api.newrelic.com ``` ```` | | `NRIA_IDENTITY_URL` | ```` https://gov-identity-api.newrelic.com ``` ```` | | `NRIA_COMMAND_CHANNEL_URL` | ```` https://gov-infrastructure-command-api.newrelic.com ``` ```` | ### Browser monitoring agent [#browser-endpoints] Browser monitoring agents will automatically update your account information to use the correct endpoints. ### Mobile monitoring agents [#mobile-endpoints] To ensure FedRAMP compliance when using our [mobile monitoring agents](https://docs.newrelic.com/docs/mobile-monitoring), 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: | Agent | Code or environment variable | | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Android | In code: ````java NewRelic.withApplicationToken({APP_TOKEN}) .usingCollectorAddress("gov-mobile-collector.newrelic.com") .usingCrashCollectorAddress("gov-mobile-crash.newrelic.com") .start(this.getApplication()); ``` Environment variable: none ```` | | iOS | In code: ````objc [NewRelic startWithApplicationToken:@"{APP_TOKEN}" andCollectorAddress:@"gov-mobile-collector.newrelic.com" andCrashCollectorAddress:@"gov-mobile-crash.newrelic.com"]; ``` Environment variable: none ```` | ## Data-ingest APIs [#data-ingest-apis] Follow these instructions as applicable to set the FedRAMP endpoint for a specific API or the integration that uses the API. ## OTLP API [#otlp-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](https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-otlp/#configure-endpoint-port-protocol). See that page for more details on FedRAMP compliance with OTLP. > #### ⚠️ IMPORTANT > > Do NOT send data to the US OTLP API endpoint of `https://otlp.nr-data.net:4317`. ## Metric API [#metric-api] To ensure FedRAMP compliance when using the [Metric API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/introduction-metric-api/), do not send [metric data](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types/#dimensional-metrics) 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 [#telemetry-integrations] Here are instructions for our [open source telemetry integrations](https://docs.newrelic.com/docs/integrations/open-source-telemetry-integrations) that report metric data: | Open-source telemetry integration | Configuration | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Dropwizard | Use the [`overrideUri` configuration](https://github.com/newrelic/dropwizard-metrics-newrelic#dropwizard-metrics-reporter) on GitHub. | | Kamon | Use the `metric-ingest-url` configuration. See the [Kamon documentation to override endpoints](https://kamon.io/docs/latest/reporters/newrelic/). | | Micrometer | Override the `public String uri()` method on your `NewRelicRegistryConfig` to return the new endpoint. See [the example](https://github.com/newrelic/micrometer-registry-newrelic/wiki/Spring-Config-Example) in GitHub. | | [Prometheus OpenMetrics](https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#OpenMetrics) | If you're using our [nri-prometheus helm chart](https://github.com/newrelic/helm-charts/blob/master/charts/nri-prometheus), you can change the endpoint in your `values.yml` file, like in [this example on GitHub](https://github.com/newrelic/helm-charts/blob/b5b6a3932989e0fa7be81c496417a68f7fde0f9e/charts/nri-prometheus/values.yaml#L68). If you're using the [nri-bundle chart](https://github.com/newrelic/helm-charts/tree/master/charts/nri-bundle), you need to nest this value under the `nri-prometheus` key to propagate it to the sub-chart. | | [Prometheus remote write integration](https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#remote-write) | 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](https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/install-configure-remote-write/set-your-prometheus-remote-write-integration/#setup). | ### Telemetry SDKs for metric data [#telemetry-sdks] Here are instructions for our [Telemetry SDKs](https://docs.newrelic.com/docs/telemetry-data-platform/get-started/capabilities/telemetry-sdks-send-custom-telemetry-data-new-relic) that report metric data: | Telemetry SDK for APM agents | Configuration | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Go | Use the [`MetricsURLOverride` configuration](https://github.com/newrelic/newrelic-telemetry-sdk-go/blob/9ff9c3035f5a4745f2f3df7ed1b13c6595542b40/telemetry/config.go#L40-L41) found on GitHub. | | Java | In the `MetricBatchSender` section, configure the endpoint. See the [example on GitHub](https://github.com/newrelic/newrelic-telemetry-sdk-java/blob/6d9bd99426c432cddb152c984b83508fe5aad922/telemetry_examples/src/main/java/com/newrelic/telemetry/examples/ConfigurationExamples.java#L77). | | .NET | Use the [`MetricUrlOverride` configuration](https://github.com/newrelic/newrelic-telemetry-sdk-dotnet/blob/2042f7bf617d4a5a90f858f1d81e1a678f648f26/src/NewRelic.Telemetry/TelemetryConfiguration.cs#L36) found on GitHub. | | Node.js | Edit the [`METRIC_HOST = 'metric-api.newrelic.com'` configuration](https://github.com/newrelic/newrelic-telemetry-sdk-node/blob/3cfbd52a4b6f5f4a41da9d14d5ea51bd8925234c/src/telemetry/metrics/client.ts#L5) found on GitHub. | | Python | Edit the [`HOST = "metric-api.newrelic.com"` configuration](https://github.com/newrelic/newrelic-telemetry-sdk-python/blob/044c18bfdc86128e8babb8016913cff934ad71a0/src/newrelic_telemetry_sdk/client.py#L289) found on GitHub. | ## Event API [#event-api] To ensure FedRAMP compliance for the [Event API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/introduction-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](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/telemetry-sdks-report-custom-telemetry-data). The Telemetry SDKs are used by our [open-source telemetry integrations](https://docs.newrelic.com/docs/integrations/open-source-telemetry-integrations). | Language | Solution | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Java Telemetry SDK | In code: ````java SenderConfiguration configuration = SenderConfiguration .builder( "gov-insights-collector.newrelic.com", EventBatchSender.EVENTS_PATH) .build(); EventBatchSender eventBatchSender = EventBatchSender.create(configuration); ``` ```` | | Python Telemetry SDK | In code: ````py event_client = EventClient(host="gov-insights-collector.newrelic.com") ``` For more information, see our [Telemetry API documentation in GitHub](http://newrelic.github.io/newrelic-telemetry-sdk-python/api.html#newrelic_telemetry_sdk.client.EventClient). ```` | ## Log API [#log-api] To ensure FedRAMP compliance for data sent via the [Log API](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-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](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api#endpoint). Here are details on changing the endpoint for our [log forwarders](https://docs.newrelic.com/docs/logs/forward-logs/enable-log-management-new-relic/). If a log forwarder is not listed, FedRAMP endpoint configuration is not available. | Log forwarder | Configuration | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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](https://docs.newrelic.com/docs/logs/forward-logs/aws-firelens-plugin-log-forwarding/). | | Fluentbit | Use [our Fluentbit endpoint configuration](https://github.com/newrelic/newrelic-fluent-bit-output#configuration-parameters) found on GitHub. | | Fluentd | Use [our Fluentd endpoint instructions](https://docs.newrelic.com/docs/logs/forward-logs/fluentd-plugin-log-forwarding). | | Infrastructure agent | See the [FedRAMP configuration instructions for infrastructure monitoring](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#fedramp). | | Kubernetes | Our Kubernetes integration logs are based on Fluentbit's output plugin. Use the [Helm chart endpoint instructions](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging#installation) found on GitHub. | | Logstash | Use our [Logstash endpoint configuration](https://docs.newrelic.com/docs/logs/forward-logs/logstash-plugin-log-forwarding/). | | Syslog | For configuring syslog clients, see our documentation about [TCP endpoint configuration](https://docs.newrelic.com/docs/logs/log-api/use-tcp-endpoint-forward-logs-new-relic/). | ## Trace API [#trace-api] To ensure FedRAMP compliance for data sent via the [Trace API](https://docs.newrelic.com/docs/distributed-tracing/trace-api/introduction-trace-api/) (including [telemetry integrations](https://docs.newrelic.com/docs/integrations/open-source-telemetry-integrations/get-started/introduction-new-relics-open-source-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](#agents). - To enable FedRAMP compliance for [Infinite Tracing](https://docs.newrelic.com/docs/distributed-tracing/infinite-tracing/introduction-infinite-tracing/), create a new FedRAMP-compliant trace observer in [Infinite Tracing settings](https://one.newrelic.com/launcher/mtb-nerdlets.edge-launcher). ## AWS PrivateLink Connectivity [#privatelink] FedRAMP-compliant endpoints are available over AWS PrivateLink in the same US-based [AWS regions and zones](https://docs.newrelic.com/docs/data-apis/custom-data/aws-privatelink#regions-zones) as our other US-based AWS PrivateLink endpoints. The requirements and instructions for setting up PrivateLink connectivity are otherwise identical to those documented at [Send New Relic data via AWS PrivateLink](https://docs.newrelic.com/docs/data-apis/custom-data/aws-privatelink/), in addition to the FedRAMP endpoint guidance above. These are the FedRAMP-compliant New Relic endpoint services available via AWS PrivateLink: ### US (us-east-1) | Data source | Hostname(s) | Endpoint service name(s) | | -------------------------------------------------------- | ------------------------------------- | --------------------------------------------------------- | | APM | `gov-collector.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-085289ac731dac9d5` | | Event API | `gov-insights-collector.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-06ba59867ec8dddd0` | | Metric API (including Prometheus and other integrations) | `gov-metric-api.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-0c67032d7c4fe49b5` | | Logging | `gov-log-api.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-09164c2d9f5b5a18f` | | Distributed tracing | `gov-trace-api.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-02af09fff9f20a1b8` | | AWS Lambda and Cloudwatch Logs monitoring | `gov-cloud-collector.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-038f12e4824efd9ca` | | Infrastructure monitoring and on-host integrations | `gov-infra-api.newrelic.com` | `com.amazonaws.vpce.us-east-1.vpce-svc-0d9904c7b662f90d2` | | OpenTelemetry | `gov-otlp.nr-data.net` | `com.amazonaws.vpce.us-east-1.vpce-svc-0650a85a1277d5e47` | ### US (us-east-2) | Data source | Hostname(s) | Endpoint service name | | -------------------------------------------------------- | ------------------------------------- | --------------------------------------------------------- | | APM | `gov-collector.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-00dd71388c3621c6b` | | Event API | `gov-insights-collector.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-0335ca060a9f394ca` | | Metric API (including Prometheus and other integrations) | `gov-metric-api.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-0b056f083ba590ef6` | | Logging | `gov-log-api.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-0d29fa0678cbc2d5b` | | Distributed tracing | `gov-trace-api.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-024c43802ddb6ab82` | | AWS Lambda and Cloudwatch Logs monitoring | `gov-cloud-collector.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-0274021e413a8f2eb` | | Infrastructure monitoring and on-host integrations | `gov-infra-api.newrelic.com` | `com.amazonaws.vpce.us-east-2.vpce-svc-0535a833972ecf6b0` | | OpenTelemetry | `gov-otlp.nr-data.net` | `com.amazonaws.vpce.us-east-2.vpce-svc-0b222a9fdac4be442` | ### US (us-west-2) | Data source | Hostname(s) | Endpoint service name | | -------------------------------------------------------- | ------------------------------------- | --------------------------------------------------------- | | APM | `gov-collector.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-070b53e0713a0e801` | | Event API | `gov-insights-collector.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-06e95a497356d3720` | | Metric API (including Prometheus and other integrations) | `gov-metric-api.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-07d02207bc4146824` | | Logging | `gov-log-api.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-0ecc7dc62de77034d` | | Distributed tracing | `gov-trace-api.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-00dcb17edbd180b7a` | | AWS Lambda and Cloudwatch Logs monitoring | `gov-cloud-collector.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-061cc9a4dc8890d76` | | Infrastructure monitoring and on-host integrations | `gov-infra-api.newrelic.com` | `com.amazonaws.vpce.us-west-2.vpce-svc-04dd56333fd4f17c4` | | OpenTelemetry | `gov-otlp.nr-data.net` | `com.amazonaws.vpce.us-west-2.vpce-svc-0db583297afa6ea1a` |