> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Requirements

## Overview

G360 requires network access to allow users to access the application and to connect with the external tools configured by your organization.

Your organization's network or security team may need to configure firewall rules before deployment.

## Inbound Access

Inbound access refers to connections coming into the G360 environment.

The primary ports used by G360 are:

| Port   | Purpose                                             |
| ------ | --------------------------------------------------- |
| `443`  | Secure HTTPS access to the G360 application and API |
| `80`   | HTTP redirects and certificate validation           |
| `22`   | SSH access for deployment and administration        |
| `4318` | Optional OpenTelemetry access                       |

### HTTPS Access

Port `443` is the primary port used by users to access G360 securely.

Users access the application through HTTPS.

### HTTP Access

Port `80` may be used to:

* Redirect HTTP traffic to HTTPS
* Support TLS certificate validation

### SSH Access

Port `22` is used for authorized server administration and deployment activities.

Access should be restricted according to your organization's security policies.

<Note>
  Port `4318` is generally not required when OpenTelemetry traffic is routed through the G360 HTTPS endpoint.
</Note>

## Outbound Access

Outbound access refers to connections made by G360 to external services.

Depending on the integrations configured by your organization, G360 may need to communicate with services such as:

* Google Artifact Registry
* GitHub or GitHub Enterprise
* Jenkins
* Slack
* AWS services
* Amazon SES
* Other supported G360 integrations

## How G360 Connects to External Services

G360 initiates connections from within your organization's environment.

For example, when you configure a GitHub integration, G360 connects to GitHub to collect the required data.

This means external service providers do not need unrestricted inbound access to your organization's internal network.

<Note>
  Your network team should review the integrations your organization plans to use and allow the required outbound connections.
</Note>

## Firewall Configuration

Before configuring integrations, confirm that the G360 environment can communicate with the required external services.

The exact network requirements depend on the integrations your organization uses.

For example:

* GitHub integrations require access to GitHub
* Jenkins integrations require access to the Jenkins server
* Slack integrations require access to Slack services
* AWS integrations require access to the required AWS services

## Next Steps

After the required network access has been configured, your organization can optionally enable G360 health monitoring.

Continue to [Heartbeat to Garth](./heartbeat-to-garth).