Notification Center

Open in ChatGPTOpen in Claude

Notification Center in the FedRAMP environment is deliberately narrower than in the commercial regions. Every destination a notification can reach has to be FedRAMP Authorized in its own right, which rules out most of the connectors available elsewhere.

This page describes what is available on GOV1 and why. For how Notification Center works generally, see Notification Center.

Available connectors

Two connectors are available: ServiceNow and Generic HTTPS. Both target Cases, which is the only notification entity in this environment. The connector decides where the Case notification is delivered: ServiceNow to a GCC instance, Generic HTTPS to an endpoint you supply.

Every other connector available in the commercial regions is unavailable in the FedRAMP environment, including Slack, Microsoft Teams, PagerDuty, and email.

Alerts do not appear as a notification entity. An alert reaches its destination through the Case it opens, so when you configure an alert, the notification step offers Cases alone.

How that surfaces depends on how you create connectors:

• In the Coralogix UI, only the connectors available in this environment are offered. Unsupported connectors are not listed, so there is nothing to select and no error to run into.
• Through Terraform or the API, a request specifying an unsupported connector type is rejected.

The reason is the destination rather than Coralogix: a notification leaves the authorization boundary when it is delivered, so the receiving service has to carry its own FedRAMP authorization. Slack is not FedRAMP Authorized (GovSlack is a separate offering), and the rest are either unauthorized or not authorized for this use.

Generic HTTPS is the exception, and it is available on different terms. Because the endpoint is one you supply, the destination is yours to authorize rather than one Coralogix can vouch for. The environment therefore fixes the destination at configuration time, so that what you reviewed when you created the connector is what every notification reaches. See Generic HTTPS accepts a static URL only.

Requesting an additional connector

Before any connector is added to the FedRAMP environment, it has to be verified on the FedRAMP Marketplace:

• The service must be listed as FedRAMP Authorized. In Process and FedRAMP Ready are not sufficient.
• The specific Cloud Service Offering must match the intended use. A vendor holding an authorization for one offering does not extend it to another.

To request one, contact your account representative or email [email protected].

Generic HTTPS accepts a static URL only

The Generic HTTPS connector works as it does elsewhere, with one restriction: the URL is a fixed value you type once, and nothing can change it at send time.

In the commercial regions the connector accepts a dynamic URL built from the notification payload, so a single connector can reach a different endpoint per alert or per Case. In the FedRAMP environment that field is not offered. The URL field takes a static value, and the dynamic fields section of the connector form is not shown at all, so the dynamic headers and dynamic body fields are unavailable along with the dynamic URL.

Field	Commercial	FedRAMP
URL	Static value	Static value
Dynamic URL	Available, overrides the URL per notification	Not available
Headers, Additional body fields	Available	Available
Dynamic headers, Dynamic body fields	Available	Not available
Per-entity-type overrides	Available	Not available

Per-entity-type overrides are the values a connector can carry for one notification source type, which replace the connector's own configuration when a notification of that type is sent. They are rejected here for the same reason: they would let the delivered destination differ from the configured one.

This applies however you create the connector. The UI does not offer the fields, and a request that supplies them through Terraform or the API is rejected rather than silently accepted. A deep link carrying override parameters has them dropped before the form opens.

ServiceNow must be a GCC instance

The ServiceNow instance you connect to must be a Government Community Cloud (GCC) instance, with a URL of the form:

https://your-instance.servicenowservices.com

A commercial ServiceNow instance (*.service-now.com) is rejected. Only ServiceNow's GCC offering holds FedRAMP authorization, so sending Coralogix data to a commercial instance would move it outside the authorization boundary.

One-directional only

The connector sends records from Coralogix to ServiceNow. Updates made in ServiceNow are not synchronized back to the Coralogix Case.

In the commercial regions this synchronization is bidirectional. Plan your workflow so that Coralogix remains the system of record for Case state.

Presets

Custom presets are available, for Generic HTTPS. Create one from Presets, the same way you would in the commercial regions, and the editor behaves identically.

ServiceNow has no custom preset, and this is not a FedRAMP restriction. ServiceNow does not support custom presets in any region, so its notifications use the ServiceNow system preset as it ships. That preset sends the same content it sends in the commercial regions. A ServiceNow GCC instance sits inside the FedRAMP authorization boundary, so the notification carries its usual fields rather than a reduced set.

Connector	Presets
ServiceNow	System preset only, the same content as commercial
Generic HTTPS	System and custom presets

What this means for setup

Otherwise, Notification Center behaves as it does elsewhere. Routers, routing rules, and routing labels work the same way, and Cases still drive notifications through their ownership tags.

The routing documentation therefore applies here as written. Read its examples with this environment in mind: they route alert entities to connectors such as Slack and PagerDuty, none of which are available here, so treat them as illustrations of the matching logic rather than configurations you can copy.

The practical differences when you configure it:

	FedRAMP environment
Connectors	ServiceNow (GCC instance) and Generic HTTPS
Creating connectors	The UI offers only supported types. Terraform and the API reject the rest
Generic HTTPS URL	Static only. No dynamic URL, dynamic headers, dynamic body, or per-entity-type overrides
Entity type	Cases only, alerts route through their Case
Presets	Custom presets for Generic HTTPS. ServiceNow uses its system preset
ServiceNow sync	Coralogix to ServiceNow only

Related resources

FedRAMP environmentServiceNow destination typeGeneric HTTPS destination typeNotification Center introductionCases

Next steps

Review how your tenant reaches the environment in Access and authentication.