# Networking

## Ingress

### Requirements

The dbnl platform needs to be hosted on a domain or subdomain (e.g. dbnl-example.com or dbnl.example.com). It cannot be hosted on a subpath. 

### HTTPS/SSL

It is recommended that the dbnl platform be served over HTTPS. Support for SSL termination at the load balancer is included.

## Egress

### Requirements

Currently, the dbnl platform cannot run in an air-gapped environment and requires a few URLs to be accessible via egress.

**Artifacts Registry**

Required to fetch the dbnl paltform artifacts such as the Helm chart and Docker images.

* `https://us-docker.pkg.dev/dbnlai/`

**Object Store**

Required for services to access the object store.

* `https://{BUCKET}.s3.amazonaws.com/​` (if using S3)
* `https://storage.googleapis.com/{BUCKET}` (if using GCS)

**OIDC**

Required to validate OIDC tokens.

* `https://login.microsoftonline.com/{APP_ID}/v2.0/` (if using Microsoft EntraID)
* `https://{ACCOUNT}.okta.com/` (if using Okta)

**Integrations**

Required to use some integrations.

* `https://events.pagerduty.com/v2/enqueue`​ (if using PagerDuty)
* `https://hooks.slack.com/services/` (if using Slack)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dbnl.com/v0.22.x/platform/self-hosted/networking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.